Category Archives: Yorba

The new 501(c)(3) and the future of free software in the United States

yorba_logo_big.pngNote: I’m a software developer, not a lawyer.  I suspect I’m not the only coder whose eyes roll to the back of their head when legal or tax matters are discussed.

However, if you’re involved in the free software movement—especially in the United States—you may want to read through this, as long as it may seem.  It appears that the United States’ Internal Revenue Service has strongly shifted its views of free and open-source software, and to the detriment of the movement, in my opinion.

What follows should not be construed as legal or tax advice or professional interpretation of those laws.  If you have questions, please consult a professional.

Earlier this month the Yorba Foundation received a formal notice from the Internal Revenue Service (IRS) denying Yorba 501(c)(3) tax-exempt status.  It’s possible this is nothing to be concerned with (at least, not unless you’re a part of Yorba).  Reading their response, I believe this denial is actually a cause for concern for free software groups within the United States, and perhaps abroad.

A quick primer

501(c) is the section of the United States’ tax code dealing with tax-exempt organizations.  The third type (i.e. 501(c)(3)) are for organizations that are “organized and operated exclusively for one or more of the following purposes: religious, charitable, scientific, testing for public safety, literary, educational, fostering national or international amateur sports competition, or the prevention of cruelty to children or animals”.  IRS publication 557 gives the full run-down.  Wikipedia has a good explanation of 501(c) and 501(c)(3) as well.

Free/libre/open software organizations such as the GNOME Foundation, Mozilla Foundation, Apache Software Foundation, Linux Kernel Organization, WordPress Foundation, Django Software Foundation and more operate under a 501(c)(3) status.

One misconception is that 501(c)(3)’s don’t pay any taxes.  501(c) only provides exemption from Federal income tax.  Most states honor Federal exemption and will exempt those organization from state income taxes as well.  The organization must still fulfill other tax obligations (such as payroll, unemployment, and sales taxes).

The advantages of 501(c)(3) go beyond income tax exemption.  The status also allows donations to the organization to be treated as a tax exemption by the donor.  For those of you giving $25 or $50 that’s not much of an advantage (although those donations are most certainly appreciated!).  However, Yorba has seen donors offering potentially thousands of dollars back away because of our lack of 501(c)(3) status.  Many large charitable foundations and grants will only consider donating to groups with a 501(c)(3) status.

Last year there was a bit of a dust-up—a scandal to some, a distraction to others, depending on their politics—when many right-wing nonprofit organizations in the United States began complaining they were being unfairly targeted by the IRS.  Media inquiries determined IRS examiners were given “BOLOs” (Be On The Lookout) for certain keywords in 501(c) applications, including “Open Source Software”.  Last year I spoke with Wired about the issue.

The question of the IRS targeting certain groups has not died off, although the connection to free software has fallen off the radar screen.

Yorba’s application

The Yorba Foundation applied for 501(c)(3) in December 2009.  We applied as a charitable, scientific, and educational organization.  Remember that we only needed to meet the criteria for one of those to receive 501(c)(3) status.

We received two requests for clarification, one on June 23, 2010, and another on September 14, 2010, which we responded to in full.  We received a notice on October 5, 2011 that our application was still being processed.

The requests for clarification contained mostly non-surprising questions.  For example, “Describe whether your organization provides any goods or services for a fee.”  (We don’t.)  Some were odd: “Will any of your directors or employees reside at your facility [i.e. our office]?”  (Ah…no.)

Other than those three notices and a couple of phone calls with our representatives at the Software Freedom Law Center, that was it.

The final determination letter, the denial of exemption, is dated May 22, 2014, almost four and a half years after we first applied.  That strikes me as excessive, particularly since, as the above list of open-source foundations suggests, ample positive precedent existed.

The new 501(c)(3)

What I find alarming are some of the statements made by the IRS in their denial letter.  This is what could have a direct impact on the free software movement, at least here in the United States.  What follows are the most hair-raising statements in their denial letter and my interpretation and response (IRS’ statements are in italics):

You have a substantial nonexempt purpose because you develop software published under open source compatible licenses that authorize use by any person for any purpose, including nonexempt purposes such as commercial, recreational, or personal purposes, including campaign intervention and lobbying.

(To help with the legalese, remember that Yorba is applying as a tax-exempt entity, and so nonexempt purposes are those that are not charitable, scientific, etc.)

The IRS reasons that since Yorba’s open source software may be used for any purpose, Yorba is not a charity.  Consider all the for-profit and non-charitable ways the Apache server is used; I’d still argue Apache is a charitable organization.  (What else could it be?)

There’s a charitable organization here in San Francisco that plants trees throughout the city for the benefit of all.  If one of their tree’s shade falls on a cafe table and cools the cafe’s patrons as they enjoy their espressos, does that mean the tree-planting organization is no longer a charity?

Mere publishing under open source licenses for all to use does not show that the poor and underprivileged actually use the Tools. … You do not limit your distribution and do not know who uses the Tools much less if they use them for artistic purposes. … you do not know who uses the Tools much less what kind of content they create with the Tools.

(Here and elsewhere, “Tools” is IRS shorthand for Yorba’s software.)

The IRS is correct that Yorba does not know who is using our software or for what purposes, nor does Yorba limit the distribution of our software to a particular charitable segment of society.  But when I spend three milliseconds imagining how that would work, I shudder.

What’s more, these objections clash with three of the Four Software Freedoms and copyleft in general:

  • The freedom to run the program as you wish, for any purpose (freedom 0).
  • The freedom to redistribute copies so you can help your neighbor (freedom 2).
  • The freedom to distribute copies of your modified versions to others (freedom 3).

In other words, we (and, presumably, everyone else) cannot license our software with a GNU license and meet the IRS’ requirements of a charitable organization.

Freedom 1 (“The freedom to study how the program works”) isn’t attacked as non-charitable by the IRS, but it is defined as non-educational:

The purpose of source code is so that people can modify the code and compile it into object code that controls a computer to perform tasks.  Anything learned by people studying the source code is incidental.

Which is like saying the only point of an algorithm is its final answer, and so Einstein publishing E=mc2 offered nothing more to the world than a way to accurately measure the amount of energy in, say, a cube of sugar or a block of cheese.  Any deeper learning is incidental.

I can directly trace the start of my year career in software development to the first BASIC programs I encountered as a 9 year-old.  I pressed the Break key, typed LIST, and learned.  I didn’t receive any formal education in programming until my junior year in high school.  I know for a fact I’m not the only one.

How many coders learned from studying and modifying existing code?  Think about UNIX, BASIC, HyperCard, and just about every scripting language devised.  The availability of source code and its relation to learning how to program is so fundamentally correlated, it’s zen.

The development and distribution of software is not a public work even if published under open source or creative commons compatible licenses because software is not a facility ordinarily provided to the community at public expense. … In the face of such consistency of the key characteristics over four centuries we are constrained from extending the term public works to encompass intangibles such as software.

The “four centuries” of terminology being referenced here is that software is not a lake, dam, bridge, highway, etc.  In other words, because 17th century English Common Law doesn’t mention IMAP email clients or JPEG decoding, software is not a public work.

Sarcasm aside, these statements are annoying because they create a kind of Möbius strip Catch-22 with the earlier statements I quoted.  Since Yorba makes our software widely available to the public at large, we’re not truly charitable; but since software doesn’t meet the IRS’ definition of “public works”, making our software widely available is not charitably serving the public at large.

And then there’s this humdinger, which sounds like it came from a Douglas Adams novel:

…public works must serve a community.  Open source licensing ensures the Tools are accessible to the world.  We have not found any authority for the proposition that the world is a community within the meaning of § 501(c)(3).

There’s something delicious about the phrase “We have not found any  authority for the proposition that the world is a community.”  Mahatma Gandhi, Jesus Christ, and Martin Luther King Jr. are three I can name off the top of my head.

You are the copyright holder of some Tools code.  Private persons are the copyright holders of the portion of Tools code you do not own. … Even though you are the copyright holder to a portion of Tools code, the portion of Tools code owned by private persons cannot be a public work within the meaning of § 501(c)(3).

I believe what the IRS is inadvertently requiring here is copyright assignment.  Since Yorba does not require copyright assignment from our contributors, the IRS appears to think our software cannot be a public work.

Copyright assignment is controversial in the free software community.  (A nice overview can be found here; the controversy up-close and in-person can be found here and here.)

I hope I’m wrong about this.  I doubt they’re going to start enforcing this in the future for organizations that already enjoy exemption.  If they do, it will be a royal mess for those projects having to contact every author of every non-trivial contribution and get them to sign over their rights.  This is all a big if, of course.

Where Yorba stands

This does not spell disaster for Yorba.  The Foundation’s existence does not hinge on 501(c)(3) status.  It certainly would’ve been advantageous if the IRS had granted it.  It certainly would’ve been a better world if the IRS hadn’t waited four and a half years to inform us of their decision.

We have no plans to appeal their decision.  It looks to be an arduous legal battle we cannot afford.

I hope other open source projects will take note of this decision, especially projects considering applying for 501(c) status.

For those who think I’m being alarmist, I encourage them to consider the above statements by the IRS and ask themselves how the good projects already granted 501(c)(3) would’ve stacked up under the IRS’ new parameters.

I also recognize that I’m cherry-picking statements from the IRS for my commentary.  I selected the ones I thought would be of most interest to the community.

The full PDF of the IRS’ decision can be found here.

Yorba and GNOME

GNOME ParkingIn October I briefly announced that Yorba was virtually moving — that we were in the process of transitioning from our self-hosted project server to GNOME’s infrastructure.  Well, the move is all but complete.  I’m pleased to announce that we’re now officially hosted inside the GNOME ecosphere: Bugzilla,, mailing lists, the works.  Here are links to our new pages:

First, let me clarify that the Yorba Foundation has not merged or become subsumed by the GNOME Foundation.  Financially and legally we’re still independent entities, albeit with a shared goal of spreading free software far and wide.

So, why’d we do it?

Yorba has always been a GNOME developer.  Our applications are GNOME-specific and we build them with GNOME technologies and libraries.  For almost five years now we’ve enjoyed a certain independence developing from outside the GNOME infrastructure, but we also were giving up a certain amount of integration that perhaps would’ve made our offerings that much better.  It’s a trade-off.  Recently we re-evaluated those trade-offs and decided that it made sense for Yorba to move into a tighter GNOME orbit.  As such, we look forward to working closer with the GNOME team on things like application design and the future direction of the free desktop.


Yorban Charles Lindsay did a great job moving a mountain of our data to, in particular our voluminous ticket database, which is approaching five years old.  Not only are all our tickets now imported into GNOME’s Bugzilla (even their attachments), the final entry in our legacy Redmine tickets include instructions on how to locate that ticket in GNOME Bugzilla.  He automated much of this with a Python script we’ve made available on github in case someone else out there needs to move their tickets (“issues” in Redmine parlance) from Redmine to Bugzilla.

I’d like to extend deep thanks to GNOME sysadmin whiz Andrea Veri for making the transition about as painless as I could imagine — no, even less.  Andrea guided us through this process with grace and steady vision.  I’d like to echo William Jon McCann’s call to “ensure Andrea Veri’s contract is renewed and stays on as the GNOME sysadmin”.  You have Yorba’s vote, av!

New version number scheme

In the past, Yorba used a standard sequential versioning scheme (0.1.0, 0.1.1, etc.)  To differentiate between stable releases and builds from source control, we appended a descriptor to the version number (0.1.1+trunk, 0.1.1+branch).  When we needed to issue pre-release tarballs to our partners, we used a different descriptor (0.1.1pr1, 0.1.1pr2).

Over the years we received a number of complaints about this, especially from package and repository maintainers (whose business, if you think about it, is very much about version numbers).  With our move to GNOME, it seemed like a good time to revisit our scheme.  The one numbering system we kept hearing was worth adopting was GNOME’s itself, where even numbers represent stable releases and odd numbers represent unstable releases.  (I believe GNOME adopted this from the Linux kernel; where they got it from, or if they invented it themselves, I don’t know.)  In addition, it was requested that we release unstable tarballs more often, to give distributors and packagers more time to prepare.

We decided to make the switch and have already adopted this with Geary.  We recently released an 0.5.0 unstable, and will follow up soon (probably after the holidays) with an 0.5.1, and so forth.  The next stable release of Geary will be 0.6.  Similar changes will be coming soon for Yorba’s other projects.

Translations / internationalization / localization

One goal we have is to move all our projects that require internationalization into GNOME’s system.  We’re not quite there yet; we need to do a little more work on our build systems in order to integrate fully.  I hope to get that wrapped up next month.  If you’re eager to offer translations for our projects, all I can ask is for your patience until we get this resolved.  (If you’re a GNOME internationalization whiz, we’d appreciate your help in finishing the work.)

Due to this expected move, I’ve closed our Transifex project repositories.  If you’ve made some translations recently, don’t worry, they’re not lost, I simply haven’t merged in the final snapshot of those strings.  I’ll do so after the holidays.


Even though we no longer use it, we’ve decided to keep our Redmine project management server up for historical reasons.  We’ve locked it down to prevent any changes.

With the server transition we also decided to clean house a bit.  Over the years Yorba has developed or adopted technologies that didn’t get off the ground.  Although Yorba is no longer maintaining them, we didn’t want them to simply disappear, as so we’ve moved them to our public github repo. The projects I’m speaking of are media (our early attempt at audio/video editors) and Valadate (a Vala-based unit testing framework).

October miscellany

It’s been a wild October!  It started with us releasing Geary 0.4 and Shotwell 0.15, and then a whole lotta more stuff happened.  Some quick bits regarding the past four weeks (or so):

Montreal Summit

Parc La Fontaine
Parc La Fontaine

I’d like to extend my (belated) thanks to everyone who organized and hosted the Summit this year, it was a great event!  Thank you Savoir Faire Linux for organizing everything and CRIM for hosting all of us.  Lots of familiar faces and some new ones too.  In particular it was good to hear about GTK/GLib things to come, like GNotifications and a formal model for GtkListBox, both things we’d like to take advantage of in Geary.

Montreal is a beautiful city and fortunately I had a chance to explore it before the Hackfest opened.  I’m pleased to report that while there I enjoyed what sounds to be the Montreal culinary trifecta: bagels, smoked meat, and poutine.

We’ve moved (physically)

CC BY 2.0 ~ Gary Soup
“Enjoy some spicy food”

Yorba resided in San Francisco’s Mission District for over four and a half years, but the time has come for a change.  We’ve been selling off furniture, cleaning off desks, and boxing up things for our big move, which happened today.  Fortunately the move was painless and quick, and we’re now settled in our new office on the hairy edge of the Financial District down the hill from Chinatown.  (We celebrated finishing the move with a great meal at Henry’s Hunan; go see this fellow, who has eaten and reviewed every item on their menu to teach himself Tomcat.  That floors me for a lot of reasons.)

Unfortunately the preparations for the move has taken our attention off of patches and coding, but that should soon change now that we’re settled.

We’re moving (virtually)

Coincidentally, Yorba is also moving virtually — we’re transitioning from our self-hosted server to (tada!) the GNOME infrastructure.  Yes, soon all of Yorba’s projects will live under the GNOME umbrella.  We’re starting small to work out the kinks, but by the end of the process Shotwell, Geary, Valencia, and gexiv2 will be available at  More information coming soon as things firm up.