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
proposal: Go 2 review meeting minutes #33892
Comments
2019-08-27 / @bradfitz, @griesemer, @ianlancetaylor
|
2019-09-03 / @bradfitz, @griesemer, @ianlancetaylor
|
2019-09-10 / @bradfitz, @griesemer, @iant
|
20190-09-17 / @bradfitz, @griesemer, @iant
|
2019-09-24 / @bradfitz, @griesemer
|
2019-10-01 / @bradfitz, @griesemer, @iant
|
2019-10-08 / @bradfitz, @griesemer, @iant
|
2019-10-15 / @bradfitz, @griesemer, @iant
|
2019-10-22 / @bradfitz, @griesemer
|
2019-10-29 / @bradfitz, @griesemer, @iant
|
2019-11-05 / @bradfitz, @griesemer, @iant
|
2019-11-12 / @bradfitz, @griesemer
Note: This was an abbreviated mtg due to external scheduling conflicts. |
2019-11-19 / @bradfitz, @griesemer, @iant
|
2019-11-26 / @bradfitz, @ianlancetaylor
|
2019-12-03 / @bradfitz, @griesemer, @iant
|
2019-12-10 / @bradfitz, @griesemer, @iant
|
2019-12-17 / @griesemer
Note: Due to other reviewers being ooo I only processed two proposals that were scheduled for closing. |
2020-01-07 / @bradfitz, @griesemer, @iant
|
2020-01-14 / @bradfitz, @griesemer, @iant
We also discussed how we can make the Go 2 proposal review process more scalable. Currently it is fairly simple to create a new Go 2 proposal (like the proposal process intended), but then it becomes a significant burden for the proposal committee to ask and answer many of the questions that should have been answered by the proposal. We are planning to introduce a template of questions (CL 214820) with the intent to dismiss new proposals quickly if they don’t have reasonable answers for most of the questions. |
2020-01-21 / @bradfitz, @griesemer, @iant
|
2020-02-04 / @griesemer, @iant
|
2020-02-18 / @bradfitz, @griesemer, @iant
|
2020-02-25 / @bradfitz, @griesemer, @iant
|
I just wanted to let the proposal review group know that these meeting minutes are helpful, and that I appreciate you writing them up. If others feel the same way, please give a thumbs up to this comment, so that the review group knows. :) |
Unfortunately, @josharian, it will be a very quiet emoji party because the conversation is locked 🔒 |
2021-02-16 / @bradfitz, @griesemer, @iant
|
2021-02-23 / @bradfitz, @griesemer, @iant
Going forward we are going to reduce the frequency of these proposal review meetings (for Go2-labeled proposals) to once a month (Tuesday of the first week of each month). We are deferring unrelated language changes until generics have landed; also, currently the number of incoming proposals is relatively low. |
2021-04-06 / @bradfitz, @griesemer, @iant
|
2021-05-04 / @bradfitz, @griesemer, @iant
|
2021-06-01 / @bradfitz, @griesemer, @iant
|
2021-08-03 / @bradfitz, @griesemer, @iant
|
2021-11-03 / @bradfitz, @griesemer, @iant
|
2022-1-5 / @bradfitz, @griesemer, @iant
|
2022-2-2 / @bradfitz, @griesemer, @iant
|
2022-3-2 / @bradfitz, @griesemer, @iant
|
May 4, 2022 / @bradfitz, @griesemer, @iant
|
Jun 8, 2022 / @bradfitz, @griesemer, @iant
|
Jan 4, 2023 / @bradfitz, @griesemer, @iant
|
Feb 1, 2023 / @griesemer, @iant
|
Mar 1, 2023 / @griesemer, @iant
|
Apr 12, 2023 / @griesemer, @iant
|
May 10, 2023 / @griesemer, @iant
|
Jun 7, 2023 / @bradfitz, @griesemer, @iant
|
Jul 19, 2023 / @griesemer, @iant
|
Aug 2, 2023 / @bradfitz, @griesemer, @iant
|
Sep 6, 2023 / @bradfitz, @griesemer, @iant
|
Oct 4, 2023 / @bradfitz, @griesemer, @iant
|
Nov 1, 2023 / @adonovan, @bradfitz, @findleyr, @griesemer
|
The Go 2 proposal review group meets monthly (every first Wednesday of a month) to review pending Go 2 proposal issues and move them along in the proposal process.
Review consists primarily of checking that discussion is ongoing, commenting on issues to move discussion along, summarizing long discussions, CC’ing experts, and accepting or closing proposals when the discussion on the GitHub issue has reached a clear consensus about the outcome.
Review also includes closing proposals that are untenable (for example, because the changes are sufficiently backwards-incompatible even after allowing for significant changes to the language as part of the Go 2 effort, or violate key design goals of the language or packages).
This meta-issue records minutes of the Go 2 proposal review meetings as issue comments, so that they can be cross-linked easily with the relevant issues. This meta-issue is for minutes only; comments that are not meeting minutes will be deleted.
(See also #33502 which records the minutes of non-Go 2 proposals review meetings).
The text was updated successfully, but these errors were encountered: