Skip to content

[Proposal] New Project Maturity Levels#233

Open
eddie-knight wants to merge 5 commits intofinos:mainfrom
eddie-knight:new-lifecycle
Open

[Proposal] New Project Maturity Levels#233
eddie-knight wants to merge 5 commits intofinos:mainfrom
eddie-knight:new-lifecycle

Conversation

@eddie-knight
Copy link
Contributor

@eddie-knight eddie-knight commented Sep 22, 2025

All TOC members are asked to respond to this proposal in the form of a +1, -1, or 0 to formally abstain.

Part of #167

This is the culmination of nearly one year of open discussion among the TOC and public meeting participants, along with active guidance from FINOS staff.

The goal of this update is to take a step toward alignment with proven project lifecycle processes from other open source foundations, while increasing clarity around the responsibility of the TOC in the project lifecycle. Follow-up contributions will include updates to improve processes related to contribution applications, promotion requests, and health reviews.

This vote will be open until Friday September 26th at 1700PST.

Functional changes must not be applied to this PR while the vote is open.

In this pull request

  • Brief descriptions for each of the new levels: Labs, Incubating, and Graduated
  • Application requirements for Labs, Incubating, and Graduated projects
  • Maintenance requirements for Labs, Incubating, and Graduated projects

Not included in this pull request

  • Application process details
  • Health review process details
  • Project maturity benefits

Signed-off-by: Eddie Knight <knight@linux.com>
Signed-off-by: Eddie Knight <knight@linux.com>
@psmulovics
Copy link
Contributor

👍

Copy link
Contributor

@chris-twiner chris-twiner left a comment

Choose a reason for hiding this comment

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

+1

mindthegab

This comment was marked as resolved.

@eddie-knight

This comment was marked as resolved.

@mindthegab
Copy link
Member

Yes @eddie-knight - 100% correct.

In the spirit of moving forward, then, my vote becomes a +1 with the condition that this PR is not merged until #230 is also contextually merged / resolved. I'm more than happy to work with the TOC members who will carry that out as needed.

This way we don't have any point in time in which two separate sets of lifecycle stages are published.

@eminty69
Copy link
Contributor

+1

2 similar comments
@harkeganesh
Copy link
Contributor

+1

@rocketstack-matt
Copy link
Member

+1

@maria-mcparland
Copy link
Contributor

+1

@psmulovics
Copy link
Contributor

psmulovics commented Oct 29, 2025

@eddie-knight would resolve conflicts and would be merged after #finos/community/374

@arroyo
Copy link

arroyo commented Jan 7, 2026

+1

@eddie-knight eddie-knight moved this from Paused / Blocked to 🏗 In progress in FINOS Technical Oversight Committee Backlog Jan 7, 2026
	modified:   operations/processes/projects/graduation.md
Signed-off-by: Eddie Knight <knight@linux.com>
@mindthegab
Copy link
Member

@eddie-knight please review finos/community#388 which from my side, unlocks merging this in.

Looking forward to it!

@TheJuanAndOnly99 @maoo @opoupeney FYI

@eddie-knight
Copy link
Contributor Author

@mindthegab I gave it a look yesterday and it appears to be all in line with what we discussed on our most recent call.

Only note is that one or more issue templates are stubs, but I understand you've got that tracked.

Copy link
Contributor

@gliptak gliptak left a comment

Choose a reason for hiding this comment

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

👍

@fgogolli
Copy link
Contributor

fgogolli commented Mar 4, 2026

+1

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

Projects

Status: 🏗 In progress

Development

Successfully merging this pull request may close these issues.