WHAT IS GOOGLE OPEN SOURCE?
Open-source software is one type of computer software in which the source code is released under a license. In this license, the copyright holder grants users the exclusive rights to study, change, and sell the software to anyone for various purposes. Open source is more than just about the code. It includes planning that happens before writing the system, the process of how that code is used and creating a community-friendly environment.
Google has helped in bringing better technology to the world by launching its open-source software. The Google company believes that open source is the technology for everyone, whether experienced or inexperienced. Google open source is open and freely available for all people. It enables and encourages the development of technology. Google open source helps us in solving real-world problems.
CREATING GOOGLE OPEN SOURCE
Google has a staunch belief in its open source and wants to help you contribute to the community. There are many legal implications whenever a Google user releases a code. So the google company has a specific process that you must follow that helps google comply with its legal obligations. Typically if you are talking about anything illegal this will be excluded along with grey area material such as fuck sites, sex apps, pornography, and other adult content.
IMPORTANCE OF GOOGLE OPEN SOURCE
Many reasons highlight the importance of why Google has launched the google open source, for example; building better software or establishing a standard regime.
COMPONENTS OF GOOGLE OPEN SOURCE DOCUMENTS
Google open source has three major components:
Creating: creating includes how Google asks users to release code which they have written. This code is either in the form of a new project or a patch to an existing old plan. This process is used for small scale and large scale projects. Creating includes:
Releasing code is open-source: This is the process for issuing new open source projects to the world. The release process applies to different projects.
Preparing for release: this process further includes steps like:
- Naming the project, licensing the project and Packaging the project
- Including a readme file, a license file, a contributing file and source code headers
- Third-party components
- Porting the build
- Scrubbing the comments
- Including a code of conduct
- Reviewing the project
- Choose the appropriate tools
- Staging the code for review
Getting approval: After preparing the project and staging the code on a Cloud Source Repository, a launch entry must be created. Once the launch is created, the following steps must be taken:
- Ensuring all reviewers have read access to the code.
- Address any comments posted by the launch reviewers.
- Waiting for approval.
Choosing a hosting option
Releasing and publicizing: this includes Cryptography compliance, Required disclaimer, Discussion forum, Publishing apps in Google Play and web store, Creating your repository, publishing your code, Importing into Google, and letting the world know.
- To accept contributions from google as well as non-google users.
Using: using explains how to bring an open-source code into the company and use it for building great products. Google catalogs many packages for maintaining license compliance. Using includes:
- Third-party code: the third party is the repository where all non-Google code, binaries, and data is checked. Using third-party code saves time, and it is very consistent. To use any third-party code, google imports it and places its source in the third party repository. The third-party deposit is a personal repository that contains all third party open source codes.
- Licenses: Google needs to comply with open-source licenses for all software that is externally distributed. Most of the software is distributed under a pre-vetted license.
- Adding code to the third party: Adding a new code to the third party takes a small amount of time. After adding code to the third party, it can be updated generously without having to repeat this process. These are the steps you should follow:
- Get the code
- Put the code in the third-party repository.
- Get the code working with Google
- Document the code and its context
- Get a review
- Responsibilities of third party owners and third party users: the third-party is a shared codebase. It is expected that google users work together in maintaining the health of the repository. As such, there are rules that users are expected to follow.
- The one version rule: This rule applies to two different versions of a single package, or separate copies having different package names under third-party.
- Reviewing: Reviewing extras to Google’s massive cache of third-party code helps Google ensure that it’s using the third party code properly.
- Growing: growing describes some of the program google runs inside and outside the company for supporting open source communities. Growing includes:
- Student Programs: Supporting the next generation of open-source developers
- Peer Bonus Program: Rewarding source developers who contribute to software that is used by Google.
- Events and Funding.
- Blog and Social Media: telling the world about the Google open – source.
- Ambassadors: Working with Google users around the world.