On Tue, Jun 3, 2008 at 3:05 PM, ant elder <[EMAIL PROTECTED]> wrote: > > > On Tue, Jun 3, 2008 at 10:10 AM, Sanjiva Weerawarana < > [EMAIL PROTECTED]> wrote: > >> ant elder wrote: >> >>> >>> While things are as they are I do think things like Mercury announcements >>> should be kept off the Apache mailing lists, so no more posts like: >>> http://apache.markmail.org/message/ounhpi54rx543vqw >>> >> >> Why? Who's rules are you trying to enforce with that? Mercury is an RM >> module for Axis2 and its open source and under Apache license. Feel free to >> ignore it but there's nothing wrong with that email. >> >> > There are no "rules" about it, but I don't think its going to help things. > Any revolutionary rewrite like this by a subset of the community is going to > make an uncomfortable situation. It seems like everyone agrees ideally this > will end up again with one RM module being developed at Apache in the WS > project with all the existing community behind it. So with that aim it would > help if everyone could try to be sensitive. > > Maybe as a start everyone could read the "rules for revolutionaries" - > http://incubator.apache.org/learn/rules-for-revolutionaries.html >
As I understood this revolutionary talks about doing a substantial improvement to an existing code base. For an example If I come up with a Sandasha2 improvement which community does not agree at first time, I can create a branch of existing Sandesha2 code base and implement my improvement. Then I can ask from the community to review it and merge it to the main trunk. But here the case is different. Mercury is completely different from Sandesha2. It is not an improvement to Sandesha2. AFAIK Apache in general does not have a policy to handle this kind of situations. For an example If I came up with this idea when I wrote the Simulator People would have said This is not a real implementation and a real implementation would be more complex. On the other hand If I put a complete implementation then people would have said This has happened without telling to the community. So it becomes a chicken and egg problem. IMHO the correct solution is to keep both implementations and Let people to contribute/use to whatever they prefer. And when the time goes we can decide whether to go ahead with Sandesha2, Mercury or both. thanks, Amila. <http://incubator.apache.org/learn/rules-for-revolutionaries.html> > > ...ant > > > > > > -- Amila Suriarachchi, WSO2 Inc.
