Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Google Wants Third Parties to Review Open Source Developers

Google is proposing changes for “critical projects” in terms of the norms of what developers do. Among those are things that make sense, such as forcing two factor authentication. Some of them not so much, like forcing a sort of registry for any contributors or not allowing anonymous contributors. But perhaps more worrisome is that that they want TWO independent, third parties to be required to review all changes. (They also want these third parties to dictate what can, and can’t be changed. And this is absolutely ridiculous.)

It is totally antithetical to the spirit of open source, along with everything it stands for. It’s taking away the freedoms that made open source so powerful, forcing and allowing third party companies to control the destiny of large scale projects. 

They claim that this is under the guise of security, and that it reduces vulnerabilities and increases truthworthiness. But let’s think about that, because Google itself has benefitted immensely from open source. One of the largest companies in the world has benefited from the huge community of projects that are available for free, thanks to the developers who had the freedom to create wonderful things. They chose to use those projects and have contributed to their popularity.

And it’s not unwarranted. There is a reason open source dominated the mobile market, the server market, and the IOT market. One of the most prominent reasons is security and stability. This is the reason we don’t use closed source options such as Windows (as often, at least). These critical open source projects are already being used by Google (and many others) because they are much more secure and trustworthy. So when Google wants to come in and force developers, many of whom are working for free, to jump through hoops and red tape that are antithetical to open source, it’s not security they are concerned about. The outcome isn’t security, it’s influence. Google is fully capable of developing their own options or forking projects if THEY want to control the destiny of those projects.

The whole thing is just against the entire spirit of open source. If you don’t trust the package, don’t use it. If you think a critical package isn’t maintained in the way you want, then fork it. It’s YOUR responsibility to do that in open source. Not your responsibility to get red tape involved and strong arm them into paying third parties. No. As a multi billion dollar company, it’s YOUR responsibility to contribute. 

Honestly, just not so sure about this one. What are your thoughts?

Google's trying to make it harder for open source work to thrive, to limit the chance for competitors to rise and to increase the value of their own products. This would be a big slap in the face to the free market.

Short answer: bad idea.
I agree. It's bothersome to me because they themselves are standing on the shoulders of giants in the open source world. They benefit immensely from it. And usually they contribute too, but right now, this is very antithetical to the entire philosophy that built open source products to begin with.

Google would like to try all legal and illegal means to prevent open source work.
Here, Google can not yet subjugate their cookies.

Any encroachment on these bunch of greed and power-addicted investors should be stopped
 [Image: autism4all.png]
[x] <= Drive in nail here for new display!

Users browsing this thread: 1 Guest(s)

Makestation Theme/Design Selector

Contact Us | Makestation | Return to Top | Lite (Archive) Mode | RSS Syndication 
Proudly powered by MyBB 1.8, © 2002-2021
Forum design by Makestation Team © 2020 - a modern day time capsule | Makestation Ajax Chat Hosting