-
Notifications
You must be signed in to change notification settings - Fork 60
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
process: Add initial onboarding document for incoming TAC members #429
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice document. As a new TAC member, this guide was already valuable for me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @justaugustus ! I just have a minor formatting nit.
process/tac-onboarding.md
Outdated
|
||
It covers details on topics such as how we make decisions, technical initiative lifecycles, and the funding process. | ||
|
||
## Open questions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ossf/tac (especially continuing members) — Please take a look at this section in particular during review and answer what you can.
Also, feel free to ask additional questions!
We can either choose to try to get everything answered this round or I can open an issue for follow-ups, so we don't block merge.
process/tac-onboarding.md
Outdated
|
||
## Open questions | ||
|
||
- Are there private mailing lists? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the TAC private mailing list is managed by OpenSSF staff.
process/tac-onboarding.md
Outdated
- Are there private mailing lists? | ||
- Are there additional access requirements not accounted for in this document? | ||
- What are our moderation responsibilities and privileges (GitHub, mailing lists, Zoom)? | ||
- How do we manage rescheduling the TAC meeting to accommodate timezones and/or new member obligations? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this one is also handled by OpenSSF staff.
process/tac-onboarding.md
Outdated
|
||
- Are there private mailing lists? | ||
- Are there additional access requirements not accounted for in this document? | ||
- What are our moderation responsibilities and privileges (GitHub, mailing lists, Zoom)? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure we ever created a moderator schedule. As far as privileges are concerned, I believe we can open a meeting, etc. I believe only staff can create repos, mailing lists, etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me! I added a few minor edit suggestions. I believe the open questions have largely been answered, at least enough for us to publish a v1. @justaugustus let us know if there are additional open questions, or if the open questions have been answered to your satisfaction, and feel free to update the open questions section accordingly.
Signed-off-by: Stephen Augustus <[email protected]>
Signed-off-by: Stephen Augustus <[email protected]>
Co-authored-by: Marcela Melara <[email protected]> Co-authored-by: Zach Steindler <[email protected]> Signed-off-by: Stephen Augustus <[email protected]>
Signed-off-by: Stephen Augustus <[email protected]>
625ebad
to
3195466
Compare
@steiza — I've dropped the "Open questions" section and opened #430 to track any follow-ups.
Agreed. Merging, as we have multiple approvals here. |
I'm not sure we should keep maintaining that file but as things stand I should point out that this should have included a new entry into CHANGELOG.md |
Part of #426.
cc: @ossf/tac