On Mon, May 27, 2019 at 7:08 PM Matt Farina <matt.far...@gmail.com> wrote:
> 1) when a company runs a project without much publicly documented process > but does as they choose, isn't that a sign of a company run project? > 2) The go team at Google has had processes that are not public. One > example is the proposal review process. There has long been a group at > Google that decides these. For a long time this wasn't documented publicly > but happened. The public documentation on it came after the decision on go > modules. > This is demonstrably false. We launched the proposal process at Gophercon in 2015 <https://talks.golang.org/2015/how-go-was-made.slide>, well before modules. We did it explicitly to open the process of contributing ideas - as opposed to code - and make it more accessible to new contributors. You can see the full commit history <https://github.com/golang/proposal/commits/master/README.md> of the process description online. I tried to streamline the doc to make it more approachable in 2018, but I did not make semantic changes in that edit. 3) how has no one outside of Google qualified for the core team and why > aren't more companies who are heavy users in on owning it? > It's unclear what you mean by "core team." If you mean the set of people who can approve (+2) and submit code changes, then as Ian said, there are more people outside Google than inside Google at this point. On Mon, May 27, 2019 at 9:17 PM Matt Farina <matt.far...@gmail.com> wrote: > As a concrete example: Cloudflare pretty heavily uses Go. When a >> cloudflare-employee started stepping up to work more and more on the Go >> crypto stack, they got hired by Google to do it fulltime. At least from the >> outside, that seems to what happened with Filippo Valsorda. >> > > That's fantastic. This shows some open source in action. It also > highlights that this isn't open governance. If it did, Filippo joining the > core team would have been a separate event from joining Google. > We did give Filippo the ability to +2 (review, approve, and submit) crypto CLs while he was still at Cloudflare, so in that sense it *was* a separate event. Filippo being at Google now means that working directly on Go can be his full-time job now. My understanding is that he had responsibilities at Cloudflare beyond contributing to the Go project. A better example might be the various engineers who work at companies like Intel, ARM, and Microsoft on Go support for those companies' processors and operating systems. Many of them can now +2 code change as well, and they do so within their area of expertise. Best, Russ -- 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/CAA8EjDR_qT0HCT%3DCiZbOW2NrkyD6gCQ3_5gPTH12MVK71GQyYA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
