Non-partner participation

Owned by Bill Branan
Jun 16, 2017
2 min read

DRAFT description of non-partner participation

In general, the partners prefer that organizations will contribute as described in the Shared IR "Process" and "Roles" section. However, we recognize that while some organizations are not ready to become partners, non-partner contributions are extremely valuable.  So, anticipating that other individuals and institutions may be interested in contributing, additional categories of participation and participation requirements will be defined here.

Developers from non-partner organizations

Programmers from non-partner organizations who wish to contribute directly to the technical development of the Curate software must meet the following requirements and follow these steps. To participate in prioritization and feature story creation we encourage non-partner contributors to explore becoming full partners on the project ( Hydramata Project).

  1. The developer must meet all the baseline requirements for participation in a Hydra project: they must understand and accept the Hydra Community Principles, the specific guidelines for Developers, and have completed and submitted a valid contributor license agreement(s) per the documentation at Samvera Community Intellectual Property Licensing and Ownership. They must have access to sufficient computing and networking resources to effectively contribute.
  2. The project Tech Lead must verify that the developer has the skills and resources needed to be an effective contributor to the project.
  3. The Lead Product Owner and Scrum Master must confirm that they have spoken with the developer and have reviewed the goals of the project and expectations of team members
  4. The Tech Lead and Lead Product Owner will communicate their recommendations to the Project Directors group, including a suggested start date for the new member. The Project Directors will approve (or reject) the addition. The Lead Project Director can act for the group in time-sensitive situations.
  5. The new developer must go through an onboarding process defined and managed by the Scrum Master and Lead Product Owner, in conjunction with the Tech Lead.

This arrangement will be reviewed periodically and adjustments made as needed.