Re: [PROPOSAL] OpenCMIS incubator for Content Mangement Interoperability Services (CMIS)
The Board has in the past condemned "balkanization" of community, and my take on this situation is exactly that. This is not "yet another web framework", which often brought forward as examples that the ASF encourages competition within. Those typically have a different "angle", "approach" or "metaphor", something making each very different beasts. But in this case we are talking about "the same spec". There is no real distinguishing features and huge overlap of commonality. I think this is a NIH-syndrome in play, in the best case "oh we have the code working already" and the worst case "we don't like to collaborate with them", and there is reason to think that that goes for both sides of the fence. I want to see Chemistry capable to absorb such contribution and collaborate heavily to bring such codebase in. And I want to see the people of the OpenCMIS proposal to show that they indeed can work with others. Exactly how the merged community goes about with the technical integration is its own business, but I am worried that the new codebase will not receive the welcome I hope, the Chemistry base will dominate, and the OpenCMIS proposer get fed up and leaves. Important Mentors understand the risks here, and keep eyes extra open for attrition, domination and forceful consensus-seeking. I think discussion should continue on Chemistry dev@ list. If agreement can't be reached there, then I am NOT in favor of incubating OpenCMIS separately and will vote -1 to such proposal. I will also form myself an opinion of how well Chemistry is trying to collaborate, and it may improve or deteriorate its status with me. This can become an excellent opportunity for all involved to show off their ApacheWay skills -- Niclas On 13 Dec 2009 09:47, "Emmanuel LŽcharny" wrote: Joe Schaefer a écrit : > > > >> >> I see where Joe is going to with his "let both project get in and > let's see which one will su... > I must admit that it's human nature, but I think - but I'm probably optimistic - that people working on an apache project should overcome this reluctance. In this very case, as Chemistry has entered the incubator more than 6 months ago, I can understand that 'merging' with OpenCMIS would slow down the process, and OTOH, OpenCMIS may not like the idea to be seen as a sub-project... But this is the Incubator, the perfect place yo work out such problems. My fear is that by accepting two separate projects, one may die (or even both), because of the lack of community... It seems less likely if both project work out a common solution, IMHO. Collaboration does not kill good ideas... - To unsubscribe, e-mail: g...
Re: [PROPOSAL] OpenCMIS incubator for Content Mangement Interoperability Services (CMIS)
Joe Schaefer a écrit : I see where Joe is going to with his "let both project get in and let's see which one will survive", I can't help but thinking that beside the rules, there is a spirit which is way more important. At least, let's try... The way I see it the purpose of a proposal is to attract mentors to the proposal. Given that Chemistry is already here, and contains lots of people who know how to build communities around the code, I can understand the reluctance to support a competing effort by some people. I must admit that it's human nature, but I think - but I'm probably optimistic - that people working on an apache project should overcome this reluctance. In this very case, as Chemistry has entered the incubator more than 6 months ago, I can understand that 'merging' with OpenCMIS would slow down the process, and OTOH, OpenCMIS may not like the idea to be seen as a sub-project... But this is the Incubator, the perfect place yo work out such problems. My fear is that by accepting two separate projects, one may die (or even both), because of the lack of community... It seems less likely if both project work out a common solution, IMHO. Collaboration does not kill good ideas... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] OpenCMIS incubator for Content Mangement Interoperability Services (CMIS)
- Original Message > From: Emmanuel Lcharny > To: general@incubator.apache.org > Sent: Sat, December 12, 2009 7:32:53 PM > Subject: Re: [PROPOSAL] OpenCMIS incubator for Content Mangement > Interoperability Services (CMIS) > > Michael Wechner a écrit : > > Emmanuel Lcharny wrote: > >> Michael Wechner a écrit : > >>> Stefane Fermigier schrieb: > OK, I personally believe this is in contradiction with the first > commandment of the Apache Way: > > "*Community over Code* is a frequent saying that exemplifies ASF > projects. > Community uses Openness and Merit, expressed through Collaborative and > Consensus > driven work, to build lasting projects that use a Pragmatic License. While a > diverse community is a requirement for every ASF project, we also expect > people > to contribute as Individuals, and wear appropriate Hats." > >>> > >>> I cannot see any contradiction. Can you explain where exactly you see the > contradiction? > >> Hi, > >> > >> I just grab the description of both projects : > >> > >> "OpenCMIS will deliver a Java implementation of the OASIS CMIS > specification." > >> > >> "Apache Chemistry is a generic Java language implementation of the > >> upcoming > OASIS CMIS specification. " > >> > >> I barely see how two communities working on two projects with the very > >> same > target can't collaborate and form the best possible community to fulfill this > target, leveraging the great people from both of the current project... > >> > >> This is where I see a contradiction : it seems like there is some > >> divergence > on the technical side, which is not really the Incubator concern. What is > important to us is that a community is built, because it's the guarantee for > a > long term existence for the project. We don't have the resources and time to > setup a darwinian process here :) > > > > I am not sure what exactly you mean with "we", but I would argue that the > > CMS > community out there is rather large and has enough > > potential to provide contributors for both projects. > > > > It's up to each incubator project itself to build a healthy community and > AFAIK these rules are clear and in particular what it takes to leave the > incubator. > > So either a project will make it or not. I am assuming this is what the > incubator is good for, right? > > Would the Incubator be a place where projects enter and try to develop and > succeed per their technical merit only, I would agree. But it involves people > with a limited timeframe (mentors, champion, PMC members), and I feel that > it's > a bit a waste to see two projects trying to implement the exact same spec > unable > to collaborate. I mean, both teams most certainly have their own merit, I > won't > argue this point, but at some point a bit less ego and a bit more > collaboration > will generate a better result. > > I see where Joe is going to with his "let both project get in and let's see > which one will survive", I can't help but thinking that beside the rules, > there > is a spirit which is way more important. > > At least, let's try... The way I see it the purpose of a proposal is to attract mentors to the proposal. Given that Chemistry is already here, and contains lots of people who know how to build communities around the code, I can understand the reluctance to support a competing effort by some people. But Apache is a big organization, certainly big enough for two entries into the CMIS market if things work out that way. But I am always skeptical about a project with closed-source origins without a decent contingent of Apache people already involved. Let me also make it clear that I have no interest in either project, so my remarks are meant to be taken as coming from a distance. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] OpenCMIS incubator for Content Mangement Interoperability Services (CMIS)
Michael Wechner a écrit : Emmanuel Lcharny wrote: Michael Wechner a écrit : Stefane Fermigier schrieb: OK, I personally believe this is in contradiction with the first commandment of the Apache Way: "*Community over Code* is a frequent saying that exemplifies ASF projects. Community uses Openness and Merit, expressed through Collaborative and Consensus driven work, to build lasting projects that use a Pragmatic License. While a diverse community is a requirement for every ASF project, we also expect people to contribute as Individuals, and wear appropriate Hats." I cannot see any contradiction. Can you explain where exactly you see the contradiction? Hi, I just grab the description of both projects : "OpenCMIS will deliver a Java implementation of the OASIS CMIS specification." "Apache Chemistry is a generic Java language implementation of the upcoming OASIS CMIS specification. " I barely see how two communities working on two projects with the very same target can't collaborate and form the best possible community to fulfill this target, leveraging the great people from both of the current project... This is where I see a contradiction : it seems like there is some divergence on the technical side, which is not really the Incubator concern. What is important to us is that a community is built, because it's the guarantee for a long term existence for the project. We don't have the resources and time to setup a darwinian process here :) I am not sure what exactly you mean with "we", but I would argue that the CMS community out there is rather large and has enough potential to provide contributors for both projects. It's up to each incubator project itself to build a healthy community and AFAIK these rules are clear and in particular what it takes to leave the incubator. So either a project will make it or not. I am assuming this is what the incubator is good for, right? Would the Incubator be a place where projects enter and try to develop and succeed per their technical merit only, I would agree. But it involves people with a limited timeframe (mentors, champion, PMC members), and I feel that it's a bit a waste to see two projects trying to implement the exact same spec unable to collaborate. I mean, both teams most certainly have their own merit, I won't argue this point, but at some point a bit less ego and a bit more collaboration will generate a better result. I see where Joe is going to with his "let both project get in and let's see which one will survive", I can't help but thinking that beside the rules, there is a spirit which is way more important. At least, let's try... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] OpenCMIS incubator for Content Mangement Interoperability Services (CMIS)
Florent Guillaume wrote: On Fri, Dec 11, 2009 at 11:18 PM, Michael Wechner wrote: Right and as long as OpenCMIS fulfills the requirements of the incubator I don't see any reason why there shouldn't be two projects of the same topic. I also do not see any reason why OpenCMIS should be a sub-project of Chemistry. Give it a chance of its own within the current rules of the incubator and it will either work or not. If it works, then graduate, if not, then remove it. My concern is that if there are two separate svn trees then factoring things between the two projects will be much harder. Let's not kid ourselves, having two different maven release cycles, and having dependencies to foreign SNAPSHOT projects, will not help. To me it's a waste of time and effort. Let me ask the question differently: what's lost by having the code in the Chemistry svn tree? Beside that I agree with Joe's email I would additionally argue that you can easily share code without being within the same project and having it separate from each other it forces you to make the architecture/code even better, which I think has (nearly) only advantages. Cheers Michael Florent - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] OpenCMIS incubator for Content Mangement Interoperability Services (CMIS)
Emmanuel Lcharny wrote: Michael Wechner a écrit : Stefane Fermigier schrieb: OK, I personally believe this is in contradiction with the first commandment of the Apache Way: "*Community over Code* is a frequent saying that exemplifies ASF projects. Community uses Openness and Merit, expressed through Collaborative and Consensus driven work, to build lasting projects that use a Pragmatic License. While a diverse community is a requirement for every ASF project, we also expect people to contribute as Individuals, and wear appropriate Hats." I cannot see any contradiction. Can you explain where exactly you see the contradiction? Hi, I just grab the description of both projects : "OpenCMIS will deliver a Java implementation of the OASIS CMIS specification." "Apache Chemistry is a generic Java language implementation of the upcoming OASIS CMIS specification. " I barely see how two communities working on two projects with the very same target can't collaborate and form the best possible community to fulfill this target, leveraging the great people from both of the current project... This is where I see a contradiction : it seems like there is some divergence on the technical side, which is not really the Incubator concern. What is important to us is that a community is built, because it's the guarantee for a long term existence for the project. We don't have the resources and time to setup a darwinian process here :) I am not sure what exactly you mean with "we", but I would argue that the CMS community out there is rather large and has enough potential to provide contributors for both projects. It's up to each incubator project itself to build a healthy community and AFAIK these rules are clear and in particular what it takes to leave the incubator. So either a project will make it or not. I am assuming this is what the incubator is good for, right? Cheers Michael my 2 cts ... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] OpenCMIS incubator for Content Mangement Interoperability Services (CMIS)
- Original Message > From: Florent Guillaume > To: general@incubator.apache.org > Cc: chemistry-...@incubator.apache.org > Sent: Sat, December 12, 2009 10:35:18 AM > Subject: Re: [PROPOSAL] OpenCMIS incubator for Content Mangement > Interoperability Services (CMIS) > > On Fri, Dec 11, 2009 at 11:18 PM, Michael Wechner > wrote: > > Right and as long as OpenCMIS fulfills the requirements of the incubator I > > don't see any reason why there shouldn't be two projects of the same topic. > > > > I also do not see any reason why OpenCMIS should be a sub-project of > > Chemistry. > > Give it a chance of its own within the current rules of the incubator and it > > will either work or not. > > If it works, then graduate, if not, then remove it. > > My concern is that if there are two separate svn trees then factoring > things between the two projects will be much harder. Let's not kid > ourselves, having two different maven release cycles, and having > dependencies to foreign SNAPSHOT projects, will not help. To me it's a > waste of time and effort. > > Let me ask the question differently: what's lost by having the code in > the Chemistry svn tree? Sovereignty over the codebase for one. At this point I don't see why people are so concerned with the (lack of) alignment with Chemistry. If the people who wish to work on this proposal prefer to go it alone for the time being, so be it. If a community doesn't emerge out of one project or the other, it's an easier decision to make at that time then it is to predict in advance right now. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] OpenCMIS incubator for Content Mangement Interoperability Services (CMIS)
On Fri, Dec 11, 2009 at 11:18 PM, Michael Wechner wrote: > Right and as long as OpenCMIS fulfills the requirements of the incubator I > don't see any reason why there shouldn't be two projects of the same topic. > > I also do not see any reason why OpenCMIS should be a sub-project of > Chemistry. > Give it a chance of its own within the current rules of the incubator and it > will either work or not. > If it works, then graduate, if not, then remove it. My concern is that if there are two separate svn trees then factoring things between the two projects will be much harder. Let's not kid ourselves, having two different maven release cycles, and having dependencies to foreign SNAPSHOT projects, will not help. To me it's a waste of time and effort. Let me ask the question differently: what's lost by having the code in the Chemistry svn tree? Florent -- Florent Guillaume, Director of R&D, Nuxeo Open Source, Java EE based, Enterprise Content Management (ECM) http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] OpenCMIS incubator for Content Mangement Interoperability Services (CMIS)
Michael Wechner a écrit : Stefane Fermigier schrieb: OK, I personally believe this is in contradiction with the first commandment of the Apache Way: "*Community over Code* is a frequent saying that exemplifies ASF projects. Community uses Openness and Merit, expressed through Collaborative and Consensus driven work, to build lasting projects that use a Pragmatic License. While a diverse community is a requirement for every ASF project, we also expect people to contribute as Individuals, and wear appropriate Hats." I cannot see any contradiction. Can you explain where exactly you see the contradiction? Hi, I just grab the description of both projects : "OpenCMIS will deliver a Java implementation of the OASIS CMIS specification." "Apache Chemistry is a generic Java language implementation of the upcoming OASIS CMIS specification. " I barely see how two communities working on two projects with the very same target can't collaborate and form the best possible community to fulfill this target, leveraging the great people from both of the current project... This is where I see a contradiction : it seems like there is some divergence on the technical side, which is not really the Incubator concern. What is important to us is that a community is built, because it's the guarantee for a long term existence for the project. We don't have the resources and time to setup a darwinian process here :) my 2 cts ... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] OpenCMIS incubator for Content Mangement Interoperability Services (CMIS)
Stefane Fermigier schrieb: OK, I personally believe this is in contradiction with the first commandment of the Apache Way: "*Community over Code* is a frequent saying that exemplifies ASF projects. Community uses Openness and Merit, expressed through Collaborative and Consensus driven work, to build lasting projects that use a Pragmatic License. While a diverse community is a requirement for every ASF project, we also expect people to contribute as Individuals, and wear appropriate Hats." I cannot see any contradiction. Can you explain where exactly you see the contradiction? -> Let our Apache Foundation overlords decide. who are you refering to? I still think that at least there should be common code (ex: constants, as suggested by Jukka) and I hope that this will the case, in any case. Maybe you want to go one step towards OpenCMIS and make a concrete suggestion what you think could be shared and I am quite certain the OpenCMIS guys will also make a step towards Chemistry as well and I am confident collaboration will happen, but yes somebody has to make a first step and maybe it is even an advantage to take this first step ;-) Cheers Michael S. On Dec 11, 2009, at 11:18 PM, Michael Wechner wrote: Florian Müller wrote: Well, here is a citation from http://www.apache.org/foundation/how-it-works.html (section "The Foundation Incubator"): "It must be noted that the incubator (just like the board) does not perform filtering on the basis of technical issues. This is because the foundation respects and suggests variety of technical approaches. It doesn't fear innovation or even internal confrontation between projects which overlap in functionality." right and as long as OpenCMIS fulfills the requirements of the incubator I don't see any reason why there shouldn't be two projects of the same topic. I also do not see any reason why OpenCMIS should be a sub-project of Chemistry. Give it a chance of its own within the current rules of the incubator and it will either work or not. If it works, then graduate, if not, then remove it. Or am I missing something which violates any current rule of the incubator? Cheers Michael Florian -Original Message- From: Stefane Fermigier [mailto:s...@nuxeo.com] Sent: Friday, December 11, 2009 7:46 PM To: chemistry-...@incubator.apache.org Cc: Incubator-General Subject: Re: [PROPOSAL] OpenCMIS incubator for Content Mangement Interoperability Services (CMIS) On Dec 11, 2009, at 7:10 PM, Florian Müller wrote: Chemistry uses Abdera to communicate with the server while OpenCMIS is based on JAX-B and some CMIS specific XML coding. I've been personally asking myself recently wether it would be feasible to drop Abdera in favor of JAXB in Chemistry, so IMHO it's something that should be discussed together and not a division line for us. There is a lot of code sharing between the AtomPub and the Web Services binding. (I couldn't find a Web Services client in Chemistry. It would be great if you could contribute one. Here we are with a working code base that we cannot give up and that we will maintain in the future for obvious reasons. Our idea was to make it Open Source and let others benefit from our work. Apache seemed to be the right place - at least three days ago. OK, I'm new to this Apache thing, but I don't believe this is the Apache Way. See: http://theapacheway.com/ or http://www.slideshare.net/jaaronfarr/the-apache-way-hk-sfd-2009 S. -- Stefane Fermigier, Founder and Chairman, Nuxeo Open Source, Java EE based, Enterprise Content Management (ECM) Web: http://www.nuxeo.com/ - Tel: +33 1 40 33 79 87 New: follow me on Twitter: http://twitter.com/sfermigier - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Stefane Fermigier, Founder and Chairman, Nuxeo Open Source, Java EE based, Enterprise Content Management (ECM) Web: http://www.nuxeo.com/ - Tel: +33 1 40 33 79 87 New: follow me on Twitter: http://twitter.com/sfermigier - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Cassandra PPMC?
On Sat, Dec 12, 2009 at 11:38 AM, Bertrand Delacretaz wrote: > On Sat, Dec 12, 2009 at 5:27 AM, Matthieu Riou > wrote: >> ...Podlings PPMCs are reflected somewhere in asf-authorization? How so? In >> any >> case Eric is part of the Cassandra PPMC and I can co-sign if necessary > > Is there a public list of PPMC members somewhere? > > I haven't found it at either > http://incubator.apache.org/projects/cassandra.html or > http://incubator.apache.org/cassandra/ > > -Bertrand > The PPMC is a bit of an artificial construct so AFAIK there is no place where PPMC membership is recorded, usually the only record of it is in the poddlings private list archive. The list of subscribers to the private list gives an indication though there'll also be all the mentors and possibly other ASF members included in that list that need to be sifted through. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Cassandra PPMC?
On Sat, Dec 12, 2009 at 5:27 AM, Matthieu Riou wrote: > ...Podlings PPMCs are reflected somewhere in asf-authorization? How so? In any > case Eric is part of the Cassandra PPMC and I can co-sign if necessary Is there a public list of PPMC members somewhere? I haven't found it at either http://incubator.apache.org/projects/cassandra.html or http://incubator.apache.org/cassandra/ -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] OpenCMIS incubator for Content Mangement Interoperability Services (CMIS)
On Sat, Dec 12, 2009 at 10:27 AM, Stefane Fermigier wrote: > OK, I personally believe this is in contradiction with the first commandment > of the Apache Way: > > "*Community over Code* is a frequent saying that exemplifies ASF projects. > Community uses Openness and Merit, expressed through Collaborative and > Consensus driven work, to build lasting projects that use a Pragmatic > License. While a diverse community is a requirement for every ASF project, > we also expect people to contribute as Individuals, and wear appropriate > Hats." > > -> Let our Apache Foundation overlords decide... Too bad...there are no overlords here ;-) Some of us are speaking as members of the Incubator PMC, having seen a few podlings succeed or fail, and trying to ensure success of at least one (or maybe two if that's needed) CMIS podlings. But in the end it's a decision of the whole Incubator PMC, which I imagine is heavily influenced by having a champion and a few mentors take care of the podling. In my case, the lukewarm welcome to OpenCMIS is mostly due to the fact that nothing was discussed with Chemistry before making the proposal. To me that feels like doing things behind the Chemistry team's back, which I don't like. Hopefully that's being sorted out with the current discussions. > ...I still think that at least there should be common code (ex: constants, as > suggested by Jukka) and I hope that this will the case, in any case Sure - that's also possible by sharing code, for example by giving write access to both Chemistry and OpemCMIS committers to some part of each other's code repository. I'd much prefer having a single project, as I said before, but two projects that collaborate on common parts (like a test suite I imagine) can work as well. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] OpenCMIS incubator for Content Mangement Interoperability Services (CMIS)
OK, I personally believe this is in contradiction with the first commandment of the Apache Way: "*Community over Code* is a frequent saying that exemplifies ASF projects. Community uses Openness and Merit, expressed through Collaborative and Consensus driven work, to build lasting projects that use a Pragmatic License. While a diverse community is a requirement for every ASF project, we also expect people to contribute as Individuals, and wear appropriate Hats." -> Let our Apache Foundation overlords decide. I still think that at least there should be common code (ex: constants, as suggested by Jukka) and I hope that this will the case, in any case. S. On Dec 11, 2009, at 11:18 PM, Michael Wechner wrote: Florian Müller wrote: Well, here is a citation from http://www.apache.org/foundation/how-it-works.html (section "The Foundation Incubator"): "It must be noted that the incubator (just like the board) does not perform filtering on the basis of technical issues. This is because the foundation respects and suggests variety of technical approaches. It doesn't fear innovation or even internal confrontation between projects which overlap in functionality." right and as long as OpenCMIS fulfills the requirements of the incubator I don't see any reason why there shouldn't be two projects of the same topic. I also do not see any reason why OpenCMIS should be a sub-project of Chemistry. Give it a chance of its own within the current rules of the incubator and it will either work or not. If it works, then graduate, if not, then remove it. Or am I missing something which violates any current rule of the incubator? Cheers Michael Florian -Original Message- From: Stefane Fermigier [mailto:s...@nuxeo.com] Sent: Friday, December 11, 2009 7:46 PM To: chemistry-...@incubator.apache.org Cc: Incubator-General Subject: Re: [PROPOSAL] OpenCMIS incubator for Content Mangement Interoperability Services (CMIS) On Dec 11, 2009, at 7:10 PM, Florian Müller wrote: Chemistry uses Abdera to communicate with the server while OpenCMIS is based on JAX-B and some CMIS specific XML coding. I've been personally asking myself recently wether it would be feasible to drop Abdera in favor of JAXB in Chemistry, so IMHO it's something that should be discussed together and not a division line for us. There is a lot of code sharing between the AtomPub and the Web Services binding. (I couldn't find a Web Services client in Chemistry. It would be great if you could contribute one. Here we are with a working code base that we cannot give up and that we will maintain in the future for obvious reasons. Our idea was to make it Open Source and let others benefit from our work. Apache seemed to be the right place - at least three days ago. OK, I'm new to this Apache thing, but I don't believe this is the Apache Way. See: http://theapacheway.com/ or http://www.slideshare.net/jaaronfarr/the-apache-way-hk-sfd-2009 S. -- Stefane Fermigier, Founder and Chairman, Nuxeo Open Source, Java EE based, Enterprise Content Management (ECM) Web: http://www.nuxeo.com/ - Tel: +33 1 40 33 79 87 New: follow me on Twitter: http://twitter.com/sfermigier - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Stefane Fermigier, Founder and Chairman, Nuxeo Open Source, Java EE based, Enterprise Content Management (ECM) Web: http://www.nuxeo.com/ - Tel: +33 1 40 33 79 87 New: follow me on Twitter: http://twitter.com/sfermigier - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
