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

Add organizations policy #29

Merged
merged 2 commits into from
Aug 28, 2019
Merged

Add organizations policy #29

merged 2 commits into from
Aug 28, 2019

Conversation

wooorm
Copy link
Member

@wooorm wooorm commented Aug 21, 2019

Rendered version

This document is written in accordance with unifiedjs/rfcs#2 and correlates with the (newly rewritten) GH-17 Members policy.

Related-to GH-6.
Related-to GH-17.
Closes GH-19.

Related-to GH-6.
Closes GH-19.
@wooorm wooorm added 🦋 type/enhancement This is great to have help wanted 🙏 This could use your insight or help 📚 area/docs This affects documentation 🙆 yes/confirmed This is confirmed and ready to be worked on 👩‍⚕ area/health This affects community labels Aug 21, 2019
@wooorm wooorm requested a review from a team August 21, 2019 19:54
wooorm added a commit that referenced this pull request Aug 22, 2019
* Add changes proposed in unifiedjs/rfcs#2
* Remove draft status
* Remove things now described in `members.md` and `organizations.md`
* Refactor things

Related-to unifiedjs/rfcs#2.
Related-to GH-17.
Related-to GH-29.
Copy link
Member

@Murderlon Murderlon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

wooorm added a commit that referenced this pull request Aug 23, 2019
Related to GH-6.
Related to GH-17.
Related to GH-29.
@wooorm wooorm mentioned this pull request Aug 23, 2019
wooorm added a commit that referenced this pull request Aug 25, 2019
* Add changes proposed in unifiedjs/rfcs#2
* Remove draft status
* Remove things now described in `members.md` and `organizations.md`
* Refactor things

Related-to unifiedjs/rfcs#2.
Related-to GH-17.
Related-to GH-29.
Closes GH-31.

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

wooorm commented Aug 26, 2019

Hey folks! Anyone else with thoughts on this?

As an interesting super meta aside: with my research into governance I came across Warnock’s dilemma:

The problem with no response is that there are five possible interpretations:

  • The post is correct, well-written information that needs no follow-up commentary. There's nothing more to say except "Yeah, what he said."
  • The post is complete and utter nonsense, and no one wants to waste the energy or bandwidth to even point this out.
  • No one read the post, for whatever reason.
  • No one understood the post, but won't ask for clarification, for whatever reason.
  • No one cares about the post, for whatever reason.

Let me know if this is nonsense, unclear, or unneeded! That’s valuable feedback as well!

wooorm added a commit that referenced this pull request Aug 26, 2019
Related to GH-6.
Related to GH-17.
Related to GH-29.
Related to GH-32.
@wooorm wooorm mentioned this pull request Aug 26, 2019
@ChristianMurphy
Copy link
Member

Warnock’s dilemma

For me, it's time constraints.
These policies have looked pretty good thus far, they also take time to read, and there have been quite a few coming through lately.

It's great that you're able to work on this full time.
For myself, I'm reviewing this on personal/volunteer time.
It takes a while to get a chunk of time set aside to review these in depth.

@wooorm
Copy link
Member Author

wooorm commented Aug 27, 2019

@ChristianMurphy Right, of course! 👍

Lazy consensus needs a wait-time to work. That’s typically 2 or 3 days, and can be fast-tracked for small things like typo fixes. I think these policies are an example of something that instead needs a longer wait-time.

wooorm referenced this pull request in unifiedjs/rfcs Aug 27, 2019
Closes GH-2.

Related to unifiedjs/governance#28.
Related to unifiedjs/governance#29.
Related to unifiedjs/governance#31.
Related to unifiedjs/governance#32.

Reviewed-by: Christian Murphy <[email protected]>
Reviewed-by: Victor Felder <[email protected]>
Reviewed-by: Titus Wormer <[email protected]>
wooorm added a commit that referenced this pull request 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 wooorm merged commit daeabf4 into master Aug 28, 2019
@wooorm wooorm deleted the organizations branch August 28, 2019 07:54
@wooorm wooorm added ⛵️ status/released and removed help wanted 🙏 This could use your insight or help 🙆 yes/confirmed This is confirmed and ready to be worked on labels Aug 28, 2019
wooorm added a commit that referenced this pull request Aug 28, 2019
Related to unifiedjs/rfcs#2.
Related to GH-29.
Related to GH-31.
Related to GH-32.
wooorm added a commit that referenced this pull request 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 pull request 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 pull request 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
📚 area/docs This affects documentation 👩‍⚕ area/health This affects community 💪 phase/solved Post is done 🦋 type/enhancement This is great to have
Development

Successfully merging this pull request may close these issues.

Security policy
3 participants