Skip to content

Final lifecycle quality / consistency updates #388

Open
mindthegab wants to merge 17 commits intomainfrom
final-lifecycle-updates
Open

Final lifecycle quality / consistency updates #388
mindthegab wants to merge 17 commits intomainfrom
final-lifecycle-updates

Conversation

@mindthegab
Copy link
Member

@mindthegab mindthegab commented Feb 21, 2026

This PR completes the Lifecycle update work by:

  • Adding cross links to existing FINOS resources to simplify maintainers work
  • Create consistent per stage pages
  • Removing dangling references to project status as second dimension beyond maturity
  • move lifecycle docs out of software projects (applies to standard projects as well)

This should be the final pass to ultimately close finos/technical-oversight-committee#233 and announce.

Follow on includes:

  • Potentially single sourcing lifecycle requirements in TOC repo
  • @TheJuanAndOnly99 to update incubation issue template
  • @maoo @TheJuanAndOnly99 to make new contribution issue templates working both for Labs and direct to Incubating contributions (asking for different info)
  • Backlink checking in finos.org
  • Announcement
  • There might be more :)

@netlify
Copy link

netlify bot commented Feb 21, 2026

Deploy Preview for eager-borg-83c1a5 ready!

Name Link
🔨 Latest commit 2eeb61e
🔍 Latest deploy log https://app.netlify.com/projects/eager-borg-83c1a5/deploys/699cd56438ec7e0008e431a9
😎 Deploy Preview https://deploy-preview-388--eager-borg-83c1a5.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Feb 21, 2026

CLA Signed

The committers listed above are authorized under a signed CLA.

@mindthegab mindthegab force-pushed the final-lifecycle-updates branch from 5506412 to efd805a Compare February 21, 2026 07:09

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

Foundation-hosted projects are expected to provide a clear indication to visitors that they are in an incubating stage. To this end, the Foundation provides a badge that should be displayed at the top of the project's root-level `README.md` file, using the following Markdown:
Copy link
Member

@TheJuanAndOnly99 TheJuanAndOnly99 Feb 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Foundation-hosted projects are expected to provide a clear indication to visitors that they are in an incubating stage. To this end, the Foundation provides a badge that should be displayed at the top of the project's root-level `README.md` file, using the following Markdown:
Foundation-hosted projects are expected to provide a clear indication to visitors that they are in a forming stage. To this end, the Foundation provides a badge that should be displayed at the top of the project's root-level `README.md` file, using the following Markdown:


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

Foundation-hosted projects are expected to provide a clear indication to visitors that they are in an incubating stage. To this end, the Foundation provides a badge that should be displayed at the top of the project's root-level `README.md` file, using the following Markdown:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Foundation-hosted projects are expected to provide a clear indication to visitors that they are in an incubating stage. To this end, the Foundation provides a badge that should be displayed at the top of the project's root-level `README.md` file, using the following Markdown:
Foundation-hosted projects are expected to provide a clear indication to visitors that they are in a graduated stage. To this end, the Foundation provides a badge that should be displayed at the top of the project's root-level `README.md` file, using the following Markdown:

Below we detail the process for each of the two scenarios.

### Apply for promotion of a FINOS Labs Project to Incubating
In order for a project to become Incubating, it must be reviewed and the change formally approved by the [Technical Steering Committee](https://github.com/finos/technical-steering-committee).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
In order for a project to become Incubating, it must be reviewed and the change formally approved by the [Technical Steering Committee](https://github.com/finos/technical-steering-committee).
In order for a project to become Incubating, it must be reviewed and the change formally approved by the [Technical Oversight Committee](https://github.com/finos/technical-oversight-committee).


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

Foundation-hosted projects are expected to provide a clear indication to visitors that they are in an incubating stage. To this end, the Foundation provides a badge that should be displayed at the top of the project's root-level `README.md` file, using the following Markdown:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Foundation-hosted projects are expected to provide a clear indication to visitors that they are in an incubating stage. To this end, the Foundation provides a badge that should be displayed at the top of the project's root-level `README.md` file, using the following Markdown:
Foundation-hosted projects are expected to provide a clear indication to visitors that they are in the labs stage. To this end, the Foundation provides a badge that should be displayed at the top of the project's root-level `README.md` file, using the following Markdown:

Co-authored-by: Juan Estrella <juan.estrella@finos.org>

To graduate into the Graduated stage, a project must meet the requirements of the [Graduated Lifecycle Checklist](/docs/governance/lifecycle-stages/graduated#Graduated+Acceptance+Requirements) and [Graduated ongoing maintenance requirements](/docs/governance/lifecycle-stages/graduated#Graduated+Ongoing+Maintenance+Requirements).

Any project maintainer may request Graduation by opening a [project graduation request](https://github.com/finos/community/issues/new?assignees=maoo%2C+TheJuanAndOnly99&labels=&template=Project-Graduation.md&title=projectName+Graduation+request) with an information packet demonstrating that they've met the requirements for activation (see below for details).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we have the assignees as a github team?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants