Difference between revisions of "Category:Developers"

From WeBWorK_wiki
Jump to navigation Jump to search
m (fixed broken links)
(Overhaul - remove many references to obsolete pages.)
 
Line 9: Line 9:
 
* [[DevelopmentProcess]]
 
* [[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
 
 
* [[Roadmap Details]] about the backend of Webwork
 
   
 
===The WeBWorK Open Problem Library (OPL) ===
 
===The WeBWorK Open Problem Library (OPL) ===
Line 23: 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 ===
 
=== Git Hub ===
The latest of our repositories
 
  +
The official WeBWorK code repository is at
 
The main "stable" Git Hub repository is at
 
   
 
http://github.com/openwebwork
 
http://github.com/openwebwork
Line 43: Line 32:
   
 
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.
 
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.
+
Docker is a convenient environment for doing development work.
 
See:
 
See:
 
* https://github.com/openwebwork/webwork2/wiki/Docker-newbie-instructions
 
* 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:
 
The Open Problem Library repo is at:
 
* https://github.com/openwebwork/webwork-open-problem-library
 
* https://github.com/openwebwork/webwork-open-problem-library
 
   
 
Very basic command list is at http://gitref.org/basic
 
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]] ([[Tarballs|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. [[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/ Internationalization ===
   
 
* [[Localization]]: follow link for instructions on helping with the translation effort
 
* [[Localization]]: follow link for instructions on helping with the translation effort
** Ben Walter and Grant He have made significant progress on this.
 
   
 
=== Projects ===
 
=== 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]]
 
 
   
 
=== Code camps ===
 
=== Code camps ===

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.