Displaying posts tagged Wine
Conservancy's Member Projects are Building the Next Generation of the Free Software Movement
byon December 19, 2018
In order for free software to succeed, we must always be bringing new people to free software. In addition to bringing in developers, we need non-coding contributors and learners of all ages for our software to fulfill the promise of our movement. We love helping our member projects as they reach out to non-coding users and learners of all ages.
Conservancy is well-known for our work to support developers which is obviously super important -- there's no free software without well, people writing software. In fact, it's tough to build truly free software without free tools. So tools and code are critically important for software freedom, but I don't believe we can build a successful free software movement without conscientiously bringing in end-users. Many of our member projects focus on building amazing software for end-users, and maybe (while you're fixing computers for family over the holidays?) one of them can help you bring someone into the free software fold.
Several of our projects don't maintain code at all and/or work solely on helping people learn more about free software. MicroBlocks is a new programming language that enables kids and lifelong learners to start building toys or tools right away. Teaching Open Source collects and advises on curricula that helps college students understand open source development and its legal underpinnings. North Bay Python is a community-driven conference serving local Python developers -- including beginners. Outreachy brings people from underrepresented groups into free software via paid internships. The longevity of the free software movement depends on our collective ability to bring in young people and new people so we are proud to support educational efforts.
Two of our newest projects maintain code bases specifically for people who work at non-profits. Non-profit folks love stuff that is free as in cost and while they appreciate free as in freedom -- they also need code that does not need a lot of tinkering to be deployed. Backdrop CMS is a lightweight, easy to deploy Drupal fork specifically designed for small businesses and non-profits. Houdini helps organizations manage every aspect of their fundraising work. Free software is a good mission match for change organizations so it was great to welcome in two projects this year that are working intentionally to serve this sector.
Of course, we believe that software freedom is for everyone and a few Conservancy projects provide tools that can be used by anyone at all. Etherpad is shared note-taking platform that we use nearly every day in our work at Conservancy. Inkscape can be used for serious artists or those just dabbling in design. There are loads of tutorial videos to help new folks get acclimated and productive. Need a band flyer or church program? There's free software for that!
We even have projects at Conservancy that help people who are just beginning to explore free software. Homebrew enables users to install free software on their Apple systems while Wine helps people use a Windows program on a free operating systems. If you don't work at somewhere like the Conservancy, it can be difficult to ditch proprietary software. Projects like Homebrew and Wine help users find ways to use free software where they can and find a way to transition away from the non-free stuff at their own pace.
So wherever you are in your software freedom journey, Conservancy might have a project that can help. We look forward to helping our member projects do even more to bring in new fans, users and supporters of their work in 2019. Help us help them, by donating to Conservancy today! And be sure to let us know if one of our member projects helped you turn a new person into a free software user -- we love those stories.
Conservancy Activity Summary, October-December 2010
byon January 2, 2011
I had hoped to blog more regularly about my work at Conservancy, and hopefully I'll do better in the coming year. But now seems a good time to summarize what has happened with Conservancy since I started my full-time volunteer stint as Executive Director from 2010-10-01 until 2010-12-31.
We excitedly announced in the last few months two new Conservancy member projects, PyPy and Git. Thinking of PyPy connects me back to my roots in Computer Science: in graduate school, I focused on research about programming language infrastructure and, in particular, virtual machines and language runtimes. PyPy is a project that connects Conservancy to lots of exciting programming language research work of that nature, and I'm glad they've joined.
For its part, Git rounds out a group of three DVCS projects that are now Conservancy members; Conservancy is now the home of Darcs, Git, and Mercurial. Amusingly, when I reminded the Git developers when they applied that their “competition” were members, the Git developers told me that they were inspired to apply because these other DVCS' had been happy in Conservancy. That's a reminder that the software freedom community remains a place where projects — even that might seem on the surface as competitors — seek to get along and work together whenever possible. I'm glad Conservancy now hosts all these projects together.
Meanwhile, I remain in active discussions with five projects that have been offered membership in Conservancy. As I always tell new projects, joining Conservancy is a big step for a project, so it often takes time for communities to discuss the details of Conservancy's Fiscal Sponsorship Agreement. It may be some time before these five projects join, and perhaps they'll ultimately decide not to join. However, I'll continue to help them make the right decision for their project, even if joining a different fiscal sponsor (or not joining one at all) is the ultimately right choice.
Also, about once every two weeks, another inquiry about joining Conservancy comes in. We won't be able to accept all the projects that are interested, but hopefully many can become members of Conservancy.
In the late fall, I finished up Conservancy's 2010 filings. Annual filings for a non-profit can be an administrative rat-hole at times, but the level of transparency they create for an organization makes them worth it. Conservancy's FY 2009 Federal Form 990 and FY 2009 New York CHAR-500 are up on Conservancy's filing page. I always make the filings available on our own website; I wish other non-profits would do this. It's so annoying to have to go to a third-party source to grab these documents. (Although New York State, to its credit, makes all the NY NPO filings available on its website.)
Conservancy filed a Form 990-EZ in FY 2009. If you take a look, I'd encourage you to direct the most attention to Part III (which is on the top of page 2) to see most of Conservancy's program activities between 2008-03-01 to 2009-02-28.
In FY 2010, Conservancy will move from the New York State requirement of “limited financial review” to “full audit“ (see page 4 of the CHAR-500 for the level requirements). Conservancy had so little funds in FY 2007 that it wasn't required to file a Form 990 at all. Now, just three years later, there is enough revenue to warrant a full audit. However, I've already begun preparing myself for all the administrative work that will entail.
Project Growth and Funding
Those increases in revenue are related to growth in many of Conservancy's projects. 2010 marked the beginning of the first full-time funding of a developer by Conservancy. Specifically, since June, Matt Mackall has been funded through directed donations to Conservancy to work full-time on Mercurial. Matt blogs once a month (under topic of Mercurial Fellowship Update) about his work, but, more directly, the hundreds of changesets that Matt's committed really show the advantages of funding projects through Conservancy.
Conservancy is also collecting donations and managing funding for various part-time development initiatives by many developers. Developers of jQuery, Sugar Labs, and Twisted have all recently received regular development funding through Conservancy. An important part of my job is making sure these developers receive funding and report the work clearly and fully to the community of donors (and the general public) that fund this work.
But, as usual with Conservancy, it's handling of the “many little things” for projects that make a big difference and sometimes takes the most time. In late 2010, Conservancy handled funding for Code Sprints and conferences for the Mercurial, Darcs, and jQuery. In addition, jQuery held a conference in Boston in October, for which Conservancy handled all the financial details. I was fortunate to be able to attend the conference and meet many of the jQuery developers in person for the first time. Wine also held their annual conference in November 2010, and Conservancy handled the venue details and reimbursements to many of travelers to the conference.
Also, as always, Conservancy project contributors regularly attend other conferences related to their projects. At least a few times a month, Conservancy reimburses developers for travel to speak and attend important conferences related to their projects.
Google Summer of Code
Since its inception, Google's Summer of Code (SoC) program has been one of the most important philanthropy programs for Open Source and Free Software projects. In 2010, eight Conservancy projects (and 5% of the entire SoC program) participated in SoC. The SoC program funds college students for the summer to contribute to the projects, and an experienced contributor to project mentors each student. A $500 stipend is paid to the non-profit organization of the project for each project contributor who mentors a student.
Furthermore, there's an annual conference, in October, of all the mentors, with travel funded by Google. This is a really valuable conference, since it's one of the few places where very disparate Free Software projects that usually wouldn't interact can meet up in one place. I attended this year's Soc Mentor Summit and hope to attend again next year.
I'm really going to be urging all Conservancy's projects to take advantage of the SoC program in 2011. The level of funding given out by Google for this program is higher than any other open-application funding program for FLOSS. While Google's selfish motives are clear (the program presumably helps them recruit young programmers to hire), the benefit to Free Software community of the program can nevertheless not be ignored.
GPL Enforcement, primarily for our BusyBox member project, remains an active focus of Conservancy. Work regarding the lawsuit continues. It's been more than a year since Conservancy filed a lawsuit against fourteen defendants who manufacture embedded devices that included BusyBox without source nor an offer for source. Some of those have come into compliance with the GPL and settled, but a number remain and are out of compliance; our litigation efforts continue. Usually, our lawyers encourage us not to comment on ongoing litigation, but we did put up a news item in August when the Court granted Conservancy a default judgment against one of the defendants, Westinghouse.
Meanwhile, in the coming year, Conservancy hopes to expand efforts to enforce the GPL. New violation reports on BusyBox arrive almost daily that need attention.
More Frequent Blogging
As noted at the start of this post, my hope is to update Conservancy's blog more regularly with information about our activities.