Difference between revisions of "Category:Developers"

Mailing Lists

Mailing Lists of interest to developers.

Developing for WeBWorK

These articles will help you modify WeBWorK and contribute to its development.

• DevelopmentProcess
• Coding Standards
• Setting up a Development Server

• openwebwork-devel — Discussion of WeBWorK development, searchable archives.

Roadmaps

• Roadmap created at code camp WeBWorK::Rochester June 2012

• Roadmap Details about the backend of Webwork

The WeBWorK Open Problem Library (OPL)

This was was called the National Problem Library prior to WeBWorK version 2.5.0.

• Contributing to the Problem Library - there are instructions for contributing to the OPL

for those who have commit privileges.

• OPL3_Design_Notes - Design Notes for the OPL version 3.0

Git Hub

The latest of our repositories

The main "stable" Git Hub repository is at

http://github.com/openwebwork

Under that page you will find several repositories, in particular those for webwork2 and pg (the main system code) and webwork-open-problem-library with the OPL.

For example, download the webwork2 repository using:

git clone https://github.com/openwebwork/webwork2.git

which will set up a local git repository.

If you intend to contribute code, create a fork on GitHub, push your code to a feature branch on your fork and make a pull request. See:

• https://github.com/openwebwork/webwork2/wiki/First-Time-Setup
• https://github.com/openwebwork/webwork2/wiki/Coding-and-Workflow
• and other pages in the GitHub wiki.

We recommend that developers consider using Docker when doing development work. See:

• https://github.com/openwebwork/webwork2/wiki/Docker-newbie-instructions

There are active experimental branch repositories at several of the forks including:

• https://github.com/mgage (Michael Gage)
• and those of other currently active developers.
• Checking the authors of recent pull requests is a good method to look for who is actively contributing.

The Open Problem Library repo is at:

• https://github.com/openwebwork/webwork-open-problem-library

Very basic command list is at http://gitref.org/basic

Administrative tasks (historical )

These articles detail how we manage the WeBWorK development and release process.

• CVS Repositories
• CVS Branching
• Preparing a release for distribution (Making tarballs)
• Bugzilla user list pruning
• Create WeBWorK LiveDVD

Design/Implementation Notes

• 2009_03_tasks Notes on projects for summer 2009 from March web-conference
• AIM07/Working_Groups Notes from the August 2007 AIM workshop
• Wishlist
• Google_summer_of_code_projects
• GUI Toolkit Ideas
• PGLanguageV2 — An idea for a markup-oriented approach to PG. No code yet. (cf. PGML.)
• WeBWorK as a web service
• Problem editor ideas
• HomeworkSetEditorIdeas — Ideas for a new Homework Set Editor.
• Hierarchical problem sets ideas
• Technical design philosophy for WeBWorK — Old, but still good for inspiration or laughs.

Localization/ Internationalization

• Localization: follow link for instructions on helping with the translation effort
  • Ben Walter and Grant He have made significant progress on this.

Projects

• ModernPerl -- Updating the perl coding style

• Configuration
• Improving the NPL
  • Collecting metadata tools
• Accessibility
  • Grant He has begun to write tools to make writing accessible HTML code easier. He is starting with a make_label subroutine.
• PG language enhancements
• Unit Testing Create automated tests to insure that WeBWorK is configured and functioning properly.
• LMS integration
  • Blackboard
  • Moodle Integration
  • Moodle 2.0
• Whiteboard
  • Aaron Wangberg
• Adaptive learning
  • Aaron Wangberg
  • Ken Appel
• Sage in WeBWorK
  • Jason Aubrey
  • John Travis
• Discussion Problems
  • John Travis

For WeBWorK Consultants

• WeBWorK Consultants, Workshops and Training Sessions
• Documentation for WeBWorK Consultants

Code camps

2013

2012