microcline + contributor_license_agreement   30

TheOpenSourceWay.org contribution policy
Implied agreement: "You accept this as part of the act of making a contribution."
contributor_license_agreement  open_source_way 
5 weeks ago by microcline
Apache: ICLA is required for commit access.
"For the ASF, an iCLA is required once one gets commit access.

Regarding the CCLA, that must be determined my the individual themselves.
There is no one, complete, all-inclusive answer other than "it depends" :)"

Jim Jagielski (recently former Apache VP Legal Affairs), org.apache.legal-discuss 2017-03-23
contributor_license_agreement  apache  licensing 
5 weeks ago by microcline
Apache: ICLA desired, not required, for normal contributions.
" I'm not sure where this meme comes from, but an ICLA is only desired,
not required, for normal contributions."

"a CLA is only required for committers."

Jukka Zitting, 2012-03-15, org.apache.legal-discuss list.
apache  contributor_license_agreement 
5 weeks ago by microcline
Apache: lots of downsides, no upsides to requiring CLAs of Contributors
wrt "a CLA is required before a potential contributor is able
to make a contribution":

"
I see lots of downsides to that policy and no upsides. The issues that
concern me:
- Unnecessary barriers to entry for new contributors
- Legally unnecessary
- Creates additional work for the secretary (not much now but if every
TLP and podling did this it might)
- Re-enforces the meme an iCLA is required to contribute at Apache

I'm also don't believe that an iCLA is even desired for all
contributions. The ALv2 provides all the legal cover we need and desire.
"
- Mark Thomas, on org.apache.legal-discuss list, 2012-10-16.
apache  contributor_license_agreement 
5 weeks ago by microcline
Apache: Committers sign ICLAs, contributors typically don't
"Committers sign ICLAs, contributors don't (typically - maybe a project has
a reason for requiring contributors to sign ICLAs but I don't recall it
being done)."

-Henri Yandell , 2016-01-07, org.apache.legal-discuss list
apache  contributor_license_agreement 
5 weeks ago by microcline
Contributor agreements considered harmful
I'm aware that I've failed to provide a TL;DR version of this article. I tried twice to write one and ultimately decided that I can't. Simply put, these issues are complex, and I had to draw on a decade of software freedom licensing, policy, and organizational knowledge to fully articulate what's wrong with the Project Harmony agreements. I realize that sounds like a It was hard to write — it should be hard to read justification, but I just don't know how to summarize these Gordian problems in a pithy way. I nevertheless hope developers will take the time to read this before they sign a Project Harmony agreement, or — indeed — any CLA or ©AA.
contributor_license_agreement 
9 weeks ago by microcline
Developer Certificate of Origin
Think of it as a minimal Contributor License Agreement, leveraging inbound == outbound.
contributor_license_agreement  licensing  open_source 
june 2016 by microcline
Producing OSS: Contributor Agreements
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.
contributor_license_agreement 
june 2016 by microcline
Oracle Contributor Agreement: Overview and FAQ
The Oracle Contributor Agreement (OCA) must be signed by
any person or entity that wishes to contribute code or other
materials to an open source project that is administered by
Oracle.
contributor_license_agreement 
june 2016 by microcline
Contributor Agreements kill contributions
A low barrier to entry is what has made the largest, most successful free software projects what they are today. If you’re wanting your project to be an open source project and not an open source product – then you too must set a low barrier to entry.
Contributor Agreements significantly raise the barrier to entry.
contributor_license_agreement 
june 2016 by microcline
Should open source communities avoid contributor agreements
It may well be advisable to have a participant agreement

Contributor agreements **that aggregate the copyrights** of open source code in favour of a single corporate sponsor are a sure sign of a community where one member has more rights than the rest.
contributor_license_agreement  licensing 
june 2016 by microcline
Why Chef chose Apache
Note discussion of CLAs, and recognition that faxing things is no fun.
chef  opscode  contributor_license_agreement 
june 2016 by microcline
In defense of contributor license agreements
Requiring a contributor license agreement is a sign that you intend to sustain your project in the long run with responsible practices regarding intellectual property management. Responsible open source developers aren’t afraid of signing contributor license agreements: they simply understand the legal implications of sharing source code with the rest of the world.
contributor_license_agreement 
june 2016 by microcline
ContributorAgreements.org
The goal of contributoragreements.org is to develop the legal and technical infrastructure that will enable open source collaborative projects to receive, use, and share in-kind contributions from participants while eliminating or minimizing the legal risk therefrom to the projects.
contributor_license_agreement 
june 2016 by microcline
Contributor Agreements say your contribution is unwelcome
contributor agreements are not just a source of inequality in a project but also a recognised flag that participation is neither expected or required.

a contributor agreement may well lead to you getting no co-developers.
contributor_license_agreement 
june 2016 by microcline
Node lifts CLA requirement
"In an effort to make it easier for users to contribute to Node.js the project has decided to lift the requirement of signing the CLA before contributions are eligible for integration. Having to sign the CLA could at times be a stumbling block for a contribution. It could involve a long conversation with your legal department to ultimately contribute typo corrections."
contributor_license_agreement 
june 2016 by microcline
Node.js removes its CLA
I'd like to congratulate Joyent for making the right decision today to remove one of the major barriers to entry for contribution to the Node.js project: its CLA.
contributor_license_agreement 
june 2016 by microcline
Why Your Project Doesn't Need a Contributor Licensing Agreement
a summary on the basics of why CLA's aren't necessary, and on Conservancy's typical recommendations to its projects regarding the issue.
contributor_license_agreement 
june 2016 by microcline
Why Your Project Doesn't Need a Contributor Licensing Agreement
In practice, most CLAs in use today are deleterious overkill ...

CLAs simply shift legal blame for any patent infringement, copyright infringement, or other bad acts from the project (or its legal entity) back onto its contributors.

disastrously, CLAs require the first interaction between a FLOSS project and a new contributor to involve a complex legal negotiation and a formal legal agreement. CLAs twist the empowering, community-oriented, enjoyable experience of FLOSS contribution into an annoying exercise in pointless bureaucracy, which (if handled properly) requires a business-like, grating haggle between necessarily adverse parties.

The most ardent supporters of CLAs have yet to experience first-hand the arduous daily work required to manage a queue of incoming FLOSS contributions. Those of us who have done the latter easily see that avoiding additional barriers to entry is paramount. While a beautifully crafted CLA — jam-packed with legalese that artfully shifts all the blame off to the contributors — may make some corporate attorneys smile, but I've never seen such bring anything but a frown and a sigh from FLOSS developers.
contributor_license_agreement  licensing  open_source 
june 2016 by microcline
Can You Contribute Code To An Open Source Project?
Most employees are not in fact the copyright holders for copyright material that is generated as part of their work. This will vary from organisation to organisation, and possibly between job roles within an organisation. Please note: having written this code at home will not, by itself, indicate that you hold the copyright on it

How do you get the consent of your employer or institution to contribute their copyright material to an open source project?

Regrettably the steps involved may be numerous, and are almost inevitably peculiar to your organisation. Nor do they guarantee that consent will be forthcoming.
contributor_license_agreement  licensing  open_source 
june 2016 by microcline
OSS Watch on Contributor License Agreements
A Contributor Licence Agreement (CLA) is strongly recommended when accepting third party contributions...
contributor_license_agreement 
june 2016 by microcline

Copy this bookmark:



description:


tags: