I think it might help if we get a bit on the same page. Apache doesn't take over projects. Apache provides a framework for people involved in a project to create good releases and to build community.
Check out resources on the web. I just found this, for instance, which is by an Apache member. It provides a reasonable outline of things. http://www.slideshare.net/hemapani/introduction-to-open-source-apache-and-apache-way On Sat, May 9, 2015 at 1:28 PM, Stefan Reich < stefan.reich.maker.of....@googlemail.com> wrote: > If Apache is interested, I'd have the following offer: As far as I am > concerned, Apache can proceed in any way the like. You can subject the > language to an organisational process, install stewards, publish the > language and so on. The stewards don't even have to be or include me. :-) > > The one thing I require is that I retain the right to do the same thing - > publish and talk about the language by myself, call my products JavaX and > so on. > > So there might be a split, but I wouldn't even find that bad. > > If there is no split and we all collaborate - that is also acceptable. I > don't know if I want to be an official part of the ASF or so... that is why > I propose that other way of you actually doing what you want. > > Of course I always like to advise, but as I said, you as a foundation could > even "grab" the whole language and call it yours. I am a very open person. > > Tell me if and how you'd all like to proceed :-) >
