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

Policies #6

Closed
7 of 8 tasks
wooorm opened this issue Dec 4, 2018 · 9 comments
Closed
7 of 8 tasks

Policies #6

wooorm opened this issue Dec 4, 2018 · 9 comments
Labels
💪 phase/solved Post is done 💬 type/discussion This is a request for comments

Comments

@wooorm
Copy link
Member

wooorm commented Dec 4, 2018

Other than governance (#2), we should draft policies on several things.
In general, I think most policies should be followed by organisations, but I think organizations should be allowed to draft their own policies.

  • GitHub organization policy (Add GitHub policy #5) — Define how the GitHub orgs, teams, humans, and repos are managed
  • project governance grant policy (Add project governance grant policy #7) — define how projects by individuals can move under an organisation
  • npm organization policy — Define how the npm orgs, teams, humans, and repos are managed. Maybe one org with teams for respectively the collective and the organization teams? Or orgs for each org team?
  • on and offboarding policy — define how individuals become members, and members become emeriti
  • .github policy — define how to add contributing, support, issue and pr templates, can be set-up
  • moderation policy — define how violations are handled
  • fund policy — Define who can request an expense on open collective, for what, and who approves them (I think this policy should be followed by the whole collective)
  • consensus seeking policy — define how initiatives are approved or rejects, and which changes require such a process
    ...anything else I’m missing?
@wooorm

This comment has been minimized.

@RichardLitt

This comment has been minimized.

@wooorm wooorm mentioned this issue Dec 5, 2018
wooorm added a commit that referenced this issue Dec 5, 2018
Closes GH-5.
Related to GH-2.
Related to GH-6.

Reviewed-by: John Otander <[email protected]>
Reviewed-by: Stephan Schneider <[email protected]>
Reviewed-by: Christian Murphy <[email protected]>
Reviewed-by: Merlijn Vos <[email protected]>
Reviewed-by: Olivia Hugger <[email protected]>
@RichardLitt

This comment has been minimized.

@wooorm

This comment has been minimized.

RichardLitt added a commit that referenced this issue Feb 21, 2019
See #6. I think that this PR should add it here, and then that we should add it to the other main documentation repositories. I did not see the need to use a different CoC - I think this one should do fine. Note that I also added myself to the moderation team, because I do not like having only one person on it, and I am happy to do this work as needed.

@komaeda what do you think?
@wooorm

This comment has been minimized.

@RichardLitt

This comment has been minimized.

@wooorm

This comment has been minimized.

@RichardLitt

This comment has been minimized.

@wooorm wooorm added 💬 type/discussion This is a request for comments 🙆 yes/confirmed This is confirmed and ready to be worked on help wanted 🙏 This could use your insight or help labels Aug 10, 2019
wooorm added a commit that referenced this issue Aug 20, 2019
Related to GH-6.
Closes GH-17.
wooorm added a commit that referenced this issue Aug 21, 2019
Related-to GH-6.
Closes GH-19.
wooorm added a commit that referenced this issue Aug 23, 2019
Related to GH-6.
Related to GH-17.
Related to GH-29.
wooorm added a commit that referenced this issue Aug 25, 2019
Related to GH-6.
Closes GH-17.

Reviewed-by: John Otander <[email protected]>
Reviewed-by: Merlijn Vos <[email protected]>
Reviewed-by: Christian Murphy <[email protected]>
wooorm added a commit that referenced this issue Aug 26, 2019
Related to GH-6.
Related to GH-17.
Related to GH-29.
Related to GH-32.
wooorm added a commit that referenced this issue Aug 27, 2019
Related to GH-6.
Related to GH-17.
Related to GH-29.
Related to GH-32.

Reviewed-by: Richard Littauer <[email protected]>
Reviewed-by: Christian Murphy <[email protected]>
wooorm added a commit that referenced this issue Aug 28, 2019
Related-to GH-6.
Closes GH-19.
Closes GH-29.

Reviewed-by: Merlijn Vos <[email protected]>
@wooorm
Copy link
Member Author

wooorm commented Aug 28, 2019

I’m closing this because most of these are done, except for the funding policy, which I’ve opened separately as GH-34.

Thanks everyone for voicing your ideas!

@wooorm wooorm closed this as completed Aug 28, 2019
@wooorm wooorm removed the help wanted 🙏 This could use your insight or help label Aug 28, 2019
@wooorm wooorm added ⛵️ status/released and removed 🙆 yes/confirmed This is confirmed and ready to be worked on labels Aug 28, 2019
wooorm added a commit that referenced this issue Aug 29, 2019
Related to GH-6.
Related to GH-17.
Related to GH-29.
Related to GH-32.
Related to GH-33.

Reviewed-by: Merlijn Vos <[email protected]>
wooorm added a commit that referenced this issue Aug 29, 2019
Related to GH-6.
Related to GH-17.
Related to GH-29.
Related to GH-32.
Related to GH-33.
wooorm added a commit that referenced this issue Sep 2, 2019
Related to GH-6.
Related to GH-17.
Related to GH-29.
Related to GH-32.
Related to GH-33.
Closes GH-35.

Reviewed-by: Jonathan Haines <[email protected]>
Reviewed-by: Merlijn Vos <[email protected]>
@wooorm wooorm added the 💪 phase/solved Post is done label May 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💪 phase/solved Post is done 💬 type/discussion This is a request for comments
Development

No branches or pull requests

2 participants