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.

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

Simplify docs around Chair election, roles, and responsibilities #432

Merged
merged 4 commits into from
Jan 24, 2025

Conversation

justaugustus
Copy link
Member

This is a follow-up to @marcelamelara's review comment around simplification of references to TAC Chair roles, responsibilities, and election process.

ref: #430

@justaugustus justaugustus requested a review from a team as a code owner January 9, 2025 02:09
@justaugustus justaugustus mentioned this pull request Jan 9, 2025
1 task
After the results are announced the TAC members will elect a Chair and a Vice Chair with 1 week for nominations and 1 week for votes. Results may be announced when all votes are cast. The candidate with the most votes will serve as Chair and the second as Vice Chair. The Chair may however choose to swap seat with the Vice Chair if agreed by the Vice Chair.
After the results of the community elections and Governing Board appointments are announced, the TAC members will elect a [Chair and a Vice Chair](/process/tac-member-R&Rs.md#tac-chair).

The TAC Chair nomination period shall commence as soon as new TAC members are seated (typically, at the beginning of the year) and shall conclude at the end of the first TAC meeting of the year.
Copy link
Member Author

Choose a reason for hiding this comment

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

@ossf/tac — I've edited this section to reflect what we're currently in the process of doing, as opposed to the one week for nominations and one week for votes.

Happy to revert that piece, but calling it out, as it's a decision point that merits discussion.

Copy link
Contributor

Choose a reason for hiding this comment

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

This is fine with me but I have to say that we've got to do better at following whatever process we have. This hasn't been the case unfortunately. We just can't keep changing our documentation to match what we did just because we ignored our documented process. It's fine to change our process of course but it's got to be intentional.

Copy link
Contributor

@marcelamelara marcelamelara Jan 9, 2025

Choose a reason for hiding this comment

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

We still did take ~1 week for nominations (it was relatively informal) prior to the Jan 7 TAC meeting, and are taking 1 week for voting. So, I actually don't think that's changed. And we won't be concluding this year's election by the first TAC meeting, but I'm ok with bounding the timeframe for the election to the second TAC meeting. The biggest change I see is the involvement of OSSF staff this year. In the past, voting was done "internally" within the TAC.

EDIT: to be clear, given that we actually did follow the documented process relatively well, I think we need to keep that text in the documentation, and just refine it with the time bound.

Copy link
Member Author

Choose a reason for hiding this comment

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

And we won't be concluding this year's election by the first TAC meeting [...]

@marcelamelara — just a point of clarification, the proposed text says that:

The TAC Chair nomination period [...] shall conclude at the end of the first TAC meeting of the year.

i.e., nominations need to be in by the end of the first meeting so that we can complete elections ahead of the second meeting

I'll refine the language a bit more based on the other feedback.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ah! Thanks for clarifying, I misread that. I'm do worry that bounding nominations to the first TAC meeting may end up giving the new TAC only a couple of days (depending on the meeting schedule), but I'm generally still ok with saying that the TAC SHOULD aim to complete the chair/vice-chair election process by the second TAC meeting of the year.

After the results are announced the TAC members will elect a Chair and a Vice Chair with 1 week for nominations and 1 week for votes. Results may be announced when all votes are cast. The candidate with the most votes will serve as Chair and the second as Vice Chair. The Chair may however choose to swap seat with the Vice Chair if agreed by the Vice Chair.
After the results of the community elections and Governing Board appointments are announced, the TAC members will elect a [Chair and a Vice Chair](/process/tac-member-R&Rs.md#tac-chair).

The TAC Chair nomination period shall commence as soon as new TAC members are seated (typically, at the beginning of the year) and shall conclude at the end of the first TAC meeting of the year.
Copy link
Contributor

Choose a reason for hiding this comment

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

This is fine with me but I have to say that we've got to do better at following whatever process we have. This hasn't been the case unfortunately. We just can't keep changing our documentation to match what we did just because we ignored our documented process. It's fine to change our process of course but it's got to be intentional.

@marcelamelara marcelamelara added the Content Updates/additions to TAC content/process. Must include a changelog entry. Needs 3 approvals. label Jan 9, 2025
Copy link
Contributor

@SecurityCRob SecurityCRob left a comment

Choose a reason for hiding this comment

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

Very nice to see the continued refinement of our processes. Thanks team!

Copy link
Member

@steiza steiza left a comment

Choose a reason for hiding this comment

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

Thank for putting this together! I have a couple of minor questions, and it looks like maybe there's some other comments / suggested changes to resolve before a final review?

elections/tac-and-scir-election-process.md Outdated Show resolved Hide resolved
process/tac-member-R&Rs.md Show resolved Hide resolved
Co-authored-by: Zach Steindler <[email protected]>
Co-authored-by: Georg Kunz <[email protected]>
Signed-off-by: Stephen Augustus <[email protected]>
@justaugustus
Copy link
Member Author

@ossf/tac — I've processed the review feedback and this should be ready to merge now.

Copy link
Member

@steiza steiza left a comment

Choose a reason for hiding this comment

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

Looks great - thanks!

Copy link
Contributor

@gkunz gkunz left a comment

Choose a reason for hiding this comment

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

Thank you driving this

Copy link
Contributor

@lehors lehors left a comment

Choose a reason for hiding this comment

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

At this point there are more lines being added than deleted so I'm not sure the title is quite right - it probably should say something like "cleanup docs ..." - but that's a detail that I'm only pointing out because I tend to be pedantic about this kind of stuff. ;-)
It LGTM otherwise.
Thanks!

Copy link
Contributor

@mlieberman85 mlieberman85 left a comment

Choose a reason for hiding this comment

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

LGTM!

Copy link
Contributor

@marcelamelara marcelamelara left a comment

Choose a reason for hiding this comment

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

Thanks @justaugustus ! LGTM

@marcelamelara marcelamelara merged commit 62ebb44 into ossf:main Jan 24, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content Updates/additions to TAC content/process. Must include a changelog entry. Needs 3 approvals.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants