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

Edit governance doc to better fit sub-team structure/powers #1543

Closed
drjwbaker opened this issue Nov 8, 2019 · 8 comments
Closed

Edit governance doc to better fit sub-team structure/powers #1543

drjwbaker opened this issue Nov 8, 2019 · 8 comments
Assignees

Comments

@drjwbaker
Copy link
Member

Spinning out from #1491 a proposal for editing the Governance document:

  1. add 'Sub-team calls' to our list of 'Venues for Discussion'.
  2. edit 'Monthly Skype calls' to 'Monthly Skype calls (including sub-team reports)'
  3. edit:

Members who have a specific interest in an issue (whether in approval or in dissent) are expected to make their voice heard on one of these venues. If any team members object to a course of action, we will not move forward without addressing those objections.

to:

Members who have a specific interest in an issue (whether in approval or in dissent) are expected to make their voice heard on one of these venues. Sub-teams are empowered to make decisions on behalf of the project (with the exception of policy level changes, see below), but must do so in a sufficiently transparent way that if any team members object to a course of action, we will not move forward without addressing those objections."

Pinging team leads: @mdlincoln @svmelton @rivaquiroga @spapastamkou @jenniferisasi @JMParr for comment.

@acrymble
Copy link

I support this. I suspect there are situations though where someone may object but we may have a legal obligation or an extremely compelling practical reason for moving ahead anyway. Maybe j ust say attempting to address those objections?

@drjwbaker
Copy link
Member Author

drjwbaker commented Nov 19, 2019

Members who have a specific interest in an issue (whether in approval or in dissent) are expected to make their voice heard on one of these venues. Sub-teams are empowered to make decisions on behalf of the project (with the exception of policy level changes, see below), but must do so in a sufficiently transparent way that if any team members object to a course of action, we will not move forward without seeking to address those objections.

Better?

@drjwbaker
Copy link
Member Author

@acrymble did this not get discussed at #1538?

@acrymble
Copy link

Sorry @drjwbaker it looks like we missed it somehow.

@svmelton
Copy link
Contributor

No objections here!

@jenniferisasi
Copy link
Contributor

No objections.

@amsichani
Copy link
Contributor

no objections - thanks for this!

@drjwbaker
Copy link
Member Author

I've made the edit to the Governance Document adding the text above about sub-teams. Happy to reopen if anyone has an objection.

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

No branches or pull requests

5 participants