Apereo Incubation Exit Criteria Documentation
 | § | Description | Status (assigned to/due by or compliance notes) |
|---|---|---|---|
| 4.1.1 | All source code, project materials, and other distribution elements should be properly licensed with an approved outbound license. See “Apereo Licensing Policy” [http://www.apereo.org/licensing], as well as the requirements of the specific outbound license, for further details. | Project is Apache2 licensed. |
| 4.1.2 | Appropriate licensing/copyright assertions and other notices, included in the overall distribution, codebase, and individual source code headers should be in place. Details are in “Implementing the Apereo Licensing Policy”, as well as the specific outbound license. No license-incompatible 3rd party dependencies, and no unlicensed code/dependencies should be included or redistributed anywhere in the code base. |
| |
| 4.1.3 | Appropriate Contributor Agreements should be on file, including: Individual Contributor License Agreements (ICLAs) for all active/former contributors, Corporate Contributor License Agreements (CCLAs) for all employers with employees contributing, and Software License Grant Agreements (SGLAs) for any significant pre-existing bodies of work being contributed to the project. |
| |
| 4.1.4 | The project or community name should be checked for trademark issues. The Incubation Working Group will check project name against US patent and trademark. Descriptive names such as Calendar Portlet do not need to be checked. Following is the link for doing a trademark search with the US Patent and Trademark Office: http://tess2.uspto.gov. | US search for OR is clear. Steering Committee has determined to /wiki/spaces/OR2/pages/103503905 anyway. | |
| 4.2.a | The level of community involvement, including: What is the number of participants? What level of participation is there? What activities do participants undertake or what artifacts have they created?) | ||
| 4.2.b | The organization of the community, including: What roles are in place? Who occupies those roles? How do those roles interact among one another and with the community? | ||
| 4.2.c | The operation of the community, including: What activities/events/artifacts are created/managed by the project to foster participation and development? How are decisions made? | ||
| 4.3 | Governance: A project governance structure should be created to oversee the project. | Bill to draft PMC-like governance | |
| 4.4 | Standard voting practices have been adopted. | See 4.3 | |
| 4.5 | The project has adopted a conflict resolution policy. | See 4.3 | |
| 4.6 | Release plans are developed and executed in public by the committers. | Model CAS Roadmap? | |
| 4.7 | At least one release has occurred during the Incubation process. | Several releases of the OR1 series have been made. |
| 4.8 | Alignment & Synergy. The Incubating Project should consider the use of other Apereo software where appropriate, and develop synergistic relationship with other Apereo projects wherever mutually beneficial. Evidence of consideration or adoption should be noted. | ||
| 4.9.a | Infrastructure: A software versioning and revision system is in place | Versioning model could be covered by roadmap | |
| 4.9.b | Infrastructure: An issue tracking system is in place | ||
| 4.9.c | Infrastructure: Mailing lists or other clear communications channels have been created and publicised. | ||
| 4.9.d | Infrastructure: Future plans, directions and objectives are articulated in a readily accessible format | Draft based on OR2 work? Roadmap = path to get from current reality to OR-as-advertised (Data Flow) | |
| 4.9.e | Infrastructure: Project website is current, and contains instructions for installation and configuration | Draft based on OR2 work? Plus cleanup of existing "front page" |