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

Make a separate "Teams" page #1511

Open
1 task
fricklerhandwerk opened this issue Jul 17, 2024 · 0 comments
Open
1 task

Make a separate "Teams" page #1511

fricklerhandwerk opened this issue Jul 17, 2024 · 0 comments
Labels

Comments

@fricklerhandwerk
Copy link
Contributor

Problem
The community page is currently about too many things:

  • communication channels
  • NixCon
  • meetups
  • RFC process
  • teams
  • foundation

Proposal

Split out the Teams part.

Ideally also move the foundation stuff on a separate page linked from the footer.
The RFC process diagram could go into the steering committee page.

I'd just do it myself, but the website has so much design stuff that one can't just move a bunch of text to a different place, and I can't make the time to figure out what to do until it looks correct. (Side note: It would be great if the contribution process would boil down to moving text around.)

Additional context
There were two notable discussions on the role of teams in 2023:

My takeaway is that we need to help people doing the technical work to get more visibility and access to those interested in helping out, and those interested in helping out a way to find people doing the technical work.

Yesterday I discussed with @imincik that we should emphasize the existence of active groups working on particular things, and and that joining one is a fast track to making change happen without getting frustrated. A separate navigation item would be a first step in that direction.

  • I already created a Pull Request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant