Participation and Funding

Participation Model

Each participating institution must:

  • Contribute member dues to our fiscal agent.
  • Have a designated contact person for CLAMP.
  • Be willing to support the community ideals of open source by sharing documentation, code, and expertise as able.

Each participating institution could contribute to our collaborative effort through any of the following:

  • Contributing additional funding above the minimum required member dues.
  • Sending a programmer to a Hack-Doc event.
  • Sending an Instructional Technologist to a Hack-Doc event.
  • Contributing to testing, planning, and prioritizing discussions and activities.
  • Sharing documentation, code, and experience.
  • Sharing a campus resource for use by the CLAMP community, e.g., listserv, development server.
  • Providing direct assistance to another member institution.
  • Taking responsibility for a block, module, code fix, etc. that the group generally uses, to assure its viability in future versions.
  • Vote and actively participate in discussions to get functionality integrated into Moodle core.
  • Contributing to documentation and coding work between Hack-Doc events.
  • Serving on the CLAMP working committees.
  • Hosting a Hack-Doc event.

Each participating institution should:

  • Consider maintenance strategies that keep current with supported versions of Moodle. A list of supported versions of Moodle can be found here.
  • Test any materials and code from CLAMP before putting it into production to verify that CLAMP products conform to your institution’s environment.

Each participating institution may:

  • Freely use, modify, and distribute any of the materials and code generated through our collaborative effort.
  • Suggest changes, direction, strategies, priorities, etc. for the group as a whole.
  • Share research and data from CLAMP within your institution.

Funding Model


Each participating institution will be asked to contribute member dues, currently set at $300, to a general fund each year. The member dues amount is reviewed by the steering committee annually and set based on the following expenditures.


  1. Shared server resources such as Redmine, web space, test moodle instances, misc. materials.
  2. Software licenses and subscription fees as needed.
  3. Event costs, such as food for Hack/Doc fests.
  4. Potentially subsidizing steering committee meetings.
  5. Potentially subsidizing attendees to a Hack-Doc event from all interested participating institutions.
  6. Potentially subsidizing the attendance at a national conference of at least one presenter to disseminate our work

Accounting Mechanism

Lafayette College serves as the fiscal agent for CLAMP. Lafayette invoices member institutions for annual dues, which is deposited into a CLAMP-specific fund. This fund is used to pay for CLAMP expenses, including event costs, hosting fees, software licensing, and event reimbursements. If CLAMP receives a grant, Lafayette will administer the money.

There is an annual fiscal report of all income and expenses submitted to the steering committee, which will then publish a summary report for the CLAMP community.