Contributors can manage their agreements and sign new agreements on cla.developers.google.com/. Be sure to direct users to your CONTRIBUTING file. In addition, individual contributors may be discouraged from accepting the terms of a CTC if they do not understand the legality or consequences of signing the agreement (online or offline) or other consent to its terms. In the absence of legal representation, individual contributors may perceive the CTC`s conditions as a constraint or unfairness. Business contributors may also be reluctant to accept a CTC or allow their employees to accept a CTC before obtaining permission from their legal counsel. However, other contributors prefer to remain anonymous, which may not be possible if a project requires a CTC. As a result, potential contributors are not able to make useful software contributions to the open source project out of fear, misunderstanding or inconvenience related to the signing of the CLA. TIP: If you`re not sure what email address you`re using for a commit, you can add .patch to many GitHub URLs to see the uns formatted patch containing the committer`s email address. For example, to view the in-mail address used in the grpc/grpc-12 pull request, just add .patch to the URL: github.com/grpc/grpc/pull/12.patch. The same goes for individual commit URLs: github.com/grpc/grpc/commit/3acf05a.patch. One way to manage dues rights is through a City Defence Law Agreement (CLA), sometimes referred to as a “contribution agreement.” However, in the open source community, there are some differences of opinion as to whether a CLA should be asked of individual contributors. A CTC can be used to define legal terms, such as the rights and obligations of the contributor, that apply to contributions (usually software) to the open source project.
The CTC may require, for example. B, that the contributor issue a copyright license for the contribution to the open source project, to its managers and/or to downstream recipients. Because CLAs are not standardized, contributions to different open source projects may be subject to different or none of the CLAs. While small informal open source projects may not require CLAs, for example. B for leisure groups that coordinate via a GitHub repository, large projects, often supported by one or more companies, require formal agreements from their contributors. Several well-known open source projects, such as The Apache Software Foundation, Django Software Foundation, Eclipse Foundation, to name a few, require CLAs.