Conversation
There was a problem hiding this comment.
presumably these would need to be filled in first?
There was a problem hiding this comment.
we should agree to the policy and then ask for volunteers. we can accept it with stubs and then put out a call for those volunteers.
|
so many words but 👍 |
|
@indutny we're actually already linking to this in the new README :) |
|
LGTM, we need to fill in emails. |
|
waiting on a better CoC without the need for an institution. |
|
Personally, I think something shorter for Code of Conduct would do the job, like https://www.debian.org/code_of_conduct. The proposed code of conduct includes things that are not part of the conduct but contribution-considerations like line 23-25. |
|
@mikeal I misspoke in our meeting today. The Rust-style CoC is actually already in this fork, so I'd recommend just omitting 745ba90, and instead, putting it on the agenda for a future TC decision once we're capable of putting the legals in place to support it. Besides missing the email addresses for reporting abuse, we're also going to need a policy for receiving reports, grievance procedures, etc. All of that requires a company or foundation or whatever that is going to back it up. |
|
This is ready to merge, someone should merge it :) |
There was a problem hiding this comment.
one "Node" and one "Node.js" reference in this paragraph needs to be fixed
* Update readme.
A push landing after the GraphQL read but before the REST one paired the new head SHA with the old head's checks and mergeability, and only behindBy was cleared. The view could show the old head's green checks against a commit whose CI hadn't started, with the merge guard sending the new SHA, until the next full refresh, up to two minutes later when blurred. The refresh now notices the REST head differs from GraphQL's headRefOid and reads the GraphQL half once more at the new head, falling back to the old behaviour if that read fails or the head moves again. It compares headRefOid rather than the last commit's oid, because commits(last:1) can come back empty on old PRs (nodejs/node#22) and would otherwise re-read every time. Request pattern: one extra GraphQL query (about one point), only on the refresh that raced a push. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MzmChCAxJPRPJoxspSUKnM
5 participants
This is the current governance and contribution policy from @isaacs and @othiym23 that is being presented to the Advisory Board for consideration in nodejs.