Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: loosen TC activity rules #5510

Merged
merged 1 commit into from
Mar 14, 2024
Merged

docs: loosen TC activity rules #5510

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions Contributing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,11 +118,13 @@ nominate someone to take their place.
TC members will be added as admin's on the Github orgs, npm orgs, and other resources as
necessary to be effective in the role.

To remain "active" a TC member should have participation within the last 6 months and miss
no more than three consecutive TC meetings. Members who do not meet this are expected to step down.
If A TC member does not step down, an issue can be opened in the discussions repo to move them
to inactive status. TC members who step down or are removed due to inactivity will be moved
into inactive status.
To remain "active" a TC member should have participation within the last 12 months and miss
Copy link
Member

@jonchurch jonchurch Feb 28, 2024 •
edited
Loading

Choose a reason for hiding this comment

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

I think we can hold off for now, with a fast follow in Season 0 to firm this up.

The penalty for inactivity requires a PR to be opened to remove someone who has not met the attendance criteria, and does not choose to resign. (it is also not spelled out WHO can open or approve that PR hehe)

I am confident that the current TC will not inactive someone if they miss the next couple meetings.

Churn in these policies need to be avoided lest we hinder their gravity. Let's make sure that the next change we make to this clause is one that balances our goals here of encouraging activity/showing up, and accomodating people's lives as this is a volunteer position. As well as choosing language we won't have to touch again for a long time unless something drastic changes.

Copy link
Member

@jonchurch jonchurch Feb 28, 2024 •
edited
Loading

Choose a reason for hiding this comment

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

A first stab from me:

"To promote active participation, TC members must attend a minimum of 75% of official monthly meetings annually. To account for time zone challenges, members may 'officially attend' by submitting detailed comments on the meeting agenda at least 12 hours before the meeting. This will count as attendance for maintaining active status.

Ad hoc working sessions are vital for progress but are not mandatory and do not count towards the monthly meeting attendance requirement. Official decisions requiring consensus or vote are reserved for monthly meetings, except under urgent circumstances, where a predefined exception process will be followed."

The bolded part here is something that we can omit, but should definitely be broached and put into writing. Im guessing we could strike that rule, and would have to depending on how "official decisions" are defined. Is merging a PR an official decision? No. Accepting a new TC member? Yes. Emptying the (nonexistent) bank account? Yes. Merging a PR to drop Node version support outside of agreed to timelines? Yes

Copy link
Member Author

Choose a reason for hiding this comment

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

Oh I like this more detailed version!

no more than six consecutive TC meetings. Our goal is to increase participation, not punish
people for any lack of participation, this guideline should be only be used as such
(replace an inactive member with a new active one, for example). Members who do not meet this
are expected to step down. If A TC member does not step down, an issue can be opened in the
discussions repo to move them to inactive status. TC members who step down or are removed due
to inactivity will be moved into inactive status.

Inactive status members can become active members by self nomination if the TC is not already
larger than the maximum of 10. They will also be given preference if, while at max size, an
Expand Down
Loading