[vote required to merge] 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.
governance/executive-council.md
Outdated
|
|
||
| ### 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
There was a problem hiding this comment.
I think we can flip these sections, starting with 'Decisions requiring a vote' and then go into how decisions are made.
So
How the Executive Council makes decisions
The Executive Council is required to review and approve decisions affecting the fiduciary aspects of the organization, this includes mission/vision/values, governance policies, budget, Executive Director compensation, and new significant strategic initiatives. The Executive Council also supports the Executive Director by serving as a resource for input when needed.
All decisions made by the Executive Council must align with the legal
obligations and policies of pyOpenSci’s fiscal sponsor—Community Initiatives.
This ensures compliance with overarching governance structures and financial
responsibilities.
Decisions requiring an Executive Council vote
what we already have in this section
Decision making process
The topics above require a motion and a vote for approval. Motions and approval can be made in Executive Council meetings or asynchronously via email or Slack. Motions and votes will be noted in the EC meeting minutes.
Collaboration with the Executive Director
...
- Strategic decisions about pursuing proposals or writing grants.
- Substantial changes to pyOpenSci programs.
In these cases, lazy consensus can be employed. About lazy consensus (noted below where to add that section)
lwasser
changed the title
@kcranston, I've reorganized the home page to include more content in each section. Hopefully, that addresses your issue. I also noticed there were a few incorrect links there as well! |
lwasser
changed the title
governance/executive-council.md
Outdated
| collaborative input. Examples include: | ||
|
|
||
| * Significant public-facing changes to the pyOpenSci website. | ||
| * Decisions impacting staff or human resources (e.g., hiring or termination). |
There was a problem hiding this comment.
| * Decisions impacting staff or human resources (e.g., hiring or termination). |
governance/executive-council.md
Outdated
| ## Collaboration between the Executive Director and the Executive Council | ||
|
|
||
| The Executive Director may request feedback | ||
| from the Executive Council on significant or public-facing decisions; these types of decisions do not require a formal vote. These discussions should |
There was a problem hiding this comment.
Remove and put in operations "These discussiosn should occur in the .... "
governance/executive-council.md
Outdated
| while minimizing unnecessary delays. | ||
|
|
||
|
|
||
| ## How the Executive Council meets and communicates |
There was a problem hiding this comment.
And then after adding lazy consensus move this to an operations section of the guide - maybe at the bottom of this page --
add a callout - everything below is just operations and can be changed as need be. everything above is voted on and requires a vote to change
governance/executive-council.md
Outdated
| obligations and policies of pyOpenSci’s fiscal sponsor—[Community Initiatives](https://communityin.org/). | ||
| ::: | ||
|
|
||
| ## Collaboration between the Executive Director and the Executive Council |
There was a problem hiding this comment.
Move this section into the "operations at the bottom too" .
and remove the staff lines from the document. (we can use may request feedback - in the other operations section).
There was a problem hiding this comment.
Moved this and lazy consensus to the operations section.
| @@ -0,0 +1,261 @@ | |||
| (pyos-executive-council)= | |||
There was a problem hiding this comment.
Add a section - that says voted on and has a date... between operations and governance part. say revised on....
|
PR next steps: leah will make structure changes as noted in the comments. leave a link in the slack EC channel and then we will vote on the pr / merge. |
|
|
||
| The pyOpenSci Executive Council uses a shared **[Google Drive](google-drive)** within the pyOpenSci Google Workspace to store and share documents. This includes meeting notes, agendas, and other important materials. Members are encouraged to access and update shared resources using the shared Drive. | ||
|
|
||
| ### Selection of Executive Council members |
There was a problem hiding this comment.
This is a part of the governance structure, so we can move this section up to the top section under 'Decision-making process'
| As needed, the Executive Council may conduct periodic evaluations to ensure its composition continues | ||
| to meet the organization’s needs. | ||
|
|
||
| ### Onboarding and offboarding Executive Council members |
There was a problem hiding this comment.
This section can stay here, because it's about operations.
|
|
||
| ### Decision-making process | ||
|
|
||
| The topics above require a motion and a vote for approval. Motions and votes can be made in Executive Council meetings or via email or Slack. Motions and votes will be noted in the Executive Council meeting minutes. |
There was a problem hiding this comment.
... via email, Slack or GitHub.
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.