[dec 1 review] feat: add Executive Council page to handbook #113
Conversation
lwasser
changed the title
There was a problem hiding this comment.
My only over-arching comment is how this is linked to the navigation in the handbook. It looks like this info will be found via the "Structure & Values" heading in the top navbar, but not via the Governance box in the main part of the page? I would expect to find it in both places.
|
|
||
| The Executive Director is currently a voting member of the Executive Council for items unrelated to their salary and accountability. | ||
|
|
||
| The Executive Council holds broad expertise in building and running a scientific / data science nonprofit organization. It is complemented by the [Advisory Council](advisory-council), which offers domain-specific expertise, guidance, and input. |
There was a problem hiding this comment.
do we even need 'scientific / data science' here? I could imagine very good EC members from other domains
|
|
||
| ## Executive Council Roles & Responsibilities | ||
|
|
||
| Each Executive Council (EC) member dedicates no more than **four to six hours per month** to pyOpenSci activities, including meeting attendance. Executive Council members are expected to fulfill the following responsibilities: |
There was a problem hiding this comment.
I think 4-6 hours on top of meeting attendance (esp if this is phrased as a hard upper bound)
There was a problem hiding this comment.
@kcranston so you think 4-6 hours + 1.5 hours a month for a meeting? You would know the time commitment better than I would at this point!! We could also write this as it dedicates approximately 4-6 hours a month. I just want to correctly represent the actual time!
There was a problem hiding this comment.
Hmmm... you are probably right that the 4-6 hour estimate includes meeting time. Let's leave this as is.
|
|
||
| ### Decision-making process | ||
|
|
||
| The Executive Council generally follows a **lazy consensus** approach for decision-making: |
There was a problem hiding this comment.
this is true, except for the cases listed below that require a vote
| - Notify the pyOpenSci's Fiscal Sponsor (Community Initiatives) of any changes in roles | ||
| that impact the chair position or budget oversight responsibilities. | ||
|
|
||
| 4. **Welcome and integration**: |
There was a problem hiding this comment.
to the council, and to the pyOS community?
lwasser
changed the title
This PR adds a new page that overviews how the EC works to our guidebook. I also fixed some typos and coordinated content between this page and the main governance page while adding some target links to other pages.