(Trimming down to the nuts and bolts to try to help us come to consensus):
On Thu, 15 Mar 2001 [EMAIL PROTECTED] wrote:
> > Why can't they do that in the Commons? Those packages are going to be
> > maintained, and enhanced, and released, as well. What's the difference?
>
> Control. Who decides the future and changes of the component. Who supports
> it.
>
> Some may prefer to use components supported by a dedicated group (
> commons, avalon, a project ). Some may prefer to use components in Agora,
> where they have control over the evolution of the component.
>
OK, now I see where Costin is coming from (sorry for being dense :-).
Costin, is it fair to say that your concern is the following scenario?
a) Through Agora-style collaboration, people from 2+ projects
create a useful Foo in the sandbox.
b) Things look good, so they propose it to be added to Commons
c) Commons (as a whole) accepts the code.
d) Original developers continue to work on it, and use the result
in a release of their subprojects.
e) Commons (as a whole) decides to take this code in a different
direction than the original developers wanted it :-(
f) Original developers feel backstabbed.
OK, that's a valid thing to worry about. However, I don't see it
happening in reality, for the following reasons:
* The commons developers as a whole only vote to accept a particular
package in the first place -- they don't determine technical direction
* The original package is still maintained by the original collaborators
(or others who add themselves into the mix on that package). It is
released only when the active developers say so, not on any global
schedule determined by Commons (as a whole).
* Even if someone did want to take the shared Foo in a different
direction, they can fork and create Foo-prime (possibly based on Foo,
possibly not depending on circumstances).
Experience with taglibs to date (which follows a model somewhat like
Commons) says that people really don't step on each other when you know
it's a shared use environment.
Does this alleviate your concern? If not, can we make the language about
how Commons works stronger to make sure that this scenario cannot happen?
> Costin
>
>
Craig
