Add a section saying who all maintainers of this website.

[asquare14]

A small photo with a short description and email. In case, anyone has questions they can message us.

[nitink4472]

I would like to work on this issue but tell me as i'm a newcomer that, Are maintainers the same as contributors/backers?

[jancborchardt]

Since contributing to Open Source Diversity can have many different means, lots of which will not necessarily mean doing a lot on the website, I’d prefer if we don’t list specific people as maintainers. :) Open Source Diversity is meant as a hub by and for people working to push inclusion & diversity in open source rather than a specific group or project.

(We already do this to a certain extent in the readme of this repository with the "backers" widget from Open Collective: https://github.com/opensourcediversity/opensourcediversity.org#-contributors-backers--sponsors )

What does everyone think? @sleepypioneer @princiya @alicetragedy @Haimchen & others

[alicetragedy]

Sooo I think both perspectives are valid. I definitely think that adding people as “maintainers” can a) put a lot of responsibility (potentially unwanted) on certain folks and b) lead to forgetting people who also played a big part.
I also agree that contributing and maintaining a group isn’t always visible work (or the type of work we assume when we call someone a “maintainer”).

I do think it might be useful though to have a few people listed either on the site or on the repo, particularly in the context of looking into Code of Conduct violations and enforcing the Code of Conduct for our community. However maybe this is part of a bigger conversation? Don’t know how y'all feel about this.

[sleepypioneer]

I feel somewhere in the middle 🙃 I think we are certainly missing some governance around how folks can contribute, who by, and how decisions are made. We currently have enforced 2 reviews on a PR but no documentation on by whom they should be done, I think the concept here was to have a democratic approach but I see with differing opinions we do need some facilitation which is something maintainers could have the responsibility for. We could agree that a quorum has been to made on larger decisions (such as rewrites, and new features) meaning that if there are 4 maintainers at least two must agree to it. (I chose 4 as a random number, this could be more). Explicit rules help those new to the projects, especially folks less confident to ask, while still allowing anyone to contribute.

Another thing I see we could do is to add the Wiki feature to the repository and start to add this information there. We also need to add a contributor file so all folks contributing code or otherwise can get recognition. Sauce labs have a tool (written by Paloma - a member of Berlin PyLadies) that checks your open-source project to see what is missing from it to help folks contribute so we could also run it on the website repo github.com/saucelabs/check-my-repo

I definitely do not want my personal email listed here. I would suggest we consider email groups for things like a CoC enforcement group. I think this is an important conversation to have because having a CoC with no clear route for enforcement is unfortunately close to having none at all :(

[Shu12388y]

@asquare14 can you assign this issue to me

[Shu12388y]

@jancborchardt can you assign this issue to me

[jonatoni]

I do agree we are missing some governance for OSD - but for now I would keep it as it is because we don't have the capacity for it. Whenever we feel ready and have someone to lead the efforts for creating some governance we can always come back to this discussion. For now I'm closing the issue as stale.