From e724ae2f389c717b14dd045e426229e8974ff4fb Mon Sep 17 00:00:00 2001 From: Lukas Puehringer Date: Mon, 8 Apr 2024 13:56:39 +0200 Subject: [PATCH 1/3] Copy subproject GOVERNANCE.md from cncf template https://github.com/cncf/project-template/blob/cdf4ee657c0ee8c50fe279c4ddf1edcaace7ecc6/GOVERNANCE-subprojects.md Signed-off-by: Lukas Puehringer --- GOVERNANCE.md | 170 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 170 insertions(+) create mode 100644 GOVERNANCE.md diff --git a/GOVERNANCE.md b/GOVERNANCE.md new file mode 100644 index 0000000..1263ff6 --- /dev/null +++ b/GOVERNANCE.md @@ -0,0 +1,170 @@ +# [TODO:PROJECTNAME] Project Governance + +This is an example governance document for projects that consist of a group +of smaller, semi-independent projects. See [GOVERNANCE.md](/GOVERNANCE.md) +for more information. Thanks to the Konveyor Project for portions of the text +below. + +This is a template document for CNCF projects that requires editing +before it is ready to use. Read the markdown comments, ``, for +additional guidance. The raw markdown uses `TODO` to identify areas that +require customization. Replace [TODO: PROJECTNAME] with the name of your project. + +This Template assumes that you are using the Contributor Ladder template as well. + + + +The [TODO:PROJECTNAME] umbrella project is composed as a federation of individual projects, +some independent and some interdependent, each of which focuses on some aspect +of [TODO:Goals of umbrella project]. Our governance reflects this federated structure. + +## Individual Project Governance + + + +All active Maintainers of each subproject, as defined in the Contributor Ladder, are +members of that project's Maintainer Committee, which governs that project. The +subproject's Maintainer Committee is responsible for the following project governance +activities: + +* Ensuring that the subproject creates and publishes regular releases; +* Holding regular, subproject-wide discussions on issues and planning; +* Monthly review of project contributors for advancement on the Contributor Ladder; +* Making final decisions on subproject changes that involve controversial trade-offs; +* Responding to security compromise reports; +* Supporting the Code of Conduct within their subproject and referring violations + to the Code of Conduct Committee. + +Additionally, the project's Maintainer Committee will select, by majority vote, one +representative to the Steering Committee. This representative need not +be a member of the subproject's Maintainer Committee, and will be replaced or +renewed by the committee annually. + +Should a member of the Maintainer Committee cease being active in the subproject, +violate the Code Of Conduct, or need to be removed for some other reason, they +may be removed by a 2/3 majority vote of the other Committee members, or a +majority vote of the Steering Committee. + +## Steering Committee + +The overall [TODO:PROJECTNAME] umbrella project is governed by a Steering +Committee, which is selected as follows: + +* One Maintainer representative from each member subproject +* [TODO:Number] general "Community Representatives" + + + +### Steering Committee Duties + +The Steering Committee is responsible for the following tasks, any of which may +be delegated to a person or group selected by the committee: + +* Reviewing and deciding on new projects to add to [TODO:PROJECTNAME] +* Arbitrating inter-project disagreements +* Selecting the Code of Conduct Committee and ratifying CoC judgements +* Removing projects which have become inactive +* Acting on escalated security or code quality issues +* Resolving issues that individual projects are unable to resolve +* Administering project infrastructure, intellectual property, and resources +* Determining overall direction for advocacy and marketing +* Issuing statements on behalf of [TODO:PROJECTNAME] and its subprojects +* Reviewing and approving Contributor Ladder advancement for participants who + work on the overall umbrella project + +In performance of these duties, the Steering Committee will hold a monthly meeting +that is open to all contributors. The Committee may hold additional, closed meetings +in order to discuss non-public issues such as security exploits, CoC enforcement, +and legal questions. + +Steering Committee members are expected to advocate for all of [TODO:PROJECTNAME], not just +certain projects or corporate sponsors, comply with and support the Code of +Conduct, and be professional and compassionate in all of their dealings with +project participants. + +### Steering Committee Elections + +The Community Representative(s) will be elected by the collective Members +of all subprojects, as defined in the Contributor Ladder. They +will be elected annually. + + + +Once per year, the Steering Committee will select between two and three Election +Officers to run the annual election and sets the dates for the election. Election +Officers should be project Members in good standing, not running for election +themselves, and represent more than one project employer. + +These officers will update the list of eligible Members according to +project records, send out announcements, and conduct the election. The election +starts with a call for nominations, which lasts for at least one week, and will +include a period for project Members to request changes to their voting status. +Candidates may nominate themselves, or they may be nominated by their colleagues. + +The election itself will last for at least one week, and is conducted as a +preference election online, using a method such as Condorcet or IRV. The +Election Officers will announce the selected candidates at the next regular +community meeting. + +## Code of Conduct Committee + + + +In order to review and enforce the Code of Conduct, the Steering Committee selects +[TODO:Number, suggest "3 to 5"] people to be on the Code of Conduct Committee. +These individuals will be chosen based on their community management and code of conduct +experience, with diverse representation across the committee, including employer, gender, +race, background, and region of the world. To avoid fatigue, the Steering Committee will +replace at least [TODO:Number] member of the CoC Committee each year. Members of the +committee do not need to be members of [TODO:PROJECTNAME] if they have sufficient other +expertise. + +The CoC Committee will receive reports of conduct violations confidentially, +and will discuss them in closed meetings. If a report is determined to be a +violation, they will recommend action on it appropriate to the scale, nature, +and context of the violation, from requiring an apology, up to expulsion of an +individual from the project. In the event that a contributor is to be demoted +or expelled, the CoC Committee will forward this recommendation to the Steering +Committee who will ratify it in a closed meeting. Should a member of the +Steering Committee be the offender or the reporter, this recommendation will +instead be forwarded to the CNCF staff for final arbitration. + +## Adding New Subprojects + +During the monthly Steering meeting, any project member may recommend projects +to become part of [TODO:PROJECTNAME]. These projects should have the following +characteristics: + +* Have a mission of [TODO:Goals of umbrella project]; +* Are appropriately licensed and governed or willing to become so; +* Are under active development; +* Consist of high quality code and designs. + +Before submitting an application to the Steering Committee, the applying project +must hold an internal consensus vote of all major contributors to join +[TODO:PROJECTNAME]. The Steering Committee will then review the +application, and decide whether or not to accept it. If it is accepted, the Committee +will assign one person to assist the subproject in their integration. + +In some cases, promising but incomplete projects may be accepted as Experimental +Subprojects. Such Experimental Subprojects will be considered part of +[TODO:PROJECTNAME], but will be marked as Experimental on the website and in code +repositories, in order to inform users. Experimental Subproject Members are considered +Members of [TODO:PROJECTNAME], but the subproject is not entitled to a representative on the +Steering Committee. Steering will review Experimental Subprojects at least twice +per year to determine if they have matured to full subproject status. + +## Removing Projects + +In some cases, projects will become inactive or unmaintainable, or wish to separate +from [TODO:PROJECTNAME]. Any Steering Committee member may propose removal of a project on +these grounds, and Steering can confirm this with a majority vote. + +Projects which still have contributors will then be moved to a repository in their +own namespace. Projects which have ceased all activity are moved to a +[TODO:Name of archive namespace] namespace. \ No newline at end of file From 0c809fcb961cde38c99c55fedb8513685f65f94a Mon Sep 17 00:00:00 2001 From: Lukas Puehringer Date: Mon, 8 Apr 2024 14:06:25 +0200 Subject: [PATCH 2/3] Update GOVERNANCE document for TUF This is a modified version of the proposed CNCF Subprojects template by Josh Berkus. Modifications are made based on two significant factors: 1) the heart of TUF is the specification and TAPs, and therefore the steering committee explicitly includes all TAP editors (spec + TAPs maintainers) 2) the community around TUF today is small, so some procedure has been streamlined to ensure governance is not too burdensome (removal of member representatives feels suboptimal, but we don't have a big community to draw from yet). Signed-off-by: Lukas Puehringer Co-authored-by: Joshua Lock --- GOVERNANCE.md | 244 +++++++++++++++++++++++--------------------------- 1 file changed, 111 insertions(+), 133 deletions(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 1263ff6..75ddef5 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -1,170 +1,148 @@ -# [TODO:PROJECTNAME] Project Governance - -This is an example governance document for projects that consist of a group -of smaller, semi-independent projects. See [GOVERNANCE.md](/GOVERNANCE.md) -for more information. Thanks to the Konveyor Project for portions of the text -below. - -This is a template document for CNCF projects that requires editing -before it is ready to use. Read the markdown comments, ``, for -additional guidance. The raw markdown uses `TODO` to identify areas that -require customization. Replace [TODO: PROJECTNAME] with the name of your project. - -This Template assumes that you are using the Contributor Ladder template as well. - - - -The [TODO:PROJECTNAME] umbrella project is composed as a federation of individual projects, -some independent and some interdependent, each of which focuses on some aspect -of [TODO:Goals of umbrella project]. Our governance reflects this federated structure. - -## Individual Project Governance - - - -All active Maintainers of each subproject, as defined in the Contributor Ladder, are -members of that project's Maintainer Committee, which governs that project. The -subproject's Maintainer Committee is responsible for the following project governance -activities: +# The Update Framework Governance + +## Project Types + +* Core: the core of The Update Framework (TUF) project is the TUF specification + of a framework for securing software update system, and the TUF Augmentation + Proposals (TAPs) process that is used to provide additional information about + TUF or describe a new feature for TUF or for its processes or environment. + Included with the core projects are ancillary projects such as the website + (theupdateframework.io) and artwork repositories. +* Subprojects: are closely related, but semi-independent, projects such as + implementations of the TUF specification (notary, go-tuf, tuf, etc). + +## Contributor Ladder + +* Participant: any person that contributes their time and thoughts to The + Update Framework. +* Contributor: someone who contributes directly to the project, such as + submitting Pull Requests, engaging in discussions on Issues or in Slack, + attending meetings, etc. +* Subproject member: a recognised contributor who has been granted additional + capabilities (including closing/reopening and assigning issues and pull + requests) +* Subproject Maintainer: a maintainer can also review and merge pull requests. +* TAP Editor: maintainers of the specification and TAPs. +* Consensus Builder: the project's founder and consensus builder, is able to + veto any issues put to the Steering Committee vote. + +Contributors who have not actively contributed to the project, through PRs and +Issues, or communicated on project forums (GitHub, Slack, Mailing list) for +longer than 12 months may be involuntarily moved down the contributor ladder, +or asked to move to an emeritus status. + +## Individual Subproject Governance + +All active Maintainers of each subproject, as defined in the Contributor +Ladder, are members of that subproject's Maintainer Committee, which governs +that subproject. The subproject's Maintainer Committee is responsible for the +following subproject governance activities: * Ensuring that the subproject creates and publishes regular releases; * Holding regular, subproject-wide discussions on issues and planning; -* Monthly review of project contributors for advancement on the Contributor Ladder; -* Making final decisions on subproject changes that involve controversial trade-offs; +* Periodic review of subproject contributors for advancement on the Contributor + Ladder; +* Making final decisions on subproject changes that involve controversial + trade-offs; * Responding to security compromise reports; -* Supporting the Code of Conduct within their subproject and referring violations - to the Code of Conduct Committee. - -Additionally, the project's Maintainer Committee will select, by majority vote, one -representative to the Steering Committee. This representative need not -be a member of the subproject's Maintainer Committee, and will be replaced or -renewed by the committee annually. +* Supporting the Code of Conduct within their subproject and referring + violations to the Code of Conduct Committee. -Should a member of the Maintainer Committee cease being active in the subproject, -violate the Code Of Conduct, or need to be removed for some other reason, they -may be removed by a 2/3 majority vote of the other Committee members, or a -majority vote of the Steering Committee. +Additionally, the subproject's Maintainer Committee will select one +representative to the Steering Committee. ## Steering Committee - -The overall [TODO:PROJECTNAME] umbrella project is governed by a Steering -Committee, which is selected as follows: - +The overall TUF umbrella project is governed by a Steering Committee, which is +selected as follows: * One Maintainer representative from each member subproject -* [TODO:Number] general "Community Representatives" - - +* All of the TAP Editors +* The Consensus Builder -### Steering Committee Duties +## Steering Committee Duties The Steering Committee is responsible for the following tasks, any of which may be delegated to a person or group selected by the committee: -* Reviewing and deciding on new projects to add to [TODO:PROJECTNAME] -* Arbitrating inter-project disagreements +* Reviewing and deciding on new subprojects to add to The Update Framework +* Arbitrating inter-subproject disagreements * Selecting the Code of Conduct Committee and ratifying CoC judgements -* Removing projects which have become inactive +* Removing subprojects which have become inactive * Acting on escalated security or code quality issues -* Resolving issues that individual projects are unable to resolve +* Resolving issues that individual subprojects are unable to resolve * Administering project infrastructure, intellectual property, and resources * Determining overall direction for advocacy and marketing -* Issuing statements on behalf of [TODO:PROJECTNAME] and its subprojects +* Issuing statements on behalf of The Update Framework and its subprojects * Reviewing and approving Contributor Ladder advancement for participants who work on the overall umbrella project -In performance of these duties, the Steering Committee will hold a monthly meeting -that is open to all contributors. The Committee may hold additional, closed meetings -in order to discuss non-public issues such as security exploits, CoC enforcement, -and legal questions. - -Steering Committee members are expected to advocate for all of [TODO:PROJECTNAME], not just -certain projects or corporate sponsors, comply with and support the Code of -Conduct, and be professional and compassionate in all of their dealings with -project participants. - -### Steering Committee Elections - -The Community Representative(s) will be elected by the collective Members -of all subprojects, as defined in the Contributor Ladder. They -will be elected annually. - - - -Once per year, the Steering Committee will select between two and three Election -Officers to run the annual election and sets the dates for the election. Election -Officers should be project Members in good standing, not running for election -themselves, and represent more than one project employer. - -These officers will update the list of eligible Members according to -project records, send out announcements, and conduct the election. The election -starts with a call for nominations, which lasts for at least one week, and will -include a period for project Members to request changes to their voting status. -Candidates may nominate themselves, or they may be nominated by their colleagues. +In performance of these duties, the Steering Committee will hold a quarterly +meeting that is open to all contributors. The Committee may hold additional, +closed meetings in order to discuss non-public issues such as security exploits, +CoC enforcement, and legal questions. -The election itself will last for at least one week, and is conducted as a -preference election online, using a method such as Condorcet or IRV. The -Election Officers will announce the selected candidates at the next regular -community meeting. +Steering Committee members are expected to advocate for all of The Update +Framework, not just certain subprojects or corporate sponsors, comply with and +support the Code of Conduct, and be professional and compassionate in all of +their dealings with project participants. ## Code of Conduct Committee - +In order to review and enforce the Code of Conduct, the Steering Committee +selects 3 people to be on the Code of Conduct Committee. -In order to review and enforce the Code of Conduct, the Steering Committee selects -[TODO:Number, suggest "3 to 5"] people to be on the Code of Conduct Committee. -These individuals will be chosen based on their community management and code of conduct -experience, with diverse representation across the committee, including employer, gender, -race, background, and region of the world. To avoid fatigue, the Steering Committee will -replace at least [TODO:Number] member of the CoC Committee each year. Members of the -committee do not need to be members of [TODO:PROJECTNAME] if they have sufficient other -expertise. +These individuals will be chosen based on their community management and code of +conduct experience, with diverse representation across the committee, including +employer, gender, race, background, and region of the world. To avoid fatigue, +the Steering Committee will replace at least 1 member of the CoC Committee each +year. Members of the committee do not need to be members of The Update Framework +if they have sufficient other expertise. -The CoC Committee will receive reports of conduct violations confidentially, -and will discuss them in closed meetings. If a report is determined to be a +The CoC Committee will receive reports of conduct violations confidentially, and +will discuss them in closed meetings. If a report is determined to be a violation, they will recommend action on it appropriate to the scale, nature, and context of the violation, from requiring an apology, up to expulsion of an -individual from the project. In the event that a contributor is to be demoted -or expelled, the CoC Committee will forward this recommendation to the Steering -Committee who will ratify it in a closed meeting. Should a member of the +individual from the project. In the event that a contributor is to be demoted or +expelled, the CoC Committee will forward this recommendation to the Steering +Committee who will ratify it in a closed meeting. Should a member of the Steering Committee be the offender or the reporter, this recommendation will instead be forwarded to the CNCF staff for final arbitration. -## Adding New Subprojects +## Adding Subprojects -During the monthly Steering meeting, any project member may recommend projects -to become part of [TODO:PROJECTNAME]. These projects should have the following -characteristics: +During the quarterly Steering meeting, any project Member may recommend +subprojects to become part of The Update Framework. These subprojects should +have the following characteristics: -* Have a mission of [TODO:Goals of umbrella project]; +* Have a mission of securing software update systems; * Are appropriately licensed and governed or willing to become so; * Are under active development; * Consist of high quality code and designs. -Before submitting an application to the Steering Committee, the applying project -must hold an internal consensus vote of all major contributors to join -[TODO:PROJECTNAME]. The Steering Committee will then review the -application, and decide whether or not to accept it. If it is accepted, the Committee -will assign one person to assist the subproject in their integration. - -In some cases, promising but incomplete projects may be accepted as Experimental -Subprojects. Such Experimental Subprojects will be considered part of -[TODO:PROJECTNAME], but will be marked as Experimental on the website and in code -repositories, in order to inform users. Experimental Subproject Members are considered -Members of [TODO:PROJECTNAME], but the subproject is not entitled to a representative on the -Steering Committee. Steering will review Experimental Subprojects at least twice -per year to determine if they have matured to full subproject status. - -## Removing Projects - -In some cases, projects will become inactive or unmaintainable, or wish to separate -from [TODO:PROJECTNAME]. Any Steering Committee member may propose removal of a project on -these grounds, and Steering can confirm this with a majority vote. - -Projects which still have contributors will then be moved to a repository in their -own namespace. Projects which have ceased all activity are moved to a -[TODO:Name of archive namespace] namespace. \ No newline at end of file +Before submitting an application to the Steering Committee, the applying +subproject must hold an internal consensus vote of all major subproject +contributors to join The Update Framework. The Steering Committee will then +review the application, and decide whether or not to accept it. If it is +accepted, the Committee will assign one person to assist the subproject in their +integration. + +In some cases, promising but incomplete subprojects may be accepted as +Experimental Subprojects. Such Experimental Subprojects will be considered part +of The Update Framework, but will be marked as Experimental on the website and +in code repositories, in order to inform users. Experimental subproject Members +are considered Members of The Update Framework, but the subproject is not +entitled to a representative on the Steering Committee. Steering will review +Experimental Subprojects at least twice per year to determine if they have +matured to full subproject status. + +## Removing Subprojects + +In some cases, subprojects will become inactive or unmaintainable, or wish to +separate from The Update Framework. Any Steering Committee member may propose +removal of a subproject on these grounds, and Steering can confirm this with a +majority vote. + +Subprojects which still have contributors will then be moved to a repository in +their own namespace. Subprojects which have ceased all activity are moved to a +theupdateframework-archive namespace. Note that any subproject assets, such as +trademarks, may be legally required to remain in the possession of the Linux +Foundation in some form. \ No newline at end of file From 3f7b39f1e6055a0bb9f175dc891f6073b00f10d9 Mon Sep 17 00:00:00 2001 From: Lukas Puehringer Date: Mon, 8 Apr 2024 14:14:39 +0200 Subject: [PATCH 3/3] Update GOVERNANCE.md based on community discussion Signed-off-by: Lukas Puehringer Co-authored-by: Justin Cappos --- GOVERNANCE.md | 73 +++++++++++++++++++++++++++++++-------------------- 1 file changed, 45 insertions(+), 28 deletions(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 75ddef5..03daa0b 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -10,6 +10,17 @@ (theupdateframework.io) and artwork repositories. * Subprojects: are closely related, but semi-independent, projects such as implementations of the TUF specification (notary, go-tuf, tuf, etc). +* Affiliated subprojects: these are related projects which have some ties to TUF + and which are granted all of the benefit of subproject status. Any mention of + subproject in this document is meant to apply to affiliated subprojects as well + unless otherwise noted. This distinction is granted by a majority of the TUF + steering committee and is intended to be used for projects which cannot or do + not wish to be official subprojects of TUF under the CNCF. +* Experimental subprojects: The experimental subproject status may be given to a + project which would benefit the TUF ecosystem, but which is not of sufficient + maturity to become a normal subproject. An experimental subproject and its + members, maintainers, etc. are not given the normal rights of a subproject + unless expressly stated. ## Contributor Ladder @@ -24,12 +35,14 @@ * Subproject Maintainer: a maintainer can also review and merge pull requests. * TAP Editor: maintainers of the specification and TAPs. * Consensus Builder: the project's founder and consensus builder, is able to - veto any issues put to the Steering Committee vote. + veto any issues put to the Steering Committee vote. If the consensus builder + leaves the project permanently, the steering committee elects another consensus + builder. Contributors who have not actively contributed to the project, through PRs and Issues, or communicated on project forums (GitHub, Slack, Mailing list) for -longer than 12 months may be involuntarily moved down the contributor ladder, -or asked to move to an emeritus status. +longer than 2 months may be involuntarily moved down the contributor ladder, +or moved to an emeritus status. ## Individual Subproject Governance @@ -54,16 +67,29 @@ representative to the Steering Committee. ## Steering Committee The overall TUF umbrella project is governed by a Steering Committee, which is selected as follows: -* One Maintainer representative from each member subproject -* All of the TAP Editors +* Two of the TAP Editors +* Two elected from the set of TUF contributors +* Two maintainers from the set of subproject maintainers. * The Consensus Builder +About voting: +* All TUF Contributors are allowed to vote in each election. The Consensus + Builder will have final decision on what constitutes a contribution for + the purposes of voting rights. +* The elections for each group of positions will be held separately in a + non-consecutive manner. +* With the exception of the consensus builder (who is omitted from this + calculation), it is not permitted to have more than one steering committee + member from the same subproject or organization. + + ## Steering Committee Duties The Steering Committee is responsible for the following tasks, any of which may be delegated to a person or group selected by the committee: * Reviewing and deciding on new subprojects to add to The Update Framework +* Granting affiliate subproject status to an external project * Arbitrating inter-subproject disagreements * Selecting the Code of Conduct Committee and ratifying CoC judgements * Removing subprojects which have become inactive @@ -78,34 +104,25 @@ be delegated to a person or group selected by the committee: In performance of these duties, the Steering Committee will hold a quarterly meeting that is open to all contributors. The Committee may hold additional, closed meetings in order to discuss non-public issues such as security exploits, -CoC enforcement, and legal questions. +CoC enforcement, and legal questions. However, as a rule, meetings will be held +in public when practical. Steering Committee members are expected to advocate for all of The Update Framework, not just certain subprojects or corporate sponsors, comply with and support the Code of Conduct, and be professional and compassionate in all of their dealings with project participants. -## Code of Conduct Committee - -In order to review and enforce the Code of Conduct, the Steering Committee -selects 3 people to be on the Code of Conduct Committee. +## Code of Conduct Violations -These individuals will be chosen based on their community management and code of -conduct experience, with diverse representation across the committee, including -employer, gender, race, background, and region of the world. To avoid fatigue, -the Steering Committee will replace at least 1 member of the CoC Committee each -year. Members of the committee do not need to be members of The Update Framework -if they have sufficient other expertise. +Code of conduct issues discovered by the community should be reported to the CNCF +code of conduct committee. -The CoC Committee will receive reports of conduct violations confidentially, and -will discuss them in closed meetings. If a report is determined to be a -violation, they will recommend action on it appropriate to the scale, nature, -and context of the violation, from requiring an apology, up to expulsion of an -individual from the project. In the event that a contributor is to be demoted or -expelled, the CoC Committee will forward this recommendation to the Steering -Committee who will ratify it in a closed meeting. Should a member of the -Steering Committee be the offender or the reporter, this recommendation will -instead be forwarded to the CNCF staff for final arbitration. +We welcome the CNCF code of conduct committee to handle code of conduct violations +in either of the following ways (at their discretion): +* notify members of the TUF Steering Committee so that we may handle the issue + internally +* handle the issue at the CNCF level and notify the project of the incident and/or + resolution, as is appropriate ## Adding Subprojects @@ -130,9 +147,9 @@ Experimental Subprojects. Such Experimental Subprojects will be considered part of The Update Framework, but will be marked as Experimental on the website and in code repositories, in order to inform users. Experimental subproject Members are considered Members of The Update Framework, but the subproject is not -entitled to a representative on the Steering Committee. Steering will review -Experimental Subprojects at least twice per year to determine if they have -matured to full subproject status. +entitled to any other subproject rights. The Steering Committee will review +Experimental Subprojects at least annually per year to determine if they have +matured to full subproject status or if they should be removed. ## Removing Subprojects