On Nov 7, 2006, at 1:50 PM, Jacek Laskowski wrote:
On 11/7/06, Rodent of Unusual Size <[EMAIL PROTECTED]> wrote:
The implicit assumption there is that the 'developers' all have
the same interests. That's not necessarily how it works. If
there are some people who are interested in EE 5 but not in the
work on trunk, then they probably aren't contributing anything
there now. So creating a branch won't be sucking those people
away from trunk, whereas *not* creating it won't advance the
trunk work and *does* present an obstacle for those people.
The uncertainty element here is people who are currently
contributing to trunk but would switch over to an EE 5
branch if one were created. Those individuals would be happy,
but the trunk work would suffer.
On the other hand, part of what contributes to community is
individual empowerment. If there's insufficient interest in
the trunk work to advance it, then that's pretty much all
she wrote. It becomes a dead horse. Trying to mandate that
people put aside their own interests and work on stuff
that *doesn't* interest them isn't an Apache paradigm. It
has a lot more in common with commercial meet-the-deadline
models.
Whow! Very well written! I like it. It should be part of our
documentation somewhere. I was leaning towards Dain's and Dave's views
and thought to withdraw my +1, but now it won't happen at all. Thanks
Ken!
My objection to putting the jee5 work into a branch is that it's not
a branch! It is currently and IMO will always remain additional
code that can happily run side by side with all our current code.
Creating the jee5 workspace is not going to involve copying any
existing geronimo server branch: its going to involve adding new
modules for new functionality. After reading ken's comments I agree
that keeping it in the sandbox carries an unwanted implication that
it's not ready for prime time.
The only solution that comes close to seeming appropriate to me is to
reorganize the jee5 work into plugins and move each one into an
appropriate plugin area. I'm worried that this will cause build
system disruption but I think we have to deal with that soon anyway.
thanks
david jencks
Jacek
--
Jacek Laskowski
http://www.jaceklaskowski.pl
