Draft Policy for BeaverSource Last modified: 2008-06-06

BeaverSource Project Policy

BeaverSource will support projects that meet the following guidelines:

Project Owner

Each project will have a designated project owner who must be an OSU student or employee. The project owner is required to do the following:

  • Confirm that the project meets the guidelines on this page.
  • Respond to all inquiries and complaints about a project.
  • Control access to a project, and remove members who violate this policy.
  • Read email regularly.
  • When absent, designate an alternate to perform these tasks.

In the event a project is running without a project owner, BeaverSource Administration will contact the project and give a two week deadline to find a new owner or move the project to a different hosting solution. BeaverSource Administration will disable all projects that do not have a valid project owner.

Project Requirements

BeaverSource is intended to be a place to share open source code with the OSU community. The following are requirements for all projects:

  • Projects must comply with the OSU Acceptable Use Policy.
  • Projects must not be commercial in nature.
  • If code or other content is included from another source, use of that content must comply with the license under which it is published, and must not violate copyright law.
  • Content produced by OSU employees using OSU resources is property of the University and should be approved for publication on BeaverSource by the employee's supervisor. (See OSU Copyright Policy for more information.)

NOTE: BeaverSource Administration will disable any project that violates the above requirements.

Project Best Practices

We recommend the following for all BeaverSource projects:

  • Each project should be licensed under a well-recognized open source license. (See http://en.wikipedia.org/wiki/Open_source_license for some examples.) Choose your license carefully.
  • While BeaverSource does allow a range of access restrictions, we suggest you keep your project as open as possible to promote participation and code review.