Skip to content

Commit 5506412

Browse files
authored
fixing headings
1 parent 532ec36 commit 5506412

File tree

1 file changed

+9
-9
lines changed
  • docs/governance/lifecycle-stages

1 file changed

+9
-9
lines changed

docs/governance/lifecycle-stages/labs.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ id: labs
33
title: Labs Stage
44
---
55

6-
# Badge
6+
## Badge
77

88
<img src="https://raw.githubusercontent.com/finos/contrib-toolbox/master/images/badge-labs.png" width="150" />
99

@@ -15,12 +15,12 @@ Foundation-hosted projects are expected to provide a clear indication to visitor
1515

1616
See here for a list of [FINOS Labs](https://github.com/finos-labs/) projects.
1717

18-
# Definition
18+
## Definition
1919
Projects in the FINOS Labs stage are in an experimental and exploratory phase.
2020

2121
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).
2222

23-
# Objectives
23+
## Objectives
2424
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.
2525

2626
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
3434
3. Construction of an implementation timeline or additions to the project roadmap
3535
4. Development and testing.
3636

37-
# How to apply for FINOS Labs
37+
## How to apply for FINOS Labs
3838

3939
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).
4040

@@ -46,9 +46,9 @@ If you are a FINOS Member (or have a FINOS member as a maintainer of your projec
4646

4747
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.
4848

49-
# Requirements
49+
## Requirements
5050

51-
## Labs Acceptance Requirements
51+
### Labs Acceptance Requirements
5252

5353
The following factors must be confirmed before the project can be accepted and onboarded as a FINOS Labs Project.
5454

@@ -58,7 +58,7 @@ The following factors must be confirmed before the project can be accepted and o
5858
- Project's license must comply with the [FINOS IP Policy](https://community.finos.org/governance-docs/IP-policy.pdf)
5959
- The above may be brought into compliance during the contribution process before final onboarding
6060

61-
## Labs Ongoing Maintenance Requirements
61+
### Labs Ongoing Maintenance Requirements
6262

6363
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.
6464

@@ -73,15 +73,15 @@ The following must remain true for projects at all times. A Health Review may be
7373
- Released artifacts must be distributed under a FINOS namespace following language-specific best practices
7474
- Demonstrated adherence to Maturity Level 1 of the [Open Source Project Security Baseline](https://baseline.openssf.org/)
7575

76-
# Transition out of Labs
76+
## Transition out of Labs
7777
As projects become more mature they have several options to progress:
7878

7979
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).
8080
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).
8181
3. Graduate to another LF foundation (if scope / audience has grown beyond finance)
8282
5. Archive
8383

84-
# Notes for Consumers and other Evaluators
84+
## Notes for Consumers and other Evaluators
8585
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:
8686

8787
* 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

Comments
 (0)