You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi everyone - in a recent meeting that I attended I shared that I was working with @marthacryan to write some documentation for best practices surrounding the process of starting a new committee or working group. Happy to share we've created a template for a few things. Note that all of these should be considered in a draft state and it still needs to be approved by the Executive Council. Sharing because it felt like a great opportunity to get this group involved early. Note that I'm not a software engineer and I find Google Docs easier to collaborate in (compared to GH). I do envision these documents would be added to the Jupyter Governance documentation. Documents are set with permissions that are open for anyone to comment.
These are great, and should help make starting new bodies much easier in the future. I've read through them and made some notes about a few items we can add to the Docs Working Group, thanks for sharing this :)
Many thanks! I've added the checklist to GH but I still need to figure out a place for the charter draft and the other items. Part of this is talking with the other folks on the Executive Council to figure out the right place for these documents. I am not sure if changes to the Governance model docs require a joint vote of the EC and SSC. That seems like a high bar for requesting changes. Anyway, various things in the works and I wanted to share them all while they're in progress because the timing
Hi everyone - in a recent meeting that I attended I shared that I was working with @marthacryan to write some documentation for best practices surrounding the process of starting a new committee or working group. Happy to share we've created a template for a few things. Note that all of these should be considered in a draft state and it still needs to be approved by the Executive Council. Sharing because it felt like a great opportunity to get this group involved early. Note that I'm not a software engineer and I find Google Docs easier to collaborate in (compared to GH). I do envision these documents would be added to the Jupyter Governance documentation. Documents are set with permissions that are open for anyone to comment.
Charter Draft
Voting
General Overview Draft
Goal of Documentation
Audience
The text was updated successfully, but these errors were encountered: