CLAMP Code Intake

Before submitting code for review to become part of the Liberal Arts Edition (LAE), you should make sure you’ve done the following:

  • Created a CLAMP account and gained access to our Redmine project management application.
  • Created a publicly-accessible git repository for your project. You should also have at least a passing familiarity with Git.
  • If this is a core bug or feature, you’ve reported it to the core Moodle tracker:

Once you’re ready, fill out our code intake form. This form asks a series of questions about your project to help give us a better idea of (1) what you’re doing and (2) how much assistance you need. Note that with code bugs or features CLAMP will try to have the fix integrated in core first, before including it in the LAE.

Once you’ve submitted the form, your request will be triaged by a member of the CLAMP Development Committee, who will create an integration issue in Redmine tracker and assign it to him or herself. He or she will then perform an initial review per the CLAMP Code Standards and Guidelines and identify areas which need improvement.

Once the outstanding issues are resolved the developer will assign a tester. The tester will evaluate the code’s functionality and verify that it works as advertised with no adverse effects on all affected versions.

Once testing is complete the developer will assign an integrator who will perform a final sanity check and then merge the code into the appropriate LAE releases.

In a nutshell:

  1. Create your project
  2. Submit the form
  3. Work with the developer to resolve the issues
  4. Assist the tester with evaluating your code
  5. Submit for integration