Difference between revisions of "Category:Developers"

From WeBWorK_wiki
Jump to navigation Jump to search
(Overhaul - remove many references to obsolete pages.)
 
(50 intermediate revisions by 8 users not shown)
Line 7: Line 7:
 
These articles will help you modify WeBWorK and contribute to its development.
 
These articles will help you modify WeBWorK and contribute to its development.
   
  +
* [[DevelopmentProcess]]
 
* [[Coding Standards]]
 
* [[Coding Standards]]
* [[Setting up a Development Server]]
 
* [http://lists.sourceforge.net/lists/listinfo/openwebwork-devel openwebwork-devel] {{--}} Discussion of WeBWorK development, searchable archives.
 
* [http://lists.sourceforge.net/lists/listinfo/openwebwork-cvs openwebwork-cvs] {{--}} CVS commit notifications, searchable archives.
 
   
===Adding WeBWorK questions to the National Problem Library (NPL) ===
 
  +
=== Roadmap ===
   
  +
===The WeBWorK Open Problem Library (OPL) ===
   
There are instructions for
 
  +
This was was called the National Problem Library prior to WeBWorK version 2.5.0.
[[Contributing_to_the_NPL |contributing to the NPL]]
 
for those who have commit privileges.
 
   
=== SVN ===
 
  +
* [[Contributing_to_the_NPL |contributing to the Open Problem Library]]
   
* [[Subversion]]
 
  +
* [[OPL3_Design_Notes]] - Design Notes for the OPL version 3.0
* [[Download from SVN]]
 
* [[SVN Commit Access]]
 
   
=== Administrative tasks ===
+
=== Git Hub ===
  +
The official WeBWorK code repository is at
   
These articles detail how we manage the WeBWorK development and release process.
 
  +
http://github.com/openwebwork
   
* [[CVS Repositories]]
 
  +
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.
* [[CVS Branching]]
 
* [[Preparing a release for distribution]] ([[Tarballs|Making tarballs]])
 
* [[Bugzilla user list pruning]]
 
* [[Create WeBWorK LiveDVD]]
 
   
=== Design/Implementation Notes ===
 
  +
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.
  +
  +
Docker is a convenient environment for doing development work.
  +
See:
  +
* https://github.com/openwebwork/webwork2/wiki/Docker-newbie-instructions
  +
  +
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
  +
  +
=== Localization/ Internationalization ===
  +
  +
* [[Localization]]: follow link for instructions on helping with the translation effort
   
* [[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. [[PGLabs|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.
 
 
=== Projects ===
 
=== Projects ===
* Localization
 
=== For WeBWorK Consultants ===
 
   
* [[WeBWorK Consultants, Workshops and Training Sessions]]
 
  +
=== Code camps ===
* [[Documentation for WeBWorK Consultants]]
 
  +
  +
  +
====2013 ====
  +
  +
  +
  +
==== 2012 ====
  +
  +
  +
{| class="wikitable"
  +
|-
  +
| [[Code_Camps|WeBWorK_Raleigh]]
  +
| March 8 - 10, 2013
  +
| ()
  +
|-
  +
| [[Code_Camps|WeBWorK_Fitchburg]]
  +
| October 12 - 14, 2012
  +
| ([http://michaelgage.blogspot.com/2012/10/the-webworkfitchburg-code-camp-took.html#more blog post])
  +
|-
  +
| [[Code_Camps|WeBWorK_Winona]] || August 5 - 8, 2012
  +
| ([http://drjt7.blogspot.com/2012/08/webworkwinona-gets-underway-its-sunday.html photo])
  +
|-
  +
| [[Code_Camps|WeBWorK_Clinton]] || June 20 - 22, 2012
  +
| ([http://drjt7.blogspot.com/2012/06/webworkclinton-2012-this-webwork-users.html blog spot])
  +
|-
  +
| [[Code_Camps|WeBWorK_Rochester]] || June 6 - 9, 2012
  +
| ([http://michaelgage.blogspot.com/2012/06/summary-for-webworkrochester2012.html#more blog post])
  +
|}
  +
  +
  +
  +
  +
  +
  +
  +
   
   

Latest revision as of 15:33, 31 March 2023

Mailing Lists

Mailing Lists of interest to developers.

Developing for WeBWorK

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

Roadmap

The WeBWorK Open Problem Library (OPL)

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

Git Hub

The official WeBWorK code 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.

Docker is a convenient environment for doing development work. See:

The Open Problem Library repo is at:

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

Localization/ Internationalization

  • Localization: follow link for instructions on helping with the translation effort

Projects

Code camps

2013

2012

WeBWorK_Raleigh March 8 - 10, 2013 ()
WeBWorK_Fitchburg October 12 - 14, 2012 (blog post)
WeBWorK_Winona August 5 - 8, 2012 (photo)
WeBWorK_Clinton June 20 - 22, 2012 (blog spot)
WeBWorK_Rochester June 6 - 9, 2012 (blog post)

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.