JavaNLP meeting notes for 11/14/02

JavaNLP news:

* cvsweb is almost ready, stay tuned!

* new release script
  - run /u/nlp/java/release-javanlp-jar.sh to checkout and build a fresh
javanlp.jar for use in other projects.
  - The releases live in /u/nlp/java/release
  - /u/nlp/java/release/javanlp.jar is always a link to the latest version.
  - Run this when you've made/committed changes that others using your
JavaNLP code should have access to (i.e. since they may not all be
developing JavaNLP with cvs)

Advise for JavaNLP developers:

* be careful of permissions when you add new files (and especially dirs).
When in doubt, log onto an nlp machine and type "chmod -Rf 2775
/u/nlp/cvsroot/javanlp" to fix things.

* before committing new code, go to your main javanlp dir and do "make
clean" and then "make" to ensure that other people will be able to compile
your code. Make sure you've added any new java files you created to cvs.

* before committing new code, do "make jdoc" and check for any javadoc
warnings. Fix them before committing.

Progress this week:

* initial implementation of classifier API and logistic regression
implementation
* misc minor improvements and javadocs to various packages

Tasks for next week:

Dan:
- package docs for classification, classification.internal,
parser.oldparser, and stats
- external classify interface
- move classify package to classify.old
- move classification package to classify
  - make sure permissions don't get messed up! :)
- naive bayes implementation

Kristina:
- package docs for mt and redwoods
- classify experiments classes

Sep:
- finish converting document to use meta-data
- update processor api to use documents with meta data

Joris:
- work with tim on ie.pcfg code

Joseph:
- finish getting cvsweb running
- teach people more cvs tricks
- work with Huy on HMM code

Huy:
- hmm stuff


Please send email to the javanlp list (or the guilty parties if you know who
they are) if you encounter build/permission/javadoc errors. Also--remember
by next Tuesday to email me with what you got done and any problems/ideas
for the meeting.

Thanks, js