I was waiting for you to respond as its your baby :-) While Sonatype helped pay for some of the work in the last stage of NARs development, our focus has really been on Java so we really haven't had much time in the last few years. That said with all the work Sonatype has been doing with Insight we get questions about native code and mobile development for the iPhone quite a bit.
I am happy if there are users contributing and you want to coalesce the fragmented implementations. I think that Github is the perfect place to do that right now, low barrier to working together and it's very easy to get a project into Central regardless of where it is. That you as users, who became developers, have come together to put NAR back together is the only key element required to make the project successful. No organization will make your project popular, usable or help it improve. It is the work of small interested individuals that make the difference. That said if you were going to take it to a foundation, in the long run I would take it to the Eclipse Foundation. They have just converted the whole platform build to Maven and there is a large native component to that for SWT and the launchers. Redhat has done a lot of the work there lately and I'm sure they would be interested as they do their own builds of the Eclipse Platform for their users and customers. I happy to talk any of the groups as Sonatype would have to make a donation of code to move it to a foundation, but honestly I really think Github is the best place for you to spark up the project again. On Oct 7, 2012, at 6:58 AM, Mark Donszelmann <mark.donszelm...@gmail.com> wrote: > Hi > > I am the author of the maven-nar-plugin. Let me start by apologizing that I > have not kept track of, neither have worked on > it in recent years. I moved on to other things, but may come back using / > working on it later on. > > The nar plugin was created by me when I was working at Stanford Linear > Accelerator Center (SLAC) for Maven 1. When Maven 2 > came out I rewrote it, and that is the code that is still there. Inside SLAC > we maintained Open Source code by High Energy Physicists > under the name FreeHEP, available to anyone. A thing such as git or github > did not exist at the time, so we needed > a way to distribute out code, and a name for it. > > I think it would be a good idea if you guys pick up the parts and continue > with it. I have no real time to work on it, but could answer questions > if you have any. > > You have my agreement, and SLAC already gave its > agreement for me to take the code away from them. I guess officially Sonatype > owns the code, as I dropped it with them, but > they seem to have little interest in it (as far as I could see from the > mailings). > > Keep me posted. > > Regards > Mark Donszelmann > > > On Oct 7, 2012, at 12:35 PM, Martin Eisengardt <martin.eisenga...@gmail.com> > wrote: > >> Do we actually need the agreement of all authors to become a maven core >> project? >> The sources are already licensed under terms of ASF. >> >> The original authors seem not respond for months or the email addresses are >> no longer valid. >> Would it be fine if there is a new (active) project group filling up the >> CLA? http://www.apache.org/licenses/#clas >> Actually duns code is not the original code. There was some other author >> (freehep). >> >> For me personally I do not care if this is becoming a maven-ocre component >> or not. I am fine with codehaus and other variants too. My personal >> interest is to remove all the forks and having an active project roup I can >> discuss and commit my work :) >> >> >> On Sun, Oct 7, 2012 at 12:23 PM, Jörg Schaible <joerg.schai...@gmx.de>wrote: >> >>> Hi, >>> >>> Benson Margulies wrote: >>> >>>> Adding plugins to the core is not so much a matter of 'strategy'. >>>> >>>> The nar plugin is a non-trivial amount of code. So, for it to come to >>>> Apache, it would have to pass IP clearance. That means understanding >>>> the provenance of all of the code and that the people contributing it >>>> have sufficient rights to grant a license to the ASF. >>>> >>>> That having been said, the existing Maven community is rather thinly >>>> spread across the many org.apache.maven.plugins. Adding another big, >>>> complex, plugin should, at least, lead to a pause for reflection. >>>> Nonetheless, If the authors are interested in contributing it, please >>>> join the dev list and start a discussion. >>> >>> another option is mojo.codehaus.org, especially since the devs discuss >>> about >>> moving the SCM for individual plugins to git. >>> >>> - Jörg >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >>> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder & CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl --------------------------------------------------------- We know what we are, but know not what we may be. -- Shakespeare
