No, my reason for the -1 is that "IBM has contracted with a group at the University of Jena in Germany to help create the reference implementation of JSR-286 to be hosted at Apache. ", as cdoremus put it. This means that the code result is a work for hire, and thus would need to go through corporate CLA, vetting, etc. in the incubator.
OTOH, given the secrecy which has involved the whole JSR process (a committer of the portals project was the chair, but we actually got the first notice through the JCP website, etc.) I'm afraid we will be again in a world of obscure changes, which go straight against the Apache Community spirit, and is the kind of things that have been slowly killing this project in the last couple of years, from the community point of view. Now, if the components of such team have the whole communications on pluto-dev, and they send patches (except for Ulrich, which is a committer) that get integrated until they earn committership, the process would not need to pass through the incubator. This is not an opinion, I think this is hard policy in the ASF. Apache is about communities, not about code. I (this is an opinion) don't care a dime about Reference Implementations unless they are used and tested. This is the case now with pluto 1.0, but it was not the case when it got donated. I am afraid that we are facing a code dump that will take a lot of time to clean up. Those are my concerns. Regards Santiago On 8/25/06, Ralph Goers <[EMAIL PROTECTED]> wrote:
Santiago Gala wrote: > I'm -1 about the branch. > Is your reason for the -1 because you feel that the JSR 286 work should happen on trunk (assuming it was Pluto committers doing the work)? Wouldn't you need to create a branch for 1.1 before you could start that? Ralph
