...
Technical and release decisions for a project should be made by consensus of that the project’s Committers. If consensus cannot be reached, decisions are taken by majority vote of a project’s Committers. Committers may, by majority vote, delegate (or revoke delegation) of any portion of such decisions to an alternate open, documented, and traceable decision-making process.
...
- Code type: major delivery of a code-type project is code and document. It has one or a group of related functions functional codes (considering donators’ opinion). Projects targeting on integrations are considered code-type as well.
- Doc type: major delivery of a doc-type project is only document. Mostly requirement doc, architecture doc for the entire platform or a group of platform users.
2.3.3. Project Lifecycle
For XGVela projects, it means internal projects under XGVela follows the LFN Project Lifecycle process; found here: LFN Project Lifecyclecommunity. It follows the following lifecycle procedure.
Highlights:
| Project State | State Summary |
|---|---|
| none | Project does not exist or exists outside of LFN - including unfunded LF projectsXGVela. |
| SandboxAprroved | Project is reviewed and admitted to LFN but does not have direct funding from LFN. The intent is to enable new projects to gain visibility and participate in the LFN with minimal impact on existing projects until they are ready for a subsequent state. |
| Incubation | Project has matured beyond sandbox and may receive funding (while not impacting TAC projects) but does not yet have a representative on the TAC. |
| TAC Project | Project is granted TAC representationXGVela. A team who wants to establish a new project under XGVela should follow Project Proposals guide. |
| Archived | Project is no longer active. |
To move from one state to the next state, the Project Team has to propose to TSCs about their moving-up goals, project data, and request for formal review discussion. TSC will vote on project state change.
| From State | To State | TAC Review | Board Review | ||||
|---|---|---|---|---|---|---|---|
| none | Sandbox | LFN Entry Review Quarterly Health Review | LFN Entry Review | ||||
| Sandbox | Incubation | Incubation Review | Incubation Review | ||||
| Incubation | TAC | TAC Admission Review | TAC Admission Review | ||||
| TAC | Incubation | Incubation Reversal Review | Archived | Archival Review | none | LFN Exit Review | LFN Exit Review |
2.4. Project Review
XGVela follows the LFN Project Lifecycle process which includes the Project Review Process, and can be found here: LFN Project Lifecycle
2.5. Release Process
Initially the TSC will make all decisions about Releases of the project. This may be amended by vote to include Project Committers as the project grows. However, to be able to measurable, the project must demonstrate a history of following the Release Process. The purpose of the Release Process is to assure openness and maximum opportunity for participation. The idea is to have a simple, clear, public declaration of what a project intends to do and when, and what was actually done in a release cycle. Towards that end, a project following the ‘Release Process’ should have a Release Plan published at the beginning of its release cycle by its Committers, after review by the TSC, and a Release Review just prior to the project release.
Both Release Plan and Release Review documents are intended to be relatively short, simple, and posted publicly on the wiki to assist project in coordinating amount themselves and the general world in gaining visibility.
Release Plan and Release Review should contain roughly the following sections:
...