Get Involved

If you are interested in becoming a member of CLAMP the participation and funding models that follow will give you a general idea of how we have structured our collaboration.

Once you have read it over, send questions to newquisk@lafayette.edu or go ahead and join us:

Participation Model

Each participating institution will contribute the minimum amount set by the steering committee annually to our collaboration. For 2012-2013 this figure will be $300 and will cover operating costs only, not reimbursement for Steering Committee meetings or Hack-Doc attendance.

Each participating institution must:

  • Contributing the minimum required funding 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 can contribute to our collaborative effort through any of the following:

  1. Contributing additional funding to a general pool, above the minimum required.
  2. Sending a PHP programmer to a Hack-Doc event
  3. Sending an Instructional Technologist to a Hack-Doc event
  4. Having people (programmers, technologist, faculty, students) available at their home institution during a Hack-Doc event
  5. Contributing to testing, planning and prioritizing discussions and activities.
  6. Sharing documentation, code and experience
  7. Sharing a campus resource for use by the CLAMP community, ex. listserv, development server
  8. Providing direct assistance to another institution
  9. Taking responsibility for a block, module, code fix, etc. that the group generally uses, to assure it’s viability in future versions
  10. Vote and actively participate in Moodle.org discussions to get functionality integrated into core
  11. Contributing to documentation and coding work between Hack-Doc events
  12. Serving on the CLAMP working committees
  13. Hosting a Hack-Doc event

Each participating institution should:

  1. Provide regular information regarding your instance and use of Moodle, by running the census module and responding to questionnaires.
  2. Consider maintenance strategies that keep you reasonably current with the CLAMP version of Moodle. (Liberal Arts Edition)
  3. Test any materials and code from CLAMP fully, before putting it into production to verify that CLAMP products conform to your institution’s environment.

Each participating institution may:

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

The Steering Committee

  1. Is made up of seven members, representing seven North American four year, residential, liberal arts colleges as geographically diverse as possible.
  2. Membership is rotated over three years (2-2-3). The first rotation will take place June 2010. Members will serve three year terms.

The Steering Committee will:

  1. Make final decisions regarding direction, priorities and focus with input from CLAMP members
  2. Administer any general fund, policy decisions and necessary overhead
  3. Maintain community tools such as discussions, blogs, wikis, code repository, test server etc.
  4. Publicize the finished product of any project within CLAMP
  5. Coordinate our efforts with the larger Moodle.org community
  6. Meet regularly via web conferencing and occasionally via video conferencing or in person.
  7. Be responsible for the CLAMP funding model including membership fees and grant applications

Funding Model

Contributions

  1. Each participating institution will be asked to contribute a specific amount to a general fund each year. The specific amount will be reviewed by the Steering Committee annually, based on expenses such as license fees, shared server space and subsidizing Hack-Doc and Steering Committee attendance.
  2. Some institutions may decide to contribute additional funds, perhaps in lieu of providing personnel or hosting an event, but no institution would be required to contribute more than the minimum amount set by the Steering Committee.

Expenditures

  1. Shared server resources such as Redmine, web space, test moodle instances, misc. materials
  2. Software licenses and subscription fees as needed
  3. Potentially subsidizing 1 – 2 Steering Committee meetings per year.
  4. Potentially subsidizing attendees to a Hack-Doc event from all interested participating institutions
  5. Potentially subsidizing the attendance at a national conference of at least one presenter to disseminate our work

For the 2012 – 2013 fiscal year each institution will be asked to contribute $300.

This level of funding, assuming approximately fifteen member institutions, would fund our basic operating expenses, such as clamp-it.org, the code repository and licensing fees.

Higher levels of participation would allow us to begin to subsidize CLAMP events.

Accounting Mechanism

Lafayette will serve as the fiscal agent for CLAMP. Institutions will write $300 checks to Lafayette which will be deposited into a CLAMP-specific fund. This fund will be used to pay for CLAMP expenses, including hosting fees, software licensing and event reimbursements. If CLAMP receives a grant, Lafayette will administer the money.

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