Difference between revisions of "Category:Developers"

From WeBWorK_wiki
Jump to navigation Jump to search
(Overhaul - remove many references to obsolete pages.)
 
(16 intermediate revisions by 6 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.
 
  +
=== Roadmap ===
* [http://lists.sourceforge.net/lists/listinfo/openwebwork-cvs openwebwork-cvs] {{--}} CVS commit notifications, searchable archives.
 
 
 
=== Roadmaps ===
 
* [[Roadmap]] created at code camp WeBWorK::Rochester June 2012
 
   
 
===The WeBWorK Open Problem Library (OPL) ===
 
===The WeBWorK Open Problem Library (OPL) ===
Line 21: Line 16:
 
This was was called the National Problem Library prior to WeBWorK version 2.5.0.
 
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_NPL |contributing to the OPL]]
+
* [[Contributing_to_the_NPL |contributing to the Open Problem Library]]
for those who have commit privileges.
 
   
 
* [[OPL3_Design_Notes]] - Design Notes for the OPL version 3.0
 
* [[OPL3_Design_Notes]] - Design Notes for the OPL version 3.0
   
  +
=== Git Hub ===
  +
The official WeBWorK code repository is at
   
  +
http://github.com/openwebwork
   
=== Git Hub ===
 
  +
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.
The latest of our repositories
 
   
The main "stable" Git Hub repository is at
+
For example, download the webwork2 repository using:
  +
git clone https://github.com/openwebwork/webwork2.git
  +
which will set up a local git repository.
   
http://github.com/openwebwork
 
  +
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
   
Download this repository using either of these commands
 
  +
The Open Problem Library repo is at:
git clone http://github.com/openwebwork # sets up a local git repository, this is recommended
+
* https://github.com/openwebwork/webwork-open-problem-library
svn checkout http://github.com/openwebwork # sets up a local svn repository. This is still being supported.
 
   
There are active experimental branch repositories at
 
  +
Very basic command list is at http://gitref.org/basic
   
* https://github.com/mgage (Michael Gage) and
 
  +
=== Localization/ Internationalization ===
* https://github.com/aubreyja (Jason Aubrey)
 
* https://github.com/whytheplatypus (David Gage)
 
   
An experimental Git Hub repository for the National Problem Library is at
 
  +
* [[Localization]]: follow link for instructions on helping with the translation effort
* https://github.com/jasongrout/webwork-national-problem-library
 
   
  +
=== Projects ===
   
Very basic command list is at http://gitref.org/basic
 
  +
=== Code camps ===
   
   
More on [[Version_Control]]
 
  +
====2013 ====
   
=== SVN ===
 
   
* [[Subversion]]
 
* [[Download from SVN]]
 
* [[SVN Commit Access]]
 
More on [[Version_Control]]
 
   
=== Administrative tasks ===
+
==== 2012 ====
   
These articles detail how we manage the WeBWorK development and release process.
 
   
* [[CVS Repositories]]
 
  +
{| class="wikitable"
* [[CVS Branching]]
 
  +
|-
* [[Preparing a release for distribution]] ([[Tarballs|Making tarballs]])
 
  +
| [[Code_Camps|WeBWorK_Raleigh]]
* [[Bugzilla user list pruning]]
 
  +
| March 8 - 10, 2013
* [[Create WeBWorK LiveDVD]]
 
  +
| ()
  +
|-
  +
| [[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])
  +
|}
   
=== 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. [[PGLabs|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 <code>make_label</code> 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]]
 
   
   

Latest revision as of 16: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.