FSF will not change unless somebody gives them a strong reason to change.

For example, if GNU developers write the following email to FSF, that
will bring change.

Each developer needs to make their own decision if they will send the
email.  RMS has previously suggested he would not like people to
completely abandon the agreements.  The email template below is only for
a conditional suspension of the agreement.  Nobody can tell you to
continue assigning[1] your rights to FSF if you want to wait for more
clarity about FSF's future.

You can still keep coding during the suspension: if a significant
quantity of code is published and virtually embargoed like this, it
creates an incentive for FSF to satisfy those people and gain rights
over that code.


Daniel Pocock
Debian Developer

To: John Sullivan <jo...@fsf.org>
CC: (relevant project mailing lists)
Subject: suspension of contributor agreement

Dear John,

I am writing to suspend my FSF / GNU project contributor agreement[1]
signed __/__/____

I will continue contributing code to (names of projects) retaining all
intellectual property rights personally during this suspension of the

I also wish to notify you that my contributor agreement will be
reinstated when FSF makes a satisfactory commitment about leadership and
governance issues.  I have not yet decided what will constitute a
satisfactory commitment, for now, I will review the proposals put
forward by FSF and I may contribute further criteria as the situation

All work completed during this suspension will be assigned
retrospectively to FSF when the conditions of reinstatement are satisfied.



1. https://www.gnu.org/prep/maintain/maintain.html#Legal-Matters

Reply via email to