Difference between revisions of "Category:Developers"

From WeBWorK_wiki
Jump to navigation Jump to search
(→‎Git Hub: several revisions/explanations)
 
Line 37: Line 37:
 
http://github.com/openwebwork
 
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.
   
Download this repository using either of these commands
 
  +
For example, download the webwork2 repository using:
git clone http://github.com/openwebwork # sets up a local git repository, this is recommended
+
git clone https://github.com/openwebwork/webwork2.git
svn checkout http://github.com/openwebwork # sets up a local svn repository. This is still being supported.
+
which will set up a local git repository.
   
There are active experimental branch repositories at
 
  +
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.
   
* https://github.com/mgage (Michael Gage) and
 
  +
We recommend that developers consider using Docker when doing development work.
* https://github.com/aubreyja (Jason Aubrey)
 
  +
See:
* https://github.com/whytheplatypus (David Gage)
+
* https://github.com/openwebwork/webwork2/wiki/Docker-newbie-instructions
   
An experimental Git Hub repository for the National Problem Library is at
 
  +
There are active experimental branch repositories at several of the forks including:
* https://github.com/jasongrout/webwork-national-problem-library
 
  +
  +
* 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
   
   

Latest revision as of 16:37, 12 February 2020

Mailing Lists[edit]

Mailing Lists of interest to developers.

Developing for WeBWorK[edit]

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

Roadmaps[edit]

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

The WeBWorK Open Problem Library (OPL)[edit]

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

for those who have commit privileges.


Git Hub[edit]

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:

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

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:


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


More on Version_Control

SVN (obsolete -- use github)[edit]

More on Version_Control

Administrative tasks (historical )[edit]

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

Design/Implementation Notes[edit]

Localization/ Internationalization[edit]

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

Projects[edit]

For WeBWorK Consultants[edit]


Code camps[edit]

2013[edit]

2012[edit]

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 5 subcategories, out of 5 total.

D

R

T

V

W