There are no legal requirements to do
a feature per bundle or make the license stuff particularly easy to access.
Plugin details is more than enough. Look at all the systems
that use these things and don't even have a UI. People have to grovel
through JAR files. As a rule we have put legal files with the thing
they are related to (i.e., with the bundle).
<Martin.Oberhuber@xxxxxxxxxxxxx> Sent by: orbit-dev-bounces@xxxxxxxxxxx
10/23/2006 07:48 AM
Please respond to
Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
Re: [orbit-dev] Ready for code features?
> > To me, the driving use-case is what we provide
> > If we follow the Callisto model, we'd provide one feature for
> > then other projects could "require" (not 'include')
> > feature for improved
> > update manager operation. Is that still the right model?
> Some projects seem to have followed that model while others (e.g.,
> Eclipse project) just included the third party bundles in their
> features. Honests I've not thought about this alot to have an
> one way or the other.
Just wondering, if there are not (at least for Apache libs) some legal
requirements that force us to have a feature per bundle? - The APL says,
that "user documentation must include the term 'This product includes
software developed by the Apache Software Foundation'".
To me, the only sensible place where to read this, is in the about box
under feature details -- the actual plugin's about_files seem to be too
hard to access for a user.
Wind River Systems, Inc.
Target Management Project Lead, DSDP PMC Member
orbit-dev mailing list