Skip to content

doc: rewrite consensus seeking in guide #23349

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.

Sign up for GitHub

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

Closed
Trott wants to merge 3 commits into from
Closed

doc: rewrite consensus seeking in guide #23349

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
664a248
doc: rewrite consensus seeking in guide
Trott Oct 9, 2018
cf16b2c
fixup! doc: rewrite consensus seeking in guide
Trott Oct 11, 2018
4f4aea3
fixup! doc: rewrite consensus seeking in guide
Trott Oct 11, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
fixup! doc: rewrite consensus seeking in guide
  • Loading branch information
@Trott
Trott committed Oct 11, 2018
commit 4f4aea3c62237753981e7570d6a7e79bacd4fae3
11 changes: 5 additions & 6 deletions COLLABORATOR_GUIDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -154,12 +154,11 @@ Another Collaborator may ask an objecting Collaborator to explain their
objection. If the objector is unresponsive, another Collaborator may dismiss the
objection.

Note that [breaking changes](#breaking-changes) must receive
[TSC reviews](#involving-the-tsc). This does not mean that a Collaborator must
put the pull request on the TSC meeting agenda. If two TSC members approve the
pull request and no Collaborators object to the pull request, it may land. If
there are objections, a Collaborator may put the pull request on the TSC meeting
agenda.
[Breaking changes](#breaking-changes) must receive
[TSC review](#involving-the-tsc). If two TSC members approve the pull request
and no Collaborators object, then it may land. If there are objections, a
Collaborator may apply the `tsc-agenda` label. That will put the pull request on
the TSC meeting agenda.

#### Helpful resources

Expand Down