LWN.net Logo

GnuTLS, copyright assignment, and GNU project governance

GnuTLS, copyright assignment, and GNU project governance

Posted Dec 21, 2012 0:38 UTC (Fri) by johnsu01 (subscriber, #34757)
Parent article: GnuTLS, copyright assignment, and GNU project governance

(The FSF unfortunately wasn't asked to comment for this article, but I wanted to add a few things now.)

We resolve violations on a regular basis, and in countries around the world. We usually do not publish the specifics, because most violations are resolved constructively -- it often turns out people have unintentionally made mistakes and do not deserve shaming once they have remedied the problems. If they do not respond to our offers to help them distribute in a compliant way, then we escalate to stop the flawed distribution. But at that point, lawyers are often involved, and there can be other constraints on publicity.

Here is a description of our compliance strategy. It's tricky business, figuring out how to let people know exactly how much of this work we do on a daily basis, without going too far and shaming those who have corrected their mistakes.

In recent conversations with Werner, it's become clear that our primary deficiency here was in communication. I admit that we did not pursue the violations he reported to us with the kind of urgency that I expect us to -- but we did pursue them, progressing through the steps of documentation, contact, and escalation that are required in these cases. The most recent violations were not of the easy kind, because they involved difficult-to-track-down companies with mostly bogus contact information. The problem is that we did not keep Werner up-to-date, and I am sorry for that. We've now adjusted our process to include explicitly notifying GNU maintainers when we take action. And of course we have stepped up our efforts to get these violations resolved.

Organizations like ours contain many moving parts, and unfortunately this creates opportunities for error. But there are always things that can be done to improve the situation, and it's my job to make them happen.

Many of the issues in the article are about lack of resources in nonprofit organizations. The solution to these issues is to help rally more resources, for us and for others doing this work. Volunteer time can be a big help, and so can monetary donations.

Thanks to a successful fundraiser at the end of last year, we were able to add additional staff resources to our licensing and compliance lab this Spring. Of course the new staff had to be brought up to speed, but this has already gone a long way toward reducing the backlogs we are facing. We have triaged the license violation reports queue, reducing its size by over 50%. We have opened more compliance cases than ever before, and have also rapidly made progress on outstanding licensing education questions. This effort has been amplified by our existing volunteer team, who does a lot of the heavy lifting answering licensing questions from the community.

We are also doing our major fundraising drive for the coming year, and are almost 40% of the way there. Like last year, our licensing area is one of the top ones on my mind for expansion. I will always strive to improve our efficiency in the way we use our current resources, but I am also confident that with more, we could get more done and do a better job living up to the expectations you all have for us.

Thanks!

-- John Sullivan, Executive Director, FSF


(Log in to post comments)

GnuTLS, copyright assignment, and GNU project governance

Posted Dec 21, 2012 1:53 UTC (Fri) by giraffedata (subscriber, #1954) [Link]

I believe some of the point this article wanted to make got confused by poor terminology: corporation/corporate, company, and nonprofit. Most nonprofits are companies and corporations, and the points made in the article seem to apply equally to various other entities, such partnerships and individual people.

Though I may not have seen through the confusion myself, I believe the two kinds of copyright holders the article really meant to refer to are 1) businesses; and 2) non-business entities. The latter could reasonably be called nonprofits, but to some people, nonprofit specifically refers to a status recognized by law that gives an entity privileges such as tax exemption.

A corporation, incidentally, is a group of people, chartered by the state, with a few special legal powers. The main ones are 1) the individual members are not liable for the actions of the group; and 2) the group can function like a single person in certain ways, such as signing contracts.

A company is any group of people working together on something.

A business is an enterprise whose purpose is economic gain.

Asking the FSF for comments

Posted Dec 21, 2012 15:19 UTC (Fri) by corbet (editor, #1) [Link]

Just to be clear on this: we stopped asking the FSF for comments many years ago because the FSF refused to talk to us without prior promises from us on what we would say and which terms we would use. We are unwilling to make such promises. If the FSF's policy on such things has changed, we would be pleased to know about it.

Asking the FSF for comments

Posted Dec 22, 2012 21:10 UTC (Sat) by quotemstr (subscriber, #45331) [Link]

> we stopped asking the FSF for comments many years ago because the FSF refused to talk to us without prior promises from us on what we would say and which terms we would use

Thank you. There's a reason I've been a subscriber for years. It's heartening (but, in a different light, unfortunate) that lwn.net has more journalistic integrity than the New York Times.

Asking the FSF for comments

Posted Dec 23, 2012 6:29 UTC (Sun) by ferringb (subscriber, #20752) [Link]

Just to be clear on this: we stopped asking the FSF for comments many years ago because the FSF refused to talk to us without prior promises from us on what we would say and which terms we would use. We are unwilling to make such promises. If the FSF's policy on such things has changed, we would be pleased to know about it. Good freaking $DEITY that's just fricking wrong, and not at all matching what the FSF is supposed to be about (or represents themselves as). While I'd like to believe their requirements there were just so that they could try enforcing 'gnu/linux' (which is @!#*ing retarded and overreaching), their general behaviour makes me think it was beyond that. Echoing what others have said, this frankly is a shame- FSF's goals are good and what most folk agree with, but the implementation? In need of a major refactoring in my books.

Asking the FSF for comments

Posted Dec 23, 2012 6:30 UTC (Sun) by ferringb (subscriber, #20752) [Link]

Related note, paying attention to the comment preview would've made that formatting far less attrocious. *cough*.

Asking the FSF for comments

Posted Dec 23, 2012 9:38 UTC (Sun) by jae (guest, #2369) [Link]

GNU/Linux is overreaching?

Do you have a non-GNU Linux system? Remove GNU coreutils, and then boot your system. Fun, innit?

It may be replacable, but it isn't being replaced.

As to the retarded part... only retards call others retarded.

Asking the FSF for comments

Posted Dec 23, 2012 10:23 UTC (Sun) by ekj (guest, #1524) [Link]

No, but "we are unwilling to talk to you about this matter unless you agree beforehand to use our preferred words" is.

Asking the FSF for comments

Posted Dec 23, 2012 11:37 UTC (Sun) by bronson (subscriber, #4806) [Link]

What on earth does coreutils have to do with the grandparent's post?

Asking the FSF for comments

Posted Dec 23, 2012 11:40 UTC (Sun) by rleigh (subscriber, #14622) [Link]

It is overreaching. I have no problems with the FSF/GNU using such terminology, that's their perogative. I use it myself. But to require other parties to use their terminology is certainly overreaching.

I've read time and time again people (mainly RMS) harp on and on about this point to others, quite often to the detriment of the real subject of discussion. That is to say that by obsessing over this minor point of terminology the discussion was sidetracked into irrelevance, and the actual important discussion was forgotten. This does not help the FSF/GNU in any meaningful way. Forcing others to adopt their terminology does not advance their real goal of software freedom.

Asking the FSF for comments

Posted Dec 31, 2012 21:32 UTC (Mon) by Trelane (subscriber, #56877) [Link]

> Do you have a non-GNU Linux system? Remove GNU coreutils, and then boot your system. Fun, innit?

I do. http://android.com

Whether this is better or worse than GNU/Linux is a pretty open question and a good conversation for friends over beers. :)

GnuTLS, copyright assignment, and GNU project governance

Posted Dec 23, 2012 0:21 UTC (Sun) by stevenb (guest, #11536) [Link]

> We resolve violations on a regular basis, and in countries around
> the world. We usually do not publish the specifics, because most
> violations are resolved constructively -- it often turns out people
> have unintentionally made mistakes and do not deserve shaming once
> they have remedied the problems.

There is no shame in reporting a successful resolution of a violation
issue. It hurts no-one to say that such-and-so a company had violated,
inadvertently, the conditions of the GPL on this-and-that piece of
software and that the issue was successfully resolved to satisfaction
for both parties. The company involved will typically have to show
the code anyway (assuming the typical resolution does not involve
removing the GPL-covered code).

No need for a wall of shame, and it might help change the perception
that the FSF is a lame duck.

GnuTLS, copyright assignment, and GNU project governance

Posted Dec 23, 2012 6:34 UTC (Sun) by mjg59 (subscriber, #23239) [Link]

Companies don't like having their name attached to negative connotations in places that Google can find, and so they're often more willing to compromise if they know that the outcome will be kept quiet. The question is whether public shaming is likely to prevent other companies from making the same mistakes - the evidence so far is that it doesn't, so keeping things quiet seems fairly reasonable.

GnuTLS, copyright assignment, and GNU project governance

Posted Dec 23, 2012 15:30 UTC (Sun) by stevenb (guest, #11536) [Link]

My point is that there is *no* shame in resolving an accidental GPL infringement. It's a matter of how you bring the message. You could even just make a list of entities using free software, with non-infringers and ex-infringers in a single list. Just to show where and how often free software is used.

Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds