Russ,
I'm happy you updated the public docs on the proposal review process. It is
much more clear now. Thanks.
Thanks for publicly listing the people on the review process. It helps
people have insights. And, thanks for listing Peter who is not on that
GitHub team. He's a Googler I didn't real
Thanks for the details, Russ.
On Tuesday, May 28, 2019 at 11:53:09 AM UTC-4, Russ Cox wrote:
>
> On Mon, May 27, 2019 at 7:08 PM Matt Farina > wrote:
>
>> 1) when a company runs a project without much publicly documented process
>> but does as they choose, isn't
> Ian mentioned that "Google" as a company doesn't actually choose to do a
> lot. The Go team is largely autonomous in their decision making and isn't
> being influenced by executives.
> So, to put it another way: If the only role the company plays is to
> provide paychecks to some Go develope
from multiple companies with differing concerns on it.
But, that's just wondering.
I use Go. Gonna start something new in go soon, too.
--
Matt Farina
mattfarina.com
Go in Practice <http://goinpracticebook.com/> - A book of Recipes for the
Go programming language.
Code Engineered <htt
This whole conversation illustrates the difference between open source and open
governance. Go is open source but the governance is controlled by Google. This
compares to something like Kubernetes that is both open source and open
governance.
Should Go be open governance? It sounds like this is
A couple months ago we had a package management survey. Since the survey
closed the data has been fed into the package management committee.
Now we are sharing the data, that was not asked to be kept private. This
can be read at
https://docs.google.com/document/d/15j_Q6RRX_LH6tu4DNDm-vAcWAUablq
