Hi, a) is GORA ASL licensed? >
it is. see http://github.com/enis/gora/blob/master/LICENSE.txt > b) what's the maintenance plan for GORA? Will it continue to live in > Github? Will you guys propose it into the Apache Incubator as an ASF > project? > I confirm that the plan is definitely to move it to the incubator or possibly as a Hadoop subproject. > > (a) svn copy NutchBase from GitHub to the nutchbase branch in > http://svn.apache.org/repos/asf/nutch/branches/nutchbase bringing the ASF > branch up to date. > this seems like an unnecessary step. There has been an enormous amount of changes between the nutchbase branch and the version on GitHub - pretty much EVERY class has been modified + a lot of classes have been removed etc... the nutchbase branch on svn is completely obsolete so I suggest that simply get rid of the nutchbase branch and move the code to trunk directly (after doing c below of course) > (b) Once the GORA license issues are figured out (they must be > compatible with the ASF or we cannot use it), then we update Nutch to > depend > on the GORA jars via Ivy? > see comment above about the license. > (c) svn tag current Nutch trunk as 1.2-branch > (d) svn merge nutchbase branch with nutch trunk > see above > (e) roll the version # in nutch trunk to 2.0-dev > (f) all issues in JIRA should be updated to reflect 2.0-dev fixes where > it makes sense > (g) a 2.1 version is added to mark anything that we don't want in 2.0 > and we file post 2.0 issues there > (h) Nutch 2.0 trunk is fixed, and brought up to speed and old code is > removed. All unit tests should pass regression where it makes sense. > (i) Nutch documentation is brought up to date on wiki and checked into > SVN > (j) We roll a 2.0 release > OK with everything else Julien -- DigitalPebble Ltd Open Source Solutions for Text Engineering http://www.digitalpebble.com
