Repository navigation
meta: add community health files for org README #10
Description
On the landing page of the organization we have an opportunity to bring attention to things like CoC, events, and other quick links - as well as a place to display sponsors.
Some examples from across the GitHub land:
github.com/microsoft
github.com/django
github.com/litestar-org
github.com/getsentry
There are two distinct customization here: internal and public.
This means we could have an internal (anyone in the python organization) README with some nice-to-knows or events to keep track of (buildbot outage windows, reminders to enable 2FA, etc.) and a public one with the aforementioned links.
Some documentation about it:
Reacted by SYAIFULNIZAM BIN SHAMSUDIN, Mike Fiedler and Maciej Olko
Metadata
Metadata
Assignees
Labels
No labels
Activity
aijadugar commentedon Oct 3, 2024
ALL OK...#10
I tried to make it super best from my side...
Thanks, to make my 1st open-source contribution...
aijadugar commentedon Oct 5, 2024
@JacobCoffee are you reviewed that...
JacobCoffee commentedon Oct 8, 2024
I'm not the deciding person here :) But yes something along the lines of what you have. I was curious if we are able to incorporate sponsors here which would require PSF staff input and they are out for the month.
Create CODE_OF_CONDUCT.md
nedbat commentedon Oct 6, 2026
This idea came up at today's Docs community meeting. I would focus the page on people interested in contributing, since they are already at github.com. So I wouldn't include marketing copy, and I wouldn't include sponsors. Of the four examples, Django seems the right flavor.
In today's discussion, this came up because someone new to contribution wasn't sure where to start. Coming to the organization page and searching for "doc" to find a repo goes to a (slightly) wrong place.
nedbat commentedon Oct 6, 2026
Here's another example of an org README that focuses on contributors: https://github.com/openedx/