Very, very barebones site is now live on http://incubator.apache.org/opennlp/
-Grant On Dec 4, 2010, at 2:40 PM, Thilo Goetz wrote: > On 12/4/2010 20:35, Jason Baldridge wrote: >> Okay, I can be on board with this. Perhaps we just need to provide a "if you >> only want maxent" instruction in the documentation. If it seems we need to >> decouple the packages in the future, then we can do so. > > Absolutely. Also, at this point in the game, it's a bit > early to worry about those details, imho. The svn layout > is orthogonal to the release/distribution issue. > > We probably want to do a grand total release first of all, > so we clear all the legal hurdles. If later on we find > that we want to roll separate releases of individual > packages, we can always do that. Somebody just has to > step up and do the work :-) > > --Thilo > >> >> Jason >> >> On Sat, Dec 4, 2010 at 3:40 AM, Jörn Kottmann<[email protected]> wrote: >> >>> On 12/3/10 11:00 PM, Jason Baldridge wrote: >>> >>>> I think it is more of a conceptual thing. You download a package like >>>> maxent >>>> so you can build models for your own prediction task, and it would be nice >>>> to not have lots of extra documentation and such getting in the way of >>>> understanding how to get up and running with the software, etc. I just >>>> think >>>> it makes sense as a separate release unit that the OpenNLP toolkit depends >>>> on without swallowing it whole. >>>> >>>> >>> I clearly disagree here. Having a separate maxent distribution maybe a >>> little more convenient >>> for maxent only users, but it has other disadvantages. >>> >>> To release the tools project we would have to release maxent always before >>> which >>> will add a two - three week delay for every tools project release which >>> depends on the maxent change. >>> Its also more work to release one more item. >>> Its also more overhead from the project structure, we need a separate >>> documentation project >>> for maxent, etc. Do you also want a separate website for maxent ? >>> The testing is also tangled, there are no good tests for maxent, expect the >>> quite >>> extensive regression test we do for the tools. In the end both projects >>> must be >>> ready for release, and maxent can not be really released separately. >>> In practice I think it means that we have usually to release both at the >>> same time, >>> expect for smaller minor fixes. >>> >>> Jörn >>> >>> >> >> > -------------------------- Grant Ingersoll http://www.lucidimagination.com
