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
