From 423428a38ea14528b3e61ef27e55bd79eb05dbda Mon Sep 17 00:00:00 2001 From: Eugen Cusmaunsa Date: Tue, 12 Jul 2022 21:12:51 +0100 Subject: [PATCH 1/5] TSC Governance: Document TSC Meetings rotation --- GOVERNANCE.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 727f778a92..044fcc260e 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -9,6 +9,16 @@ It extends [Technical Charter](https://stackstorm.com/wp/wp-content/uploads/2020 The Technical Steering Committee is a group of Maintainers (Committers) who have earned the ability to modify (“commit”) sourcecode, documentation or other artifacts. This group is responsible for all technical oversight of StackStorm as Open Source Project. +### TSC Meetings +Because of the different schedules and time zones, TSC is keen to prioritize asynchronous collaboration and work. +However every first Tuesday of the month [@StackStorm/tsc](OWNERS.md) members are gathering for 1 hour to discuss the project problems, roadmap, priorities to help the StackStorm as a project evolve and succeed. +These meetings are open and we invite community to join them to be up to date with the latest project developments and progress. + +* TSC Meetings Host responsibility is rotated between the TSC maintainers. +* Priority is given based on activity: Current Release Managers > Senior Maintainers > Maintainers. +* Maintainers are free to decide collectively who would run the next TSC meeting. They can run in pairs, repeat, however no Maintainer can be a host for more than one in three consecutive meetings. +See [StackStorm TSC Meetings](https://github.com/StackStorm/community/issues/33) for more info about the meeting schedule, meeting host responsibilities and procedure. + ### Maintainer Roles The current list of maintainers is published and updated in [OWNERS.md](OWNERS.md). StackStorm uses a three-tiered system of Maintainer roles: From 9c51126c6c9d3909b33ae1850e03c0c2cd9f6fe8 Mon Sep 17 00:00:00 2001 From: Eugen Cusmaunsa Date: Wed, 17 Aug 2022 13:12:25 +0200 Subject: [PATCH 2/5] Add more clarification for the TSC meetings & host priority --- GOVERNANCE.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 044fcc260e..9238a39116 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -11,13 +11,13 @@ This group is responsible for all technical oversight of StackStorm as Open Sour ### TSC Meetings Because of the different schedules and time zones, TSC is keen to prioritize asynchronous collaboration and work. -However every first Tuesday of the month [@StackStorm/tsc](OWNERS.md) members are gathering for 1 hour to discuss the project problems, roadmap, priorities to help the StackStorm as a project evolve and succeed. -These meetings are open and we invite community to join them to be up to date with the latest project developments and progress. +However, every `1st Tuesday` of the month `09:30 AM US Pacific`, [@StackStorm/tsc](OWNERS.md) members are gathering for `1 hour` to discuss the project problems, roadmap, priorities to help the StackStorm as a project evolve and succeed. +The meetings are open, and we invite community to join them to be up-to-date with the latest project developments and progress. * TSC Meetings Host responsibility is rotated between the TSC maintainers. -* Priority is given based on activity: Current Release Managers > Senior Maintainers > Maintainers. -* Maintainers are free to decide collectively who would run the next TSC meeting. They can run in pairs, repeat, however no Maintainer can be a host for more than one in three consecutive meetings. -See [StackStorm TSC Meetings](https://github.com/StackStorm/community/issues/33) for more info about the meeting schedule, meeting host responsibilities and procedure. +* Priority to host is given based on activity: Current Release Owners > Maintainers who weren't in rotation > Other Maintainer Volunteers. +* Maintainers are free to decide collectively who would run the next TSC meeting. They can run in pairs, swap, however for diversification reasons no Maintainer can be a host for more than one in three consecutive meetings. +See [StackStorm TSC Meetings](https://github.com/StackStorm/community/issues/33) for more info about the meeting schedule, calendar, meeting host responsibilities and procedure. ### Maintainer Roles The current list of maintainers is published and updated in [OWNERS.md](OWNERS.md). From 69287ab76cd38d8392cf41fa3e618e2a80355db8 Mon Sep 17 00:00:00 2001 From: Eugen Cusmaunsa Date: Tue, 6 Sep 2022 14:38:49 +0100 Subject: [PATCH 3/5] Remove host limitation when rotating the TSC meetings Just state in the governance the intent of TSC Meetings rotation. The mechanism will follow naturally. --- GOVERNANCE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 9238a39116..169323fb15 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -16,7 +16,7 @@ The meetings are open, and we invite community to join them to be up-to-date wit * TSC Meetings Host responsibility is rotated between the TSC maintainers. * Priority to host is given based on activity: Current Release Owners > Maintainers who weren't in rotation > Other Maintainer Volunteers. -* Maintainers are free to decide collectively who would run the next TSC meeting. They can run in pairs, swap, however for diversification reasons no Maintainer can be a host for more than one in three consecutive meetings. +* Maintainers are free to decide collectively who would run the next TSC meeting: they can run in pairs, swap. See [StackStorm TSC Meetings](https://github.com/StackStorm/community/issues/33) for more info about the meeting schedule, calendar, meeting host responsibilities and procedure. ### Maintainer Roles From 534e604a0375411c262a8e0393d49eaa25751a53 Mon Sep 17 00:00:00 2001 From: Eugen Cusmaunsa Date: Wed, 7 Sep 2022 11:57:39 +0100 Subject: [PATCH 4/5] Link to the TSC Meetings page with more info about the schedule --- GOVERNANCE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 169323fb15..cea7b5aceb 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -11,13 +11,13 @@ This group is responsible for all technical oversight of StackStorm as Open Sour ### TSC Meetings Because of the different schedules and time zones, TSC is keen to prioritize asynchronous collaboration and work. -However, every `1st Tuesday` of the month `09:30 AM US Pacific`, [@StackStorm/tsc](OWNERS.md) members are gathering for `1 hour` to discuss the project problems, roadmap, priorities to help the StackStorm as a project evolve and succeed. +However, every month, [@StackStorm/tsc](OWNERS.md) members are gathering for `1 hour` to discuss the project problems, roadmap, priorities to help the StackStorm as a project evolve and succeed. The meetings are open, and we invite community to join them to be up-to-date with the latest project developments and progress. * TSC Meetings Host responsibility is rotated between the TSC maintainers. * Priority to host is given based on activity: Current Release Owners > Maintainers who weren't in rotation > Other Maintainer Volunteers. * Maintainers are free to decide collectively who would run the next TSC meeting: they can run in pairs, swap. -See [StackStorm TSC Meetings](https://github.com/StackStorm/community/issues/33) for more info about the meeting schedule, calendar, meeting host responsibilities and procedure. +See [StackStorm TSC Meetings](https://github.com/StackStorm/community/issues/33) for more info about the meeting schedule, how to join, calendar, meeting host responsibilities and procedure. ### Maintainer Roles The current list of maintainers is published and updated in [OWNERS.md](OWNERS.md). From 63208b904f77d37974d034e62295abaf1ae20aa4 Mon Sep 17 00:00:00 2001 From: Eugen C <1533818+armab@users.noreply.github.com> Date: Wed, 7 Sep 2022 15:46:07 +0100 Subject: [PATCH 5/5] Update GOVERNANCE.md with the minor wording fixes Co-authored-by: Jacob Floyd --- GOVERNANCE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index cea7b5aceb..8f9d64dfd9 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -11,7 +11,7 @@ This group is responsible for all technical oversight of StackStorm as Open Sour ### TSC Meetings Because of the different schedules and time zones, TSC is keen to prioritize asynchronous collaboration and work. -However, every month, [@StackStorm/tsc](OWNERS.md) members are gathering for `1 hour` to discuss the project problems, roadmap, priorities to help the StackStorm as a project evolve and succeed. +However, every month, [@StackStorm/tsc](OWNERS.md) members gather for `1 hour` to discuss the project problems, roadmap, priorities to help the StackStorm as a project evolve and succeed. The meetings are open, and we invite community to join them to be up-to-date with the latest project developments and progress. * TSC Meetings Host responsibility is rotated between the TSC maintainers.