On Wed, Oct 18, 2023 at 08:07:32AM +0200, Krzysztof Kozlowski wrote: > On 17/10/2023 23:41, Doug Anderson wrote: > > > > 3. The ChromeOS team is organized much more like the upstream > > community than a big hierarchical corporation. Just as it's not easy > > for you to control the behavior of other maintainers, it is not > > trivial for one person on the team to control what others on the team > > will do. We could make an attempt to institute rules like "all patches > > must go through internal review before being posted", but as per #2 I > > don't think this is a good idea. The ChromeOS team has even less > > control over what our partners may or may not do. In general it is > > always a struggle to get partners to even start working upstream and > > IMO it's a win when I see a partner post a patch. We should certainly > > help partners be successful here, but the right way to do that is by > > offering them support. > > I don't know who is exactly core team, who is partner. I see > "google.com" domain, so Google folks are responsible for not wasting > time of the community. If Google disagrees, please change the domain so > I will understand that and not feel like Google wants to use us all. I think it might help if you think of <company>.corp-partner.google.com addresses as gmail.com addresses. People who are using these addresses are not employees of Google nor contractors for Google; they work for their respective <company>. The main reason person@<company>.corp-partner.google.com addresses are being used for mainline submissions is because it is actually possible to set up "git send-email" with them, as their main domain typically handled by Exchange and mandates Outlook. Thanks. -- Dmitry
