Skip to content

Conversation

@arm4b
Copy link
Member

@arm4b arm4b commented Feb 1, 2021

A follow-up to: #5071 where TSC Chair Election was initially suggested by @dzimine. This is a new revision proposal on top of that, covering governance inconsistencies.

When we defined "Leaders" we expected them (several persons) to take responsibility of:

External Relations, Organizational aspects, coordinating Events, Partnerships

TSC Meeting is an Organizational aspect and involves Event Coordination. TSC Chair is normally responsible for External Relations as well, including communicating with the LF (per Technical Charter) and being a project spokesperson. Having said that, role with many Leaders was previously created to reflect the TSC chairperson responsibilities and even more.

Now as team is gravitating towards the TSC Chair, the proposal is to move the StackStorm TSC governance model from Promotion (Leaders) to Election (TSC Chair). After reviewing tens of OSS Governance examples from different projects it's definitely more anticipated way for an average LF/CNCF project.

This version also defines new emeritus role "Project Mentor" for someone unique like project co-founder (as seen in some OSS Governance structures). Besides of being neutral mediator, advising members on fulfilling their responsibilities and helping project operating within best practices, Project Mentor holds election coordination responsibilities: ensuring proper announcements were made and in time, procedures are followed, calculating the election voting, the election results are communicated, deadlines are in place, etc.

@arm4b arm4b requested review from a team and dzimine February 1, 2021 14:53
@arm4b arm4b requested review from a team as code owners February 1, 2021 14:53
@pull-request-size pull-request-size bot added the size/M PR that changes 30-99 lines. Good size to review. label Feb 1, 2021
@arm4b arm4b marked this pull request as draft February 1, 2021 14:53
arm4b and others added 2 commits February 2, 2021 18:41
@stale
Copy link

stale bot commented Jun 2, 2021

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically marking is as stale. If this issue is not relevant or applicable anymore (problem has been fixed in a new version or similar), please close the issue or let us know so we can close it. On the contrary, if the issue is still relevant, there is nothing you need to do, but if you have any additional details or context which would help us when working on this issue, please include it as a comment to this issue.

@stale stale bot added the stale label Jun 2, 2021
@CLAassistant
Copy link

CLAassistant commented Sep 6, 2021

CLA assistant check
All committers have signed the CLA.

@stale stale bot removed the stale label Sep 6, 2021
@cognifloyd cognifloyd added the TSC PR managing GOVERNANCE or other TSC documentation label Oct 3, 2021
@stale
Copy link

stale bot commented Apr 16, 2022

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically marking is as stale. If this issue is not relevant or applicable anymore (problem has been fixed in a new version or similar), please close the issue or let us know so we can close it. On the contrary, if the issue is still relevant, there is nothing you need to do, but if you have any additional details or context which would help us when working on this issue, please include it as a comment to this issue.

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

Labels

documentation size/M PR that changes 30-99 lines. Good size to review. status:under discussion TSC PR managing GOVERNANCE or other TSC documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants