Forge Your Future with Open Source
by VM (Vicky) Brasseur · 266pp · 79,297 words
Preparation 3. Prepare to ContributeWays to Contribute Common Project and Community Roles Files You Should Know About Before You Start Issue Tracking Common Communication Routes Contributor License Agreement/Developer Certificate of Origin You’re Ready to Find a Project 4. Find a ProjectSet Your Goals Collect Your Requirements Collect Candidate Projects Select a
…
creative work you contribute to a project, unless you agree to assign your copyright elsewhere (as can happen in a work for hire or a Contributor License Agreement situation, both covered later in the book), you retain copyright over your contribution and—if the project is released under an OSI-Approved License—your
…
you should carefully read and review your employment agreements before signing them, regardless. On the other side of the copyright ownership exception coin, we have Contributor License Agreements (CLA). These are discussed further in Chapter 3. Some (but not all) CLAs include the requirement that the contributor assign the copyright of all of
…
’d wish to join. Respect their choices and the process that went into making them. Contributor License Agreement/Developer Certificate of Origin A few free and open source software projects require all contributors to agree to either a Contributor License Agreement or a Developer Certificate of Origin before their contributions can be merged and distributed with
…
might impact your contributions. Some projects—especially but not exclusively, those developed under the aegis of a large corporation—require all contributors to sign a Contributor License Agreement (CLA). A CLA is a document resplendent with intellectual property implications and therefore, a controversial matter for some free and open source software practitioners. The
…
This question of who owns the copyright to your potential contribution is particularly important when the project to which you wish to contribute has a Contributor License Agreement (CLA) or a Developer Certificate of Origin (DCO) that you must sign before your contribution will be accepted. If you recall from Chapter 3, Prepare
…
maintainers to decline it than to explain to the creator the many ways in which the contribution falls short. The contributor has not signed the Contributor License Agreement (or a commit for the Developer Certificate of Origin). Projects that require a signed CLA or DCO will not be able to accept contributions from
…
. See the entry for CI/CD for more information. contribution Documentation, testing, design, programming, event coordination, or any other action that helps a FOSS project. Contributor License Agreement Also known as CLA. This is a legal document intended to certify that the person sharing a contribution has the right to do so, and
Producing Open Source Software: How to Run a Successful Free Software Project
by Karl Fogel · 13 Oct 2005
, Copyrights, Trademarks and Patents Terminology Aspects of Licenses The GPL and License Compatibility Choosing a License The GNU General Public License Contributor Agreements Doing Nothing Contributor License Agreements Proprietary Relicensing Problems with Proprietary Relicensing Trademarks Case study: Mozilla Firefox, the Debian Project, and Iceweasel Case study: The GNOME Logo and the Fish Pedicure
…
to by many people. The first is to ignore the issue of copyright entirely (I don't recommend this). The second is to collect a contributor license agreement (CLA) from each person who works on the project, explicitly granting the project the right to use that person's contributions. This is usually enough
…
project will have no documentation showing that the contributor formally granted the right to use the code, which could make some legal defenses more difficult. Contributor License Agreements CLAs probably offer the best tradeoff between safety and convenience. A CLA is typically an electronic form that a developer fills out and sends in