-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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: reconsider proposal review process #67968
Comments
Similar Issues
(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.) |
Patience is a virtue. An issue like #36532 for example is much older than your issue (2020) and is only being considered now. Not all issues are equal. It seems the Go dev team has more urgent issues to deal with than yours. |
@bjorndm's response may be a bit unintentionally harshly worded, but it's not wrong. The offered load on proposal review is far greater than we can serve, so we some things take a while. The oauth2 issue is waiting on me to dig into it and have time to really think about the path forward, and I have had other work-related responsibilities instead. My apologies that it is taking so long. |
Sorry if I came off harsh, but the Go team is working hard and we should respect that. For this issue probably the fastest way forward is to use an open source third party library or to make a temporary fork of the oauth2 library and fix it yourself. |
Proposal Details
The proposal review meeting (#33502) regularly comments or updates open proposals. Especially one proposal- #61417 has been stuck as "discussion ongoing" for months now. It remains unclear what is there to be discussed since the proposal has no open comments. It seems as if it is not reviewed in those meetings at all.
I'm kindly asking the proposal review process to actually review the open proposals instead of moving them as undead "actives" from meeting to meeting.
The text was updated successfully, but these errors were encountered: