70 · Representative Documents: OSS Contributor Agreements
UNIVERSITY OF CALIFORNIA
Guidelines for Contributing to Open/Community Source Software
8/26/2012 Page 1 of 4
UNIVERSITY OF CALIFORNIA GUIDELINES
FOR CONTRIBUTING TO
OPEN/COMMUNITY SOURCE SOFTWARE
The University of California not only uses Open Source Software and Community Source Software (O/CSS) in
furtherance of its mission, in a growing number of cases the University also contributes code back to those
O/CSS communities. Benefits accrue to the University as a result of making such contributions, but in doing so
the University takes on certain associated responsibilities.
The purpose of this document is to:
• Summarize the rights and responsibilities associated with O/CSS contributions made on behalf of the
• Provide guidelines by which the University can most effectively and appropriately evaluate and manage
making such contributions, taking into account pertinent licensing, technical, intellectual property, legal,
policy and cost/benefit issues; and
• Identify organizations, roles and responsibilities pertinent to the implementation and management of the
guidelines outlined herein.
These Guidelines apply to:
• All Open Source Software and Community Source Software (as defined in Section III below) used by
the University of California;
• All software code that has been created by, or on behalf of, the University of California, that is based
upon and intended to correct, modify or enhance existing O/CSS software code, and which the
University of California determines is in its best interest to contribute to that O/CSS community;
• All employees, including student, part-time and temporary employees;
• All departments and organizations of the University of California; and
• All third parties whose conduct, in the performance of their work for the University of California, is under
the control of the Regents of the University of California.
Community Source Software (CSS), as used in these Guidelines, means a software model that blends
elements of directed development, in the classic sense of an organization employing staff and resources to work
on a project, and the openness of traditional Open Source Software projects.
License, as used in these Guidelines, means a contract in which a copyright owner grants to another
permission to exercise one or more of their rights under copyright.