[#148] Project categorization and transition rules
Project Types
Two types of projects are hosted by openehealth: private and public
- private are projects that are only visible to the members of the project and are generally used when a prioject is still in its early phases (internally refered to as incubation) or for doing experiments that might not necessarily end in public domain
- public are projects that are visible to the entire community and are open to membership applications from the contributer community. It is the responsibility of the project owner to control the membership and the access to the project
Requirements for changing the type of a project from private to public
- Project Definition (whitepaper or reference) is reviewed by the TAB
- Project is validated to be in the scope of the Foundation
- The project offers code under the Apache Software License 2
- The project adheres to the foundation package convention (prefixed by org.openehealth)
Project Statuses
During its lifecylte a project goes through the following 6 phases:
- planning
- pre-alpha
- alpha
- beta
- production/stable
- mature
Requirements for promoting a project from "beta" to "production/stable" state
- Code Quality
- Compliance to Coding conventions
- Enforcement of coding conventions by checkstyle
- Project Quality
- Sufficient Test Coverage (proposal is 70%)
- ASL 2 License Compliance
- Documentation Quality
- Design documentation
- Code documentation
- Usage tutorials or samples
- Identify interfaces of central interest
- Identify cross-cutting concerns
- Open eHealth Compliance Criteria
- Security
- Fit to other existing projects
- Presentation of the Project Owner
- current status of the project
- code review results (from indendependent peer)
Delete Page Lock Page Edit this pagePrint Version




