There's some obvious humor behind a pull request opened by dependabot that prompts the #CLA assistant to invite the bot to first sign the contributor license agreement.

But there's also a concerning thread. I've seen a lot of this CLA Assistant bullshit proliferate online lately.

In case I haven't already said it enough times, CLAs are awful and they deserve to die - not proliferate.

They impose an unrequired additional legal burden on top of the standard software license.

They often require voluntary unpaid contributors to offer free support on indefinite term for software that they aren't supposed to maintain.

They are that additional bureaucratic burden that nobody in the community really asked for.

They are part of the same problem as the proliferation of custom T&Cs on online services (private parties creating whatever arbitrary set of binding rules they want on top of the standard law, assuming that they're so important that people are ok to waste half of their lives reading their legalese bullshit).

The difference is that, whilst there's no golden standard for a universal T&Cs that applies to all online services, we have one for software licenses.

That's the GPL, MIT, BSD or whatever license that basically every FOSS project slapts in their LICENSE.txt.

So, please, just stick to your LICENSE.txt, let your contributors stick to the basic common-sense rules written your CONTRIBUTING.md, and reserve a spot for CLAs in the graveyard of awful tech ideas that nobody should mourn.

https://github.com/dosyago/BrowserBoxPro/pull/289

Exxon says world set to fail 2°C global warming cap by 2050
https://www.reuters.com/business/energy/exxon-projects-oil-gas-be-54-worlds-energy-needs-2050-2023-08-28/
#ycombinator #NRLPA_OENR #RSBI_SUSTAINABLE_MARKETS #REPI_REFINING #REPI_GAS #RSBI_CLIMATE_CHANGE #RSBI_CLIMATE_SOLUTIONS #MTPIX #CLA #CLC #CMPNY #CO2 #COM #CRU #ENER #ENFF #ENG #ENR #ENV #GASU #GEN #NGS #NRG #OILG #PUBL #REFI #REFI1 #UTIL #AMERS #NAMER #TOPNWS #SUSTAINABLE_BUSINESS #ENERGY #LEGAL #REUTERS_LEGAL #GRNTCH #SCI #TMP #TOPCMB #WEA

#Jisti requires you to sign #CLA to accept contributions.

https://github.com/jitsi/jitsi-meet/blob/master/CONTRIBUTING.md#contributor-license-agreement

> While the Jitsi projects are released under the Apache License 2.0, the copyright holder and principal creator is 8x8. To ensure that we can continue making these projects available under an Open Source license, we need you to sign our Apache-based contributor license agreement as either a corporation or an individual.

I am wondering if the CLAs are OK to stop an incident like one on #hashicorp from happening.

@jwildeboer
CLA MUST state under which license it is made and which kind of licenses it can be moved to (OSI-approved and/or GPL type, if you intend it to remain Open Source).

#OpenSource #licensing #cla #SoftwareDevelopment #LicenseManagement

Même eux, ils n'avaient pas pensé à tout au départ.

Mais ils ont progressé :

https://www.wired.com/2004/05/linux-whose-kernel-is-it/

#DCO #CLA #Licences #FLOSS

🙏🏼🌞

A heads up for other UK #Pentax67 owners; #NewtonEllis in #Liverpool no-longer do the #CLA with these #Cameras.

#BelieveInFilm #Photography #MediumFormat

Another rare win for the hornets!
#hornets #clt #cla #Charlotte
https://www.si.com/nba/hornets/news/charlotte-defeats-houston

Super sad that the rights ratchet clicked for yet another VC-backed #FOSS project, GitPod.

Can one VC-backed company try #AGPLv3 without a #CLA that lets them ignore the #copyleft license terms, and demonstrate what compliance looks like for their own managed service? Just. One.

I *am* glad that it's all going to be AGPLv3, and there's not a proprietary license.

#FreeSoftware #OpenSource
https://www.gitpod.io/blog/introducing-gitpod-dedicated

Any devs here that have worked with cla-assistant? #javacript #cla #claAssistant #developer

Before I had children and witness #acquisition every day, I thought the theory of #Universal #Bilingualism by #Roeper was unparsimonious. Now, having seen #CLA in action, it's clear there are stages where 2 possible analyses and/or structures compete. We've been varying "did + infinitive" and "did + past participle" for a few months. Maybe it's because of less data due to German/English bilingualism or some strange CLI effect (because Germany doesn't do that), but it's not the first such rodeo!

Before I had children and witness #acquisition every day, I thought the theory of #Universal #Bilingualism by #Roeper was unparsimonious. Now, having seen #CLA in action, it's clear there are stages where 2 possible analyses and/or structures compete. We've been varying "did + infinitive" and "did + past participle" for a few months. Maybe it's because of less data due to German/English bilingualism or some strange CLI effect (because Germany doesn't do that), but it's not the first such rodeo!

I’m a #privacy law nerd.

Today I had a zoom meeting to discuss the latest proposed regulations for the California Privacy Protection Act (#CCPA / #CPRA ) with the California Lawyers Association (#CLA ) Privacy Section.

One of the best parts of being part of the #CLAPrivacy is jumping on calls with people far more nerdy and conversant than me about my area of nerdy conversation. 😀

Mostly, developers trust contributors not to sue them for #copyright infringement. In order to prevent issues, you should apply a so-called Contributor #Licence Agreement or #CLA.

I just created an ethical one: https://codeberg.org/ForGoodEyesOnly/Ethical-CLA

RT @Silona@twitter.com

#IEEE #Standard #OpenSource Committee is also looking for comments on the new #CLA s both individual and Entity based! https://opensource.ieee.org/oscom/meetings/-/issues/8

🐦🔗: https://twitter.com/Silona/status/1517204178581524482

@SirFahrenheit@noagendasocial.com

Oh, and I forgot to mention among all of this there's a CLA and plans to roll Audacity code into proprietary software products.

Anyway, you can read more about the whole bruhaha over at:
https://hackaday.com/2021/07/13/muse-group-continues-tone-deaf-handling-of-audacity/

#Audacity #MuseGroup #GPL #Tenacity #CLA

@minoru @doctormo

Actually, I found another link that goes into their recommendations and isn't behind an account wall. There are a bunch of good guidelines in there relating to the code, but they seem to ignore many of the more important social protections. For example, there's no discussion of #CLA's or #governance at all.

A decent start though, although I'd still like to see the possibility to use it without an account, especially primarily recommending one from #Github.

I've just signed my first ever #CLA 🤯 . However it is the #FSF CLA which is the least objectionable of all the CLA's I've seen. Once the paper work is filled I'll be able to contribute to #emacs although in this case the contribution is lined up for counsel/ivy/swiper.