-
Notifications
You must be signed in to change notification settings - Fork 42
Update governance docs #729
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
Conversation
docs/community/governance.md
Outdated
developers can request or be invited to become active core developers at | ||
a later date and with consensus from currently active core developers. | ||
|
||
For a full list of core developers see our [About Us](team) page. |
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.
either "about the project and team" or just "about"? "About Us" doesn't exist as a string anywhere there.
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.
"About Us" doesn't exist as a string anywhere there.
Well maybe it should 😆
Updated in latest commit.
docs/community/governance.md
Outdated
The SC may be contacted at `napari-steering-council@googlegroups.com`. | ||
Or via the [@napari/steering-council](https://github.com/orgs/napari/teams/steering-council) GitHub team. For a list of the current SC see our [About Us](team) page. | ||
The SC may be contacted at `napari-steering-council@googlegroups.com`. For a list of the current | ||
SC see our [About Us](team) page. |
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.
As above
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.
Done!
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.
very minor optional nitpicky suggestion, otherwise 👍
@@ -95,8 +100,8 @@ then admission to the SC by consensus. During that time deadlocked votes of the | |||
be postponed until the new member has joined and another vote can be held. The IFP seat | |||
is elected by the IFP Advisory Council. | |||
|
|||
The SC may be contacted at `napari-steering-council@googlegroups.com`. | |||
Or via the [@napari/steering-council](https://github.com/orgs/napari/teams/steering-council) GitHub team. For a list of the current SC see our [About Us](team) page. | |||
The SC may be contacted at `napari-steering-council@googlegroups.com`. For a list of the current |
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.
Were we switching to a (at)napari.org adress for this?
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.
@psobolewskiPhD I think we decided not to (at least for forseeable future) because of the issues with administering private groups or something?
References and relevant issues
Closes #206
Description
This PR makes a couple of updates to our About Us, Governance and Core Dev Guide pages:
In #206 there is also mention of the community calendar being broken, but I just checked on incognito mode and it appears correct to me, so I believe that issue has been addressed.