Contact Us

From WeBWorK
(Difference between revisions)
Jump to: navigation, search
(Created page with 'There are a number of ways to get in contact with people from the WeBWorK project. == == This is the primary support email address for questions about WeBWorK…')
Line 50: Line 50:

Revision as of 22:47, 13 April 2011

There are a number of ways to get in contact with people from the WeBWorK project.


This is the primary support email address for questions about WeBWorK. This address is most appropriately used for questions related to MAA hosting, but your message will be routed appropriately if sent to this address.


The WeBWorK forums are very active with questions of all sorts. Posting your question to the appropriate forum is usually the quickest way to get a reply. Discussions range from complete newbie getting started questions to advanced problem authoring and system administration questions.

The forums are described on this page. You can access them at

You must be a registered user of this wiki to post to the forums.

IRC Chat

The #webwork IRC (Internet Relay Chat) channel is the best form of real-time communication for discussion of or questions about WeBWorK. You will often find developers or other knowledgeable users who will be happy to answer any technical questions you may have about WeBWorK. Instructions for accessing #webwork are given at the page linked here.

Development Mailing Lists

We also have a number of development related email lists (described below) which you can subscribe to at

If you are interested in WeBWorK development, the most important to subscribe to is webwork-devel


For joining/initiating development related discussion (development of WeBWorK, that is). You'll also notice that there is a "Features/Development" Moodle forum. Generally, the moodle forum is for "high level" discussion, questions and comments about the WeBWorK development process, feature requests, etc. The mailing list is also used for this, but at its best discussion there is generally more geared toward technical discussion of specific programming issues that arise during development, discussion about how to address particular bugs, or how to best implement particular features. Also discussed are development policies, such as procedures for allocating commit access, etc.


This list, along with webwork-bugs, will help you keep track of WeBWorK development activity. The webwork-vcs list is for those who which receive email notifications of commits to the Subversion repositories. This is an announcement only list with reply-to: webwork-devel. Usually a few commits (=emails) a day. Generally more traffic in the summer than during the academic year.


To receive notifications of new bugs and notifications when a bug's status has been updated.

The bug-tracker is important to the development process. It the central to-do list of things to fix, things to improve, and things to implement. If you subscribe to this list, you'll receive an email whenever a bug is fixed, a bug is reported, a comment is made about a bug, a patch is submitted against a bug, etc.

One helpful activity would be to try to confirm new bug reports as they come in, especially about bugs in the NPL problems. If particular problem misbehaves for you as described in the bug report or if it doesn't, adding a comment to the bug saying as much will very much help to clarify the issue. But, you can only do that in real-time if you're keeping track of new bug reports!

Also, if you're in charge of a WeBWorK installation, it can be useful to know of problems you might (or might not) run into.

This is an announcement only list with reply-to: webwork-devel. This list currently has a lot of activity because Arnie and Mike's student Spyro is working hard this summer to fix the bugs filed against the problem libraries. Under normal circumstances you'll probably see at most a couple messages a week from this list.

If you subscribe either of these last two, you may also want to subscribe to webwork-devel in case you want to comment on an svn commit or discuss a bug.

follow us