Skip to content
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

Governance page #366

Merged
merged 15 commits into from Apr 4, 2020
Merged

Governance page #366

merged 15 commits into from Apr 4, 2020

Conversation

garbas
Copy link
Member

@garbas garbas commented Mar 25, 2020

This page was inspired by Goverance page on Rust website and replaced/consumed existing Security item from the top navigation bar.

  • RFC Steering Committee needs to be update the page with correct info
  • Security team needs to update the page with correct info
  • Add NixOS release team
  • Infrastructure team
  • nixcon team
  • Add redirects from removed pages to /governance.html

Have I missed any other team?

Those of you reviewing this please try to ignore the design and focus on content.

@github-actions
Copy link
Contributor

@samueldr

This comment has been minimized.

@github-actions
Copy link
Contributor

@github-actions
Copy link
Contributor

github-actions bot commented Apr 1, 2020

@github-actions
Copy link
Contributor

github-actions bot commented Apr 1, 2020

@garbas
Copy link
Member Author

garbas commented Apr 1, 2020

Ready for final review

governance.tt Outdated Show resolved Hide resolved
governance.tt Outdated Show resolved Hide resolved
governance.tt Outdated Show resolved Hide resolved
governance.tt Outdated Show resolved Hide resolved
governance.tt Outdated Show resolved Hide resolved
governance.tt Outdated Show resolved Hide resolved
governance.tt Outdated Show resolved Hide resolved
@davidak
Copy link
Member

davidak commented Apr 1, 2020

This already looks great.

I actually had the idea to create such a site last year (#284):

We should describe the organization structure on the website, like the RFC Steering Committee, Nixpkgs Maintainers (New GitHub group) etc. [...] so we probably need a new page. Maybe the Foundation could be just one section on that page.

"Nixpkgs Maintainers" is currently missing, but they are an important part of the ecosystem.

Until we can get a list of maintainers from ElasticSearch and have a good description what these people do, we can just add it as section with title "Nixpkgs Maintainers" and text "The package maintainers keep the packages up-to-date and fix reported problems." without further link...

I think that is better than not mentioning them.

Update: I see now what you meant in the chat. They are not really a team that meet and work together, so it don't fit under the heading "Teams" on the site. We could just ignore that and improve later (i don't have an idea how) or don't add it there. The package maintainers can also be mentioned in a Contribution guide...

@github-actions
Copy link
Contributor

github-actions bot commented Apr 2, 2020

@worldofpeace
Copy link
Contributor

@davidak I think @garbas mentioned (to me in private) this would go in the community page.

teams/nixos_release.tt Outdated Show resolved Hide resolved
teams/nixos_release.tt Outdated Show resolved Hide resolved
@garbas
Copy link
Member Author

garbas commented Apr 2, 2020

on some pages I call people by full name somewhere by irc nick somewhere else by github handle. I guess I should choose one :)

@worldofpeace
Copy link
Contributor

@garbas I think the community would understand full name and github handle in parenthesis.

@worldofpeace
Copy link
Contributor

I do know of at least two people in the community that want to remain semi-anonymous, so in that case you should just use their GitHub. (I believe one of them is in the webpage actually)

@davidak
Copy link
Member

davidak commented Apr 2, 2020

@davidak I think @garbas mentioned (to me in private) this would go in the community page.

yes, that makes sense. since the package maintainers are normal community members and there is no team that governs them. we might want to establish a packaging working group later to coordinate getting maintainers for abandoned packages, define workflow and responsibility of maintainers etc

@worldofpeace
Copy link
Contributor

@davidak I think @garbas mentioned (to me in private) this would go in the community page.

yes, that makes sense. since the package maintainers are normal community members and there is no team that governs them. we might want to establish a packaging working group later to coordinate getting maintainers for abandoned packages, define workflow and responsibility of maintainers etc

Yep, I agree with you on all points.

@nixos-discourse
Copy link

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/marketing-team-meeting-minutes-2/6537/1

@ryantm
Copy link
Member

ryantm commented Apr 3, 2020

Another official source of governance is Discourse admins and moderators:

Admins:
ryantm
edolstra
grahamc
zimbatm

Moderators:
mic92

@ryantm
Copy link
Member

ryantm commented Apr 3, 2020

I added a PR for it #378

@github-actions
Copy link
Contributor

github-actions bot commented Apr 3, 2020

@ryantm
Copy link
Member

ryantm commented Apr 3, 2020

Sorry, I was going to use the CI to test it first, it looks like it isn't good yet.

@ryantm
Copy link
Member

ryantm commented Apr 3, 2020

okay #379 is better now (I actually tested it locally)

cc @garbas

@garbas
Copy link
Member Author

garbas commented Apr 3, 2020

No worries. Thank you a ton for adding it.

@github-actions
Copy link
Contributor

github-actions bot commented Apr 3, 2020

@garbas
Copy link
Member Author

garbas commented Apr 4, 2020

I do know of at least two people in the community that want to remain semi-anonymous, so in that case you should just use their GitHub. (I believe one of them is in the webpage actually)

I'll use the following format:

  • link to discourse
  • full name published on discourse
  • IRC nickname

I think that would provide all information to be able to contact and follow how people want to be presented.

@github-actions
Copy link
Contributor

github-actions bot commented Apr 4, 2020

@garbas garbas merged commit 8207cb3 into master Apr 4, 2020
@garbas garbas deleted the governance branch April 4, 2020 04:08
@garbas garbas moved this from Confirmed to Done in TODO Feb 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
TODO
Done
Development

Successfully merging this pull request may close these issues.

None yet

7 participants