Anybody knows what's going on with #Google and #FOSS lately?
https://www.zdnet.com/google-amp/article/open-source-google-wants-new-rules-for-developers-working-on-critical-projects/
@unfa seems like the usual google thinking/acting like they own the place.
@falktx @unfa Reading the blog post, I don't get that impression at all. These all seem like reasonable ideas to address problems that everybody shares and I'm glad Google is putting resources into addressing them. The blog post ends by explicitly acknowledging that they don't own the place. To me the only part of that proposal that seems contentious is maintainers of widely used software to not be anonymous.
@be @falktx @unfa I dont think that's the point. If some software is mission-critical to Google, and they need more guarantees than relying on volunteers doing work for Google, they should hire someone to ensure everything runs smoothly. And the entire community would benefit. Plus, noone has ever imposed such rules on proprietary software.
@LuKaRo @be @unfa every time I have seen google employees submit patches to stuff I maintain, it always comes with the caveat that the google name needs to be in the authors list (even though it is a company, not the real author)
see https://github.com/jackaudio/jack2/pull/348
you both are making good points, I am just very cautious when it comes to google stuff.
google has a terrible history when it comes to maintaining stuff https://killedbygoogle.com/
@unfa that is understandable.
FYI https://opensource.google.com/docs/patching/#common-rules has details on the whole subject.
A lot of FLOSS developers dislike google, and it is not just because their are a Advertising/Data-Collection company that happens to make products to spread their business.
@falktx Well, ok - sorry, I just wanted to express my shock on the Google's policy.