Software Freedom Conservancy

[RSS] Conservancy Blog

Displaying posts tagged conservancy

Conservancy News Round-up

by Deb Nicholson on April 17, 2019

Check out these videos, blog posts from member projects, code releases and upcoming events.

Recent Videos

Our Member Projects Have Been Busy

Some recent code releases:

What's coming up?

Catch up with staff:

Many of our projects have events coming up:

Bonus news! GPLv3 code made the famous black hole picture possible. Congrats to Doctor Katie Bouman and her team!

Tags: conservancy, conferences, Godot, Reproducible Builds, Selenium, Outreachy, events, Clojars, inkscape, Hackfests, Racket

Understanding LF's New “Community Bridge”

by Bradley M. Kuhn and Karen M. Sandler on March 13, 2019

Yesterday, the Linux Foundation (LF) launched a new service, called “Community Bridge” — an ambitious platform that promises a self-service system to handle finances, address security issues, manage CLAs and license compliance, and also bring mentorship to projects. These tasks are difficult work that typically require human intervention, so we understand the allure of automating them; we and our peer organizations have long welcomed newcomers to this field and have together sought collaborative assistance for these issues. Indeed, Community Bridge's offerings bear some similarity to the work of organizations like Apache Software Foundation, the Free Software Foundation (FSF), the GNOME Foundation (GF), Open Source Initiative (OSI), Software in the Public Interest (SPI) and Conservancy. People have already begun to ask us to compare this initiative to our work and the work of our peer organizations. This blog post hopefully answers those questions and anticipated similar questions.

The first huge difference (and the biggest disappointment for the entire FOSS community) is that LF's Community Bridge is a proprietary software system. §4.2 of their Platform Use Agreement requires those who sign up for this platform to agree to a proprietary software license, and LF has remained silent about the proprietary nature of the platform in its explanatory materials. The LF, as an organization dedicated to Open Source, should release the source for Community Bridge. At Conservancy, we've worked since 2012 on a Non-Profit Accounting Software system, including creating a tagging system for transparently documenting ledger transactions, and various support software around that. We and SPI both now use these methods daily. We also funded the creation of a system to manage mentorship programs, which now runs the Outreachy mentorship program. We believe fundamentally that the infrastructure we provide for FOSS fiscal sponsorship (including accounting, mentorship and license compliance) must itself be FOSS, and developed in public as a FOSS project. LF's own research already shows that transparency is impossible for systems that are not FOSS. More importantly, LF's new software could directly benefit so many organizations in our community, including not only Conservancy but also the many others (listed above) who do some form of fiscal sponsorship. LF shouldn't behave like a proprietary software company like Patreon or Kickstarter, but instead support FOSS development. Generally speaking, all Conservancy's peer organizations (listed above) have been fully dedicated to the idea that any infrastructure developed for fiscal sponsorship should itself be FOSS. LF has deviated here from this community norm by unnecessarily requiring FOSS developers to use proprietary software to receive these services, and also failing to collaborate over a FOSS codebase with the existing community of organizations. LF Executive Director Jim Zemlin has said that he “wants more participation in open source … to advance its sustainability and … wants organizations to share their code for the benefit of their fellow [hu]mankind”; we ask him to apply these principles to his own organization now.

The second difference is that LF is not a charity, but a trade association — designed to serve the common business interest of its paid members, who control its Board of Directors. This means that donations made to projects through their system will not be tax-deductible in the USA, and that the money can be used in ways that do not necessarily benefit the public good. For some projects, this may well be an advantage: not all FOSS projects operate in the public good. We believe charitable commitment remains a huge benefit of joining a fiscal sponsor like Conservancy, FSF, GF, or SPI. While charitable affiliation means there are more constraints on how projects can spend their funds, as the projects must show that their spending serves the public benefit, we believe that such constraints are most valuable. Legal requirements that assure behavior of the organization always benefits the general public are a good thing. However, some projects may indeed prefer to serve the common business interest of LF's member companies rather than the public good, but projects should note such benefit to the common business interest is mandatory on this platform — it's explicitly unauthorized to use LF's platform to engage in activities in conflict with LF’s trade association status). Furthermore, (per the FAQ) only one maintainer can administer a project's account, so the platform currently only supports the “BDFL” FOSS governance model, which has already been widely discredited. No governance check exists to ensure that the project's interests align with spending, or to verify that the maintainer acts with consent of a larger group to implement group decisions. Even worse, (per §2.3 of the Usage Agreement) terminating the relationship means ceasing use of the account; no provision allows transfer of the money somewhere else when projects' needs change.

Finally, the LF offers services that are mainly orthogonal and/or a subset of the services provided by a typical fiscal sponsor. Conservancy, for example, does work to negotiate contracts, assist in active fundraising, deal with legal and licensing issues, and various other hands-on work. LF's system is similar to Patreon and other platforms in that it is a hands-off system that takes a cut of the money and provides minimal financial services. Participants will still need to worry about forming their own organization if they want to sign contracts, have an entity that can engage with lawyers and receive legal advice for the project, work through governance issues, or the many other things that projects often want from a fiscal sponsor.

Historically, fiscal sponsors in FOSS have not treated each other as competitors. Conservancy collaborates often with SPI, FSF, and GF in particular. We refer applicant projects to other entities, including explaining to applicants that a trade association may be a better fit for their project. In some cases, we have even referred such trade-association-appropriate applicants to the LF itself, and the LF then helped them form their own sub-organizations and/or became LF Collaborative Projects. The launch of this platform, as proprietary software, without coordination with the rest of the FOSS organization community, is unnecessarily uncollaborative with our community and we therefore encourage some skepticism here. That said, this new LF system is probably just right for FOSS projects that (a) prefer to use single-point-of-failure, proprietary software rather than FOSS for their infrastructure, (b) do not want to operate in a way that is dedicated to the public good, and (c) have very minimal fiscal sponsorship needs, such as occasional reimbursements of project expenses.

Update on 2019-04-01: Community Bridge was also discussed on episode 0x65 of Free as in Freedom, which is available in mp3 format and ogg format.

Tags: conservancy, CLA, licensing

Successful First Copyleft Conf!

by Deb Nicholson on February 22, 2019

Last year, in FOSDEM's Legal & Policy Devroom , we promised to hold an event co-located with the 2019 FOSDEM to have more in depth discussion around the legal issues that we care about as a community and in particular, copyleft. We made good on that promise and this year the first annual Copyleft Conf took place on February 4th. About 150 people came to the event from copyleft enthusiasts to the "copyleft curious." The venue, DigitYser was funky and accessible and walking distance from many downtown Brussels hotels.

Molly deBlanc discussing the impact of free software on marginalized groups in front of a full room.

By all accounts, it was a very successful first event. We had 25 speakers, panelists and discussion leaders -- including lawyers, coders, academics, non-profit employees and industry folks. The audience was extremely engaged, participating in discussions and asking great questions.

The Right Time

Here at Conservancy, we've wanted GPL compliance and copyleft licensing to be de-mystified and approachable for a long time. We also wanted to provide a place to talk about the future of copyleft; where else it might impactfully be applied, how it might evolve as technology changes and how it could best serve the next generation of users and developers. Additionally, we needed it to be a friendly, welcoming space where new folks and more experienced folks could begin to bridge some gaps.

Our Most Sincere Thanks

Thanks so much to our program committee, our onsite volunteers and everyone who helped us spread the word about the event. We want to especially thank our friends from the FOSDEM video team, who joined us the day after FOSDEM (which is already a massive gift to the free software community!) and spent the day live-streaming and recording all our sessions. Thank you as well to the lovely folks at DigitYser who went above and beyond to assist the video team and promote our event to the local Belgian community.

Conservancy staff members in front of a Copyleft Conf sign.

Copyleft Conf would've been nothing without our speakers and discussion leaders, or our inspiring keynote Molly deBlanc, who set a high-minded and altruistic goal for the day's discussions. We are also very grateful to our sponsors and of course, all our lovely attendees who took a chance and came out for an inaugural event.

What's Next?

We're so glad you asked! First of all, make sure you stay in touch by joining our low-traffic mailing list. Also, stay tuned, because video is coming. We will let you know when it's all up and we hope you'll share the sessions you liked with friends and colleagues. And finally, please let us know if you have thoughts for making Copyleft Conf better next time, via email. We'd love to hear from you.

Both images are licensed CC.BY.SA, the picture of Molly deBlanc was taken by Leslie Hawthorn and the staff picture by Deb Nicholson (with help.)

Tags: conservancy, Copyleft Conf

Volunteers needed in Brussels! Also, January is Busy.

by Deb Nicholson on January 25, 2019

Hello again, friends! January at Conservancy is a very busy month -- we launch an Outreachy round, close our financial year, finish up our year-end fundraising and then? Well, then we get ready to go out and talk to folks about software freedom and events like linux.conf.au and FOSDEM. In fact our Executive Director, Karen Sandler's talk on "Right Not to Broadcast" and our Distinguished Technologist, Bradley Kuhn's talk on "Preventing the IOT Dystopia with Copyleft" are both already up.

And, oh boy, are we at FOSDEM this year.

We could really use your help in several key areas:

  • Helping us set up for video at Copyleft Conf on Sunday, February 3rd after FOSDEM in the evening
  • Midday booth help on either Saturday or Sunday
  • Saturday morning help bringing stuff to FOSDEM
  • General conference staff support or video support on Monday the 4th at Copyleft Conf

If you are able to help out with any of these tasks, please drop us a note so we can schedule you. We will be eternally grateful for any slice of time you can offer. Small orgs like Conservancy depend on our supporters to pitch in -- thank you so much!

Tags: conservancy, conferences

Next page (older) »

[1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35

Connect with Conservancy on Mastodon, Twitter, pump.io, Google+, Facebook, and YouTube.

Main Page | Contact | Sponsors | Privacy Policy | RSS Feed

Our privacy policy was last updated 25 May 2018.