8000 Update governance docs by DragaDoncila · Pull Request #729 · napari/docs · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

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

Merged
merged 2 commits into from
Jun 11, 2025
Merged

Conversation

DragaDoncila
Copy link
Contributor

References and relevant issues

Closes #206

Description

This PR makes a couple of updates to our About Us, Governance and Core Dev Guide pages:

  • Adds @lucyleeow to the emeritus core developer list, as she has stepped back from her active role 🥹
  • Adds copy about emeritus core developers being able to request or be invited to become active again to the governance doc. Improves the language in the core dev guide to match.
  • Removes mentions of our github teams from the docs. Looking at GitHub's docs it's not possible to make organization teams visible to the public, they can only be made visible to other organization members. I had a look as to whether we could use organization members as our GitHub core developer listing (this would require a LOT of tidying up, but could be done). However, this requires each individual member to change their own organization membership to public (go to the people page in incognito mode to see what the public sees). If we are happy to change the org members to only ever include active core devs and each member is happy to set their membership to public, we could use this as our listing. For now, I've removed mentions of the teams, and just linked to the About Us page.

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.

@github-actions github-actions bot added the documentation Improvements or additions to documentation label Jun 6, 2025
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.
Copy link
Member

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.

Copy link
Contributor Author

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.

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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As above

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done!

Copy link
Member
@jni jni left a 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 👍

@jni jni added this to the 0.6.2 milestone Jun 6, 2025
@@ -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
Copy link
Member

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?

Copy link
Contributor Author

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?

@DragaDoncila DragaDoncila merged commit 9abdf99 into napari:main Jun 11, 2025
8 checks passed
@DragaDoncila DragaDoncila deleted the update-governance branch June 11, 2025 05:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DOC - Governance documentation is outdated
5 participants
0