Contact Guidelines

We have several software tools widely used by the NLP community. We try to provide support for users of our tools. However, it is often difficult to answer all of the incoming questions and to continue to do research and development at the same time. To make it easier to keep up with the incoming questions, it's great if you can also help us.

• The most important thing to do is to keep up with the current version of the software. We do our best to fix bugs as they are reported, and we request that everyone use the latest versions. Please do not request bug fixes for old versions.
• It is difficult to help people if we don't know what system or software version they are using. Please specify which operating system, Java version, and version of our software when you are asking a question.
• Often, when reporting an exception, users neglect to actually include the exception in question. If present, please make sure to include the full stack trace when sending in a message. Ideally, include the command line or code of yours which produces the error, including sample data needed to reproduce it. Problems that we can reproduce are the most likely to be fixed.
• Many frequently asked questions have answers already posted on either the web page for the tool in question, in the javadoc for that tool, in a FAQ page dedicated to that tool, in the mailing list archives, or on StackOverflow. Please search on Google or consult those pages first and ask for clarifications if needed.
• Finally, please post questions publicly to either Stack Overflow or our mailing lists rather than sending them directly to an individual.

Having said all that, here's where to ask questions:

Stack Overflow

Ask a question on Stack Overflow with the tag stanford-nlp. This is the best way to get a code question answered.

GitHub

For clear bugs in code, code enhancement requests, and (even better) pull requests, feel free to use the the Stanford CoreNLP GitHub. (It's a good fit for questions and bugs concerning the CoreNLP code, but not for general user and usage questions.)

Mailing Lists

parser-user@lists.stanford.edu	This is the best list to post to in order to ask questions, make announcements, or for discussion among parser users, including sentence structure related tools like tregex and Stanford Dependencies. Join the list via this webpage or by emailing parser-user-join@lists.stanford.edu. (Leave the subject and message body empty.) You can also look at the list archives.
parser-support@lists.stanford.edu	This list goes only to the parser maintainers. It's a good address for licensing questions, etc. For general use and support questions, you're better off joining and using parser-user. You cannot join parser-support, but you can mail questions to parser-support@lists.stanford.edu.
parser-announce@lists.stanford.edu	This list will be used only to announce new parser versions, so it will be very low volume (expect 1-3 messages a year). Join the list via this webpage or by emailing parser-announce-join@lists.stanford.edu. (Leave the subject and message body empty.)
java-nlp-user@lists.stanford.edu	This is the best list to post to in order to ask questions, make announcements, or for discussion among JavaNLP users. You have to subscribe to be able to use it. Join the list via this webpage or by emailing java-nlp-user-join@lists.stanford.edu. (Leave the subject and message body empty.) You can also look at the list archives.
java-nlp-support@lists.stanford.edu	This list goes only to the software maintainers. It's a good address for licensing questions, etc. For general use and support questions, please join and use java-nlp-user. You cannot join java-nlp-support, but you can mail questions to java-nlp-support@lists.stanford.edu.
java‑nlp‑announce@lists.stanford.edu	This list will be used only to announce new versions of Stanford JavaNLP tools, so it will be very low volume (expect 1-3 messages a year). Join the list via via this webpage or by emailing java-nlp-announce-join@lists.stanford.edu. (Leave the subject and message body empty.)