cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "marc fleury" <>
Subject RE: Cocoon and Axis
Date Thu, 04 Oct 2001 13:17:48 GMT
|"Customers" finding and fixing problems themselves is one of the benefits
|of open source.  I certainly won't say that we couldn't have done better
|(we clearly could have), but for the moment can I ask that you open problem
|reports on bugzilla for issues that are important to you.


|People who were active participants for long periods of time disappear
|suddenly and without a trace for a long period of time, only to poke their
|head in occasionally to give advice as to what the others should be working
|on.  No, I am not attempting to single out Sanjiva - pretty much all but
|one or two names on the committers list falls into this category.

well frankly I am amused by the naivete of this....

OF COURSE people come and people go, only when you are paid full time by IBM
can you afford to commit full time.  I am reading this thread and alarms go
off in my head left and right.

It looks as if IBM controls the commit, does a poor job of following up with
all the people, is surprised at fundamental workings of Open Source.

What you are going to see is forks if you don't remedy the situation.

|For a while, the solution appeared to be to nominate more committers.  That
|has lead to mixed results as best.  Glen (unquestionably one of the stable
|resources committed to the Apache Soap projects) has now rightfully called
|in question this practice.

No that is the solution.  More committers, you just can't follow everything
and trust is the key, no trust no project, just paid developers from IBM
releasing software under an open source license using Apache infrastructure
and cover. Blah.

|At the same time, I would love to see some more involvement by cocoon
|committers.  Berin, dims, and yourself all appear interested, but as I
|pointed out above, we have recently been burned by disappearing committers.

What we do in JBoss is that if you don't use your RW you loose your
privileges RW is not for life. RW is for the time the commiter is going to
help you, i.e. for the time he is going to develop with your stuff and fix
bugs accordingly after that he is gone... it works, it's done, it is normal.

|If you want a DOM based approach (like cocoon1 was), then sure.  If not,
|bear with us, and pitch in when you can.


Look, I don't mean to give lessons, but I monitor the list and I see from
Jung that we have 101 simple problems that are normal in an alpha
implementation but really are simple/beginner stuff.  You want a quality
implementation for free? you give RW wide and fast! Your job is then to
monitor the commiters for abuse.  Simple scalable.


To unsubscribe, e-mail:
For additional commands, email:

View raw message