I have just read https://github.com/golang/go/issues/33892#issuecomment-659618902 and since it was posted on a closed issue I wanted to comment a bit more.
I subscribed to this issue and read the updates for both the Go2 proposals as well as the Go1 proposals and I enjoy reading them. I understand the reasoning behind wanting to do less here but I do belive there are some downsides as well. One reason I read these every week is that it gives people outside of the Go team an insight into the thought process and the reasoning of decisions. Also feedback on these changes hopefully should help to refine future requests. I am really afraid that just "ignoring" requests continues or goes back to the idea that that Go is not a community language and that the only ideas and changes can come from Google employees (or past employees in the case of bradfitz). The transparency here was awesome and I am very sad to see it go away. I hope there is some other middle ground or at least some details around what will go into hand picking? For the non-picked proposals will they just remain open for some undetermined amount of time? Will they just be closed? Is feedback on these still expected? Maybe the real solution is just to meet up less? Maybe once a month or even once a quarter vs every week? Thank you, Brandon -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/6e012c05-24ce-49cf-a8f2-b8b6f3f543ffo%40googlegroups.com.
