Difference between revisions of "Category:Developers"
Jump to navigation
Jump to search
| Line 24: | Line 24: | ||
* [[CVS Repositories]] |
* [[CVS Repositories]] |
||
* [[CVS Branching]] |
* [[CVS Branching]] |
||
| − | * [[Distribution]] |
||
| + | * [[Preparing a release for distribution]] ([[Tarballs|Making tarballs]]) |
||
| − | * [[Tarballs]]--see [[Distribution]] |
||
* [[Bugzilla user list pruning]] |
* [[Bugzilla user list pruning]] |
||
Revision as of 22:04, 6 August 2008
Contents
Developing for WeBWorK
These articles will help you modify WeBWorK and contribute to its development.
- Coding Standards
- Setting up a Development Server
- openwebwork-devel — Discussion of WeBWorK development, searchable archives.
- openwebwork-cvs — CVS commit notifications, searchable archives.
Adding WeBWorK questions to the National Problem Library (NPL)
For those who have commit privileges to the NPL.
CVS
Administrative tasks
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
Design/Implementation Notes
- Wishlist
- 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
- Hierarchical problem sets ideas
- Technical design philosophy for WeBWorK — Old, but still good for inspiration or laughs.
Subcategories
This category has the following 8 subcategories, out of 8 total.
A
D
G
L
R
T
V
W
Pages in category "Developers"
The following 62 pages are in this category, out of 62 total.
C
- CheckAnswers SubmitAnswers design
- Coding Standards
- Collecting metadata tools
- Configuration
- Contribute To WeBWorK
- Converting the webwork database from the latin1 to the utf8mb4 character set
- Create WeBWorK Amazon Machine Image (AMI) File
- Create WeBWorK LiveDVD
- Create WeBWorK Virtual Machine (.OVA) File
- CVS Branching
- CVS Commit Access
- CVS Repositories
