You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -15,12 +15,12 @@ Foundation-hosted projects are expected to provide a clear indication to visitor
15
15
16
16
See here for a list of [FINOS Labs](https://github.com/finos-labs/) projects.
17
17
18
-
# Definition
18
+
##Definition
19
19
Projects in the FINOS Labs stage are in an experimental and exploratory phase.
20
20
21
21
To clearly differentiate their early stage maturity, projects in this stage are hosted in the dedicated [FINOS Labs](https://github.com/finos-labs/) Github org, separate from the main [FINOS org](https://github.com/finos).
22
22
23
-
# Objectives
23
+
##Objectives
24
24
The objective of the Labs labs stage is to provide a low-friction environment to allow the project team to experiment under a neutral governance in the open, and work through their concepts collaboratively within the FINOS umbrella.
25
25
26
26
This stage serves the default entry stage for all new projects contributed to FINOS, allowing for quick evolution towards project-market-fit.
@@ -34,7 +34,7 @@ Once established, Labs projects are expected to prioritise some or all of the fo
34
34
3. Construction of an implementation timeline or additions to the project roadmap
35
35
4. Development and testing.
36
36
37
-
# How to apply for FINOS Labs
37
+
##How to apply for FINOS Labs
38
38
39
39
To be accepted, Labs projects must comply with formal [FINOS Labs Acceptance Requirements](/docs/governance/lifecycle-stages/labs#labs-acceptance-requirements) by the [Technical Oversight Committee (TOC)](https://github.com/finos/technical-oversight-committee) and enforced by the FINOS staff. After acceptance, they must also adhere to a short list [FINOS Labs ongoing maintainance requirements](/docs/governance/lifecycle-stages/labs#labs-ongoing-maintenance-requirements).
40
40
@@ -46,9 +46,9 @@ If you are a FINOS Member (or have a FINOS member as a maintainer of your projec
46
46
47
47
If you believe your project is more mature than a Labs project, at the time of contribution you will have an option to evidence compliance with later stages and contextually request the [Technical Oversight Committee](https://github.com/finos/technical-oversight-committee) to award [Incubating](/docs/governance/lifecycle-stages/incubating) or [Graduated](/docs/governance/lifecycle-stages/graduated) stage.
48
48
49
-
# Requirements
49
+
##Requirements
50
50
51
-
## Labs Acceptance Requirements
51
+
###Labs Acceptance Requirements
52
52
53
53
The following factors must be confirmed before the project can be accepted and onboarded as a FINOS Labs Project.
54
54
@@ -58,7 +58,7 @@ The following factors must be confirmed before the project can be accepted and o
58
58
- Project's license must comply with the [FINOS IP Policy](https://community.finos.org/governance-docs/IP-policy.pdf)
59
59
- The above may be brought into compliance during the contribution process before final onboarding
60
60
61
-
## Labs Ongoing Maintenance Requirements
61
+
###Labs Ongoing Maintenance Requirements
62
62
63
63
The following must remain true for projects at all times. A Health Review may be done by the FINOS TOC or Staff as often as once every six months. Project support will be offered in the event that a project is found to be out of compliance. If a project remains out of compliance for two consecutive Health Reviews, it will qualify for archival.
64
64
@@ -73,15 +73,15 @@ The following must remain true for projects at all times. A Health Review may be
73
73
- Released artifacts must be distributed under a FINOS namespace following language-specific best practices
74
74
- Demonstrated adherence to Maturity Level 1 of the [Open Source Project Security Baseline](https://baseline.openssf.org/)
75
75
76
-
# Transition out of Labs
76
+
##Transition out of Labs
77
77
As projects become more mature they have several options to progress:
78
78
79
79
1. Transition into FINOS Incubating stage by [requesting incubation](https://github.com/finos/community/issues/new?assignees=maoo%2C+TheJuanAndOnly99&labels=&template=Project-Incubation.md&title=projectName+Incubation+Request).
80
80
2. Transition into FINOS Graduated stage by [requesting graduation](https://github.com/finos/community/issues/new?assignees=maoo%2C+TheJuanAndOnly99&labels=&template=Project-Graduation.md&title=projectName+Graduation+Request).
81
81
3. Graduate to another LF foundation (if scope / audience has grown beyond finance)
82
82
5. Archive
83
83
84
-
# Notes for Consumers and other Evaluators
84
+
##Notes for Consumers and other Evaluators
85
85
If you're evaluating Foundation-hosted open source projects and see the Labs badge shown above, here are some of the things you should expect should you choose to download and use the software:
86
86
87
87
* The software is not guaranteed to be "finished", either from a functional perspective or a quality (security, compliance, testing) perspective. As a result you should expect to run into bugs and missing features.
0 commit comments