Contributor Model

Owned by ScottS
Last updated: Jan 27, 2009Version comment
2 min read

DRAFT

Individual and Institutional Contributions Not Hosted with JASIG Resources

Contributions that are not hosted on any JASIG resources are not endorsed or recognized by the CAS Steering Committee. As such, the CAS Steering Committee has no recommendations or control over how they are presented. The community would clearly encourage contributions, whether hosted on JASIG or not, conform to the hosted contributions recommendations in order to ease deployment.

The one exception is that if the CAS Steering Committee becomes aware of a non-hosted project that harms of the image of the JASIG CAS project, it may acknowledge the project and release a statement about it.

Individual and Institutional Contributions Hosted with JASIG Resources

JASIG and the CAS Steering Committee actively encourage individuals and institutions to contribute their customizations, add-ons, and modules to the general CAS community. One way to do this is to encourage these resources to be placed within the JASIG Subversion and Maven2 repository.

Contributions that are hosted on JASIG resources require the following:

  • Initial code review by community members
  • Analysis of conflict with existing contributions (and to determine possibility of merger)
  • At a minimum, wiki documentation
  • Packaged as a Maven2 module, if applicable.
  • Released by Maven2 repository (public repo, or JASIG repo), if applicable
  • Commitment to be responsive and maintain contribution, if necessary (prevents stale projects, forking, etc.)
  • Should not use the org.jasig.cas package name
  • Should be released under a license compatible with the CAS server distribution

Official JASIG Contributions included with Distribution

Contributions from non-core developers that request enhancements or changes to the featureset of CAS are required to go through the RFC Process and is governed by that process.

In addition, contributions are required to meeting the following requirements:

  • Should use the org.jasig.cas package name
  • Contributors should have signed the appropriate contributor agreements (individual and/or institutional)
  • Released under the same license as the JASIG Central Authentication Service
  • Packaged as a Maven2 module, if applicable, following the conventions of the other official CAS modules
  • Commitment to be responsive and maintain contribution, if necessary, or locate someone else that is willing to