e. hashman Profile picture
12 Apr, 7 tweets, 4 min read
Thread 🧵 of 501(c)(3) public charities you can support instead of the @fsf, if you care about its mission:
The Software Freedom Conservancy (@conservancy) provides a fiscal home for community-governed projects like git, sponsors @outreachy, and is the only organization doing GPL enforcement: sfconservancy.org/supporter/
Software in the Public Interest (@spi_inc) provides a fiscal home for a number of FOSS projects like @debian and @FFmpeg. spi-inc.org/donations/
The Open Source Initiative (@OpenSourceOrg) [disclosure: I recently served on its board] maintains the Open Source Definition, a list of approved open source licenses, educates about open source, and much more: opensource.org/membership
The Electronic Frontier Foundation (@EFF) advocates for privacy, security, and digital liberties: supporters.eff.org/donate/join-ef…
The Freedom of the Press Foundation (@FreedomofPress) protects whistleblowers and journalists with free software like @SecureDrop and education and advocacy: freedom.press/donate/
There are many more, but I have focused this thread on umbrella organizations that overlap with certain functions of the FSF: digital rights, anti-surveillance, education, fiscal sponsorship, approved software licenses.

Please reply with awesome orgs I've missed!

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with e. hashman

e. hashman Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @ehashdn

22 Jan
I am real mad about the Elastic relicense so I'm going to vent a bit.
Say that I contributed some code to Elastic, under the original open source license. That license defines the terms of our engagement. Me: "hey I improved your code, can you include this fix so I and everyone can use it?" Elastic: "sure!"
They require a CLA, which assigns ownership of my fix to the project steward. The idealistic reason to do this is to protect the long-term health of the project: if copyright law gets totally rewritten, we can update the license to reflect our original intent!
Read 12 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!