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

Cleanup #106

Closed
wants to merge 2 commits into from
Closed

Cleanup #106

wants to merge 2 commits into from

Conversation

chaals
Copy link
Contributor

@chaals chaals commented Sep 27, 2017

Ensure AC review does start (at PR)
Update changelog

Ensure AC review *does* start (at PR)
Update changelog
@LJWatson
Copy link
Contributor

I still do not understand why we want to open the ballot at PR? If the intent of the original change was to enable early feedback by opening the ballot at CR and running it through PR, reverting to opening the ballot at PR seems like a step back.

If we open the ballot at CR and run it for a limited period of time (perhaps 4 weeks), the spec should be stable enough for the AC to make a reasoned decision about its readiness to progress. If there are concerns, then it enables the early feedback the original change sought to enable.

Feedback, especially concern about readiness to progress, without the formality of a ballot, seems unlikely to have much impact.

@dwsinger
Copy link
Contributor

dwsinger commented Sep 27, 2017

We have to have a formal AC ballot at some point as to whether the spec. should be published as a Rec. We can't do that at CR because there are questions of implementability, features at risk, and so on. So, we notify the AC at CR (so they can raise any general objections) and then do the formal ballot at PR. Yes, it should be a question of the AC confirming that i's are dotted, t's crossed, and all is hunky-dory, but we have to ask at some point.

I don't think we want two formal ballots (at CR and again at PR), and we do need the community's formal endorsement "yes, publish that" and "that" needs to be well-defined at the time we ask the question.

@LJWatson
Copy link
Contributor

Thanks @dwsinger. Understood. As you were :)

@chaals
Copy link
Contributor Author

chaals commented Sep 27, 2017

I'm assuming @wseltzer will merge this.

@chaals
Copy link
Contributor Author

chaals commented Sep 27, 2017

Oh. This has been overtaken by a patch from Wendy.

@chaals chaals closed this Sep 27, 2017
@frivoal frivoal deleted the chaals-patch-wseltzer5 branch November 16, 2018 05:45
@frivoal frivoal added Closed: Rejected DoC This has been referenced from a Disposition of Comments (or predates the use of DoCs) labels Dec 9, 2018
@frivoal frivoal added this to the Process 2018 milestone Feb 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Rejected DoC This has been referenced from a Disposition of Comments (or predates the use of DoCs)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants