Hi Shann, Thank you for reaching out! If your goal is to get your project integrated into Apache Nutch, proper, then I would recommend simply:
0. File some JIRA issues in Apache Nutch http://issues.apache.org/jira/browse/NUTCH Small incremental patches and issues are preferred and this will let people know what your plan is so you can get committers and PMC members attention. 1. svn co http://svn.apache.org/repos/asf/nutch/branches/2.x/ 2. cd 2.x 3. Edit files 4. svn status (make sure the files you edited looked correct) 6. svn diff > NUTCH-xxx.sleduc.yyMMdd.patch.txt for each issue you created 7. Attach patches from #6 to issues from #1 Otherwise if you go off onto Github, and work it's going to be harder to get your patch accepted since it will represent large change when instead you can effect the change here at the ASF, incrementally making sure your code gets in. ALv2 is the license to use, BTW, either way you decide. Cheers, Chris On 2/12/13 12:25 PM, "Shann" <[email protected]> wrote: >Hi, >Part of my internship, we must develop a specialized search engine using >Nutch, Solr, HBase, Tika. > >I began to develop a Java application for crawler with Nuth branch 2.x. > >Functions inject, generate, fetch, parse, updatedb, solrindex based on the >actual execution of nutch via a shell command from Java application. > >As an advocate of free software, I propose therefore to give you access to >my git project. > >Using nutch in the background, under what license should I put my >application ? > > > >-- >View this message in context: >http://lucene.472066.n3.nabble.com/Nutch-JAVA-Application-tp4040050.html >Sent from the Nutch - Dev mailing list archive at Nabble.com.
