%% LyX 2.2.2 created this file.  For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[letterpaper,english]{article}
\usepackage[T1]{fontenc}
\usepackage[latin9]{inputenc}
%\usepackage[paperwidth=8.5in,paperheight=11in,landscape]{geometry}
\usepackage[verbose,tmargin=1.6in,bmargin=1.8in,lmargin=1.9in,rmargin=1.9in]{geometry}
\usepackage{color}
\definecolor{shadecolor}{rgb}{0.679688, 0.5, 0.660156}
\usepackage{wrapfig}
\usepackage{framed}
\usepackage{url}
\usepackage{graphicx}
\usepackage{setspace}
\usepackage{babel}
\usepackage{epsf}
\usepackage{url}
\usepackage{float}
%noprint does portrait orientation and pagination appropriate for reading as a
%PDF. print does landscape orientation and pagination appropriate for printing.
%\usepackage[noprint,1to1]{booklet}
\usepackage[print,1to1]{booklet}
\usepackage{colortbl}

% Margins and such
% Switch back and forth between these two sets of margins for print versus on-screen.
%\setlength{\paperheight}{18in} --2017-05-27 seems unnecessary, remove? -johns
%\setlength{\paperwidth}{6in} --2017-05-27 seems unnecessary, remove? -johns
\setlength{\paperheight}{8.5in}
\setlength{\paperwidth}{17in} 
%\setlength{\voffset}{-0.10in} --2017-05-27 seems unnecessary, remove? -johns
\setlength{\fboxsep}{12pt} % Puts ``padding'' around the text in all the boxes

%\setdvipstargetpages % this has to change if printing to pdf --2017-05-27 seems unnecessary, remove? -johns
%\pagespersignature{6} --2017-05-27 seems unnecessary, remove? -johns
\special{!TeXDict begin /landplus90{true}store end} % craziness to work with ghostview
%\special{!TeXDict begin <</Duplex true>> setpagedevice end} % duplex
%\special{!TeXDict begin <</Tumble true>> setpagedevice end} % short binding


\hyphenation{key-note Media-Goblin Free-dom Snowden Libre-Planet IceCat
  November Public Algeria Dribbble English Software ser-ver wide-ly
  wor-ld ker-nel need-ed Law-rence Open-Office an-nounced proj-ects
  proj-ect ac-a-de-mia art-ists coun-ted glob-al Dan-iel Open-Document
  Mi-cro-soft sup-port-ed anon-y-miz-er page-views
  de-fec-tive-by-de-sign stopp-ed co-op-er-at-ing re-stric-tions
  Java-Script}

\widowpenalty=300
\clubpenalty=300
% Was 1500
\tolerance=8000

 % no numbering on sections in the TOC

% LaTeX redefinitions (removes ``Table:'' and ``Figure:'' from captions)


\long\def\@makecaption#1#2{%
  \vskip\abovecaptionskip
  \sbox\@tempboxa{#2}%
  \ifdim \wd\@tempboxa >\hsize
    #2\par
  \else
    \global \@minipagefalse
    \hb@xt@\hsize{\hfil\box\@tempboxa\hfil}%
  \fi
  \vskip\belowcaptionskip}


% colors

\definecolor{Myblue}{RGB}{173,127,168}

% fonts

\font\mhfont = cmss17 scaled 3000 % masthead
\font\issfont = cmss10 % issue number and month/year

% masthead
% #1 = filename for eps logo graphic
% #2 = Name for big Bulletin title
% #3 = Issue number (include the word Issue)
% #4 = Month and year

\newcommand{\masthead}[4]{
\begin{center}
\includegraphics*{#1}
\vspace*{0.12in}

\mhfont #2
\issfont
\vbox{
  \hbox{#3}
  \hbox{#4}}
\end{center}
\hrule
\vspace*{0.12in}}


\newenvironment{article}[2]{
%\addvspace{24pt}
\addvspace{8pt}
\vbox{
\begin{center}
{\usefont{OT1}{cmss}{bx}{n}\huge#1}\\
\smallskip
{\usefont{OT1}{cmss}{m}{n}\Large#2}
\end{center}
}\nobreak\vskip 0pt plus 10pt \nobreak
}{}

% big caps for first letter of article

\font\capfont = cmr17 scaled 1600
\def\cap#1{%
\setbox0=\hbox{\capfont #1}
\noindent\hangindent=\wd0\hangafter=-2
\dimen0=\ht0
\advance\dimen0 by -\baselineskip
\vbox to 0pt{\vskip-\dimen0\hbox to0pt{\hskip-\wd0\box0}}%
}

% for some letters it may be desirable to back up the first line:
% \cap{A}\hskip-4pt{}pple

% Little gnu head article ender

\def\ender{~\hskip-4pt\lower1pt\hbox{\includegraphics*{gerwinski-gnu-head.eps}}}

% for scaling graphics

\def\epspic#1#2{
  \def\epsfsize##1##2{#1##1}
  \epsfbox{#2}
}

% Interview 


\newenvironment{interview}{
\def\item##1{{\sffamily\bfseries ##1 }}
}{
}

\font\capfont = cmr17 scaled 1600
\def\cap#1{%
\setbox0=\hbox{\capfont #1}
\noindent\hangindent=\wd0\hangafter=-2
\dimen0=\ht0
\advance\dimen0 by -\baselineskip
\vbox to 0pt{\vskip-\dimen0\hbox to0pt{\hskip-\wd0\box0}}%
}

% Callout boxes
% First argument is title, second argument is text

\newcommand{\callout}[2]{\begin{center}
    \begin{figure}[htb!]
      \colorbox{Myblue}%
      {\parbox[t]{2in}{%
          \textbf{\Large{#1}}
          \vspace{6pt}
          \hrule
          \vspace{4pt}
          \large{#2}}}
    \end{figure}
  \end{center}}

% Donation box
% Insert the box listing the options for how to donate 
% The argument is the description of the current new member gift.

\newcommand{\donate}[1]{
  {\begin{center}
      \colorbox{Myblue}{\parbox[l]{2.0in}{%
          {\bf\large How to Contribute}
          \vspace{6pt}
          \hrule
          \vspace{4pt}
          \begin{list}{}{\setlength{\leftmargin}{0pt}}
          \item {\bf Associate Membership}: \newline Become an associate member of the FSF.  Members will receive a bootable USB card,  e-mail forwarding, and an account on the FSF's Jabber/XMPP server.  To sign up or get more
            information, visit \url{member.fsf.org} or write to
            \url{membership@fsf.org}.
          \item {\bf Online}: Use your credit card or PayPal account
            to make a donation at \url{donate.fsf.org} or contact \url{donate@fsf.org} for more information on supporting the FSF.
          \item  {\bf Jobs}: List your job offers on our jobs page: \url{fsf.org/jobs}.
          \item {\bf Free Software Directory}: Browse and download from thousands of different free software projects: \url{directory.fsf.org}.
            \item {\bf Volunteer}: To learn more, visit
            \url{fsf.org/volunteer}.
            \item {\bf LibrePlanet}: Find local groups in your area or start your own at \url{libreplanet.org}!
           \item {\bf Free Software Supporter}: Receive our monthly email newsletter: \url{fsf.org/fss}.
             
          \end{list}
          \vspace{2pt}}}
          
    \end{center}}}

% Copyright box
% This inserts the verbatim copying notice

\newcommand{\verbatimcopyright}[1]{
  \begin{center}
    \parbox[t]{2.00in}{%

\noindent\hbox{}{
\center\includegraphics{bitcoinqr.eps}

\center\small\noindent Donate to the FSF with Bitcoin.
\break\break
}
      \noindent Copyright \copyright\/#1\\Free Software Foundation, Inc.
        \bigskip         

        \noindent{The articles in this bulletin are individually
          licensed under the Creative Commons Attribution No~Derivative Works 4.0. 
          \url{https://creativecommons.org/licenses/by-nd/4.0}}
        \bigskip

        \noindent{Images from \textit{Wires for Empathy}
are licensed under the Creative Commons Attribution Works 4.0. 
          \url{https://creativecommons.org/licenses/by/4.0}}
        \bigskip

      \noindent{Published twice yearly by the Free Software Foundation, 51 Franklin Street, 5th Floor, Boston, MA 02110-1301, (617) 542-5942. \\ \url{info@fsf.org}, \url{fsf.org}}

         \begin{flushright}
         \end{flushright}}
         

    \end{center}}

% Gear box
    \newcommand{\gnugear}{
      {\begin{center}
          \colorbox{Myblue}{\parbox[l]{2.0in}{%
              {\bf\large Show Your Support with GNU Gear}
              \vspace{6pt}
              \hrule
              \vspace{4pt}
              Order stuff at \url{order.fsf.org}
              \begin{list}{\textbullet}{\setlength{\leftmargin}{0pt}}
              \item  {\bf Happy Hacking T-shirt}
              \item {\bf Free Software Free Society T-shirt}
              \item  {\bf GNU Baseball Caps}
              \item  {\bf Much more}
              \end{list}}}
        \end{center}}}

% TOC -- not used in Spring 2017, went back to manual because of
% formatting problems
%% \usepackage{tocloft}
%% \cftsetindents{section}{0.0in}{0.0in}
%% \cftsetindents{subsection}{0.0in}{0.0in}
%% \setlength{\cftbeforesecskip}{0pt}


%% \renewcommand{\cftsecfont}{}
%% \renewcommand{\cftsecpagefont}{}


%% \newcommand{\mytoc}{
%%   \noindent\colorbox{Myblue}{
%%     \parbox[l]{1.85in}{
%%       \setcounter{secnumdepth}{-1} % no numbering on sections in the TOC
%%       \vspace{-0.5cm}
      
%%       \raggedright\tableofcontents
%%     }
%%   }
%% }

 % Author
\usepackage{titlesec}
\titlespacing\section{0pt}{10pt}{-18pt}

\newcommand{\myauthor}[2]{
  \textbf{\textit{ \begin{flushleft}By #1\break
#2 \end{flushleft}}}
  \vspace{-8pt}
}






%JS \makeatother

\begin{document}
\twocolumn[\masthead{bulletin-logo.eps}{Bulletin}{Issue 30}{Spring/Summer 2017}]

% Table of contents
\setcounter{secnumdepth}{-1} % no numbering on sections in the TOC
\noindent
\colorbox{Myblue}{%
  \begin{tabular}{p{1.5in}p{0.12in}}
    \Large\textbf{Contents} \\
      \\
      \raggedright\normalsize{{Copyleft's decline: A claim without evidence}} & {1}\
      \\
      \raggedright\normalsize{{Respects Your Freedom certification program continues to grow}} & {3}\
      \\
      \raggedright\normalsize{{Join the federation}} & {5}\
      \\
      \raggedright\normalsize{{What not to miss from LibrePlanet}} & {7}\
      \\
      \raggedright\normalsize{{FSF ongoing infrastructure upgrades}} & {8}\
      \\
      \raggedright\normalsize{{Mastodon interview}} & {9}\
      \\
      \raggedright\normalsize{{On the road with RMS}} & {11}\
      \\
  \end{tabular}
}

\section{Copyleft's decline: A claim without evidence }

\myauthor{John Sullivan}{Executive Director}

\cap{W}e know that one tactic for convincing people to stop doing
something you don't want them to do is to tell them nobody else is
doing it anymore. Peer pressure is a powerful force, and in the world
of technology, there's a particularly strong desire to be seen as
current. That could be why we've been seeing reports in the tech press
that the use of copyleft licenses, like the GNU General Public License
(GPL), is declining in comparison to the use of lax permissive
licenses like Apache or Expat (commonly but unfortunately called
``MIT'').

All of the articles I've seen making this claim cite the same few
corporate ``studies\textquotedblright{} as their primary sources.
The evidence they present is not evidence at all, because neither
the specific data set nor the methodology used are published. No field
of science accepts experimental conclusions that can't be reproduced
by others. We shouldn't accept such conclusions in the area of counting
license use either.

Counting the licenses used by free software projects may seem straightforward.
By definition, all of their code is published in publicly-available
repositories, and should carry easy-to-read notices indicating the
applicable licenses. But doing it turns out to involve a minefield
of potential errors and biases.

\begin{figure}[H]
  \includegraphics[width=0.9\columnwidth]{sumana_bulletin}
  Sumana Harihareswara, keynote speaker at LibrePlanet
  2017
\end{figure}

I reviewed some of the data likely used by companies counting licenses,
and found obvious mistakes. As of May 2017, \url{openhub.net},
operated by the company Black Duck and used in its license-counting
data set, lists GNU Bash as GPLv2-or-later. Bash has been GPLv3-or-later
for several years. While it's now been corrected, the site also listed
GNU Emacs as GPLv2-only, a license the project has never had. I found
these errors on the first two projects I spot-checked. How many more
would we find if the full data set were identified?

Even if the inputs were perfect, writing software to count licenses
is extremely difficult and requires making many normative choices.
These choices need to be disclosed if we're to draw any accurate conclusions.
The problems start with deciding what qualifies as a project to count.
Do you care whether the code actually works, or whether it's had contributions
from more than one person? Projects often change code hosting sites
without removing their old home. If you are crawling multiple hosts,
is your code smart enough to tell when two programs are the same?
Does a forked or slightly modified version count as a separate program?
Versions of the same program for different operating systems can conceivably
each be under a different license. Do you count them separately?

After you've determined which projects qualify, you have to parse
their license information. License notices are not yet predominantly
in structured, machine readable formats. They are written by and for
humans, with typos and inconsistent formatting that confound automated
parsers. When licenses are recognized, there may be several of them.
A GPL-covered project can contain files carrying lax permissive license
notices, because it is allowable\textemdash and common\textemdash to
redistribute such files as part of a copyleft work. Does that add
one just to the GPL column, or do you also increment the noncopyleft
license columns?

Once you've decided a project qualifies, and have figured out how to
represent its license(s), you then have to decide how much weight
to give it. Do you care about the size of the codebase? If you don't,
then you will count a large package like GNU Emacs as equal to a small
node.js library. If you do care, then you have to create categories
to better compare apples to apples, and those criteria need to be
shared for others to properly understand the results. Do you care
about the size of the user base? If you don't, you will count a GitHub
repo containing someone's personal configuration files, kindly shared
under a free license but really intended only for their personal use,
the same as GCC, used as the foundation for billions of dollars in
economic value. If you do care, then you need to share how you determined
the user base and how that was incorporated.

Counting licenses used across the entire universe of free software
is not an easy job. Whether any given article claiming that copyleft
is declining is part of an intentional anti-copyleft effort or not,
it risks creating a self-fulfilling prophecy by increasing peer pressure
against choosing copyleft licenses. As an individual advocate for
user freedom, you can make a difference by questioning these claims
when you see them.

Ask two questions: First, is the methodology, including the code used
to do the counting, published? Second, is the data set published?
If the answer to either one of the above is no, then the claim should
be ignored entirely. It's no better than an assertion, and the interpretation
of the \textquotedbl{}data\textquotedbl{} will be like reading tea
leaves\textemdash just the author's own confirmation bias from within
their particular bubble.

You can avoid the self-fulfilling prophecy by choosing copyleft for
your own projects. Individual license choices have a large impact,
because they influence the decisions made by future projects based
on yours, or that integrate with yours. From my bubble, I see plenty
of people continuing to choose copyleft. We interview some of them
every month in a blog series.\footnote{\url{fsf.org/blogs/licensing}}
Recently, the Department of Defense chose the Affero GNU GPL as the
license for a new project, and plans to use the GPL as the default
for its future projects.\footnote{\url{code.mil}}

You can also help efforts to scientifically collect information about
software license usage. Our Free Software Directory is growing into
a useful resource for this, and welcomes volunteer contributions.
The Software Heritage Project will be extremely useful in this area
as well, and there are packages like FOSSology which aim to do the
work of license counting with free, auditable software.\footnote{Software Heritage: \url{softwareheritage.org}, FOSSology: \url{fossology.org}}

In the end, we need to remember that numbers about who chooses which
free license may not be that useful or interesting. All of this is
part of the same pie as proprietary software, and so increases in
noncopyleft use may be trading off with proprietary licenses, not
copyleft, and noncopyleft licenses are still free software licenses.
If every proprietary license were replaced with a noncopyleft free
license tomorrow, that would be an amazing victory for our movement.

Licenses are a means to the end of user freedom. Copyleft remains
the best tool we have for achieving and securing that freedom in the
context of our current global regimes on copyright, patents, and contracts.
We need it now more than ever. Software under noncopyleft licenses
is free, but contingent\textemdash future improvements to it can be
made proprietary, essentially pulling the rug out from under us. Only
copyleft builds a solid foundation for freedom. If we want to measure
something, let's focus on metrics of how more or less free we are
in our daily, increasingly digital, lives. \ender

\section{Respects Your Freedom certification program\\continues to grow}

\myauthor{Donald Robertson}{Licensing and Compliance Manager}

\cap{T}he Free Software Foundation's Respects Your Freedom (RYF)
certification program is growing rapidly. In March of this year, we
certified three devices from Vikings GmbH, bringing the total number
of certified devices to twenty-two.\footnote{The Vikings devices most recently certified include: Vikings USB Stereo
Sound Adapter, Vikings D16 Mainboard, and Vikings X200 libre-friendly
laptop.} Certifying multiple devices at once quickly expands the pool of hardware
that users can trust, but can also work as a stress test of our certification
system.

When the RYF program first launched, no one knew how many companies
would be up to the task of ensuring that their hardware only came
with freedom inside. We are certainly pleased with the response. Increasingly,
however, companies are looking to follow in Vikings' footsteps with
ever larger launches. It makes sense: once you know what it takes
to meet the RYF criteria, it becomes easier to see all of your hardware
as potential candidates.

As the number of applicants and devices has risen, so has the need
to refine the certification process to better handle increased interest
in RYF. We plan on publishing more information about the process,
so applicants can better know what to expect. Right now, the criteria
are published, but the actual process from initial contact and application
form, to rounds of review, to certification and announcement aren't
publicly documented in full.\footnote{\url{u.fsf.org/ryfcriteria}}
We are also working with potential partner organizations to help set
up something like a mentoring program to help first time applicants
through the process.

Another big item is that we are working with current applicants to
rethink how we handle reviewing the physical devices themselves. Currently,
we ask for two samples of each device be sent to the FSF. That certainly
isn't too onerous when dealing with a single device, but that changes
with the prospect of potentially dozens of pieces of hardware. Particularly,
we are looking at how we handle what are essentially variations of
the same device, such as a laptop with different pre-installed distributions.
The same base device can be sold with many different potential configurations
of components. Each configuration can represent an issue regarding
what software might be hiding inside, or what free software is compatible
with that component. This part of the process is not easy to improve,
however. The RYF program certifies a particular piece of hardware
as it is sold to a user. It is not a general recommendation of a particular
retailer, so we need to check all devices that are up for certification.
We want to streamline the process while still maintaining a robust
standard of review, and we are working with current applicants to
figure out the proper balance between those two goals. With these
upcoming changes, we hope to continue to help the program expand while
maintaining its rigorous standards.

\begin{wrapfigure}{L}{0.4\columnwidth}%
  \includegraphics[width=0.4\columnwidth]{RYF}
 \end{wrapfigure}%

Historically, RYF devices have leaned heavily on refurbishing existing
hardware with a fully free stack of software. But more and more we
are hearing from companies looking to build RYF devices from the ground
up. Controlling the design of their own hardware means they can avoid
problems from the start, rather than having to reverse engineer solutions
on existing devices. Because hardware manufacturers are increasingly
locking down machines, being able to create works designed with freedom
in mind is necessary for the future of the RYF program. This is an
exciting development, and one that is coming much sooner than anticipated.
In addition, we are also receiving applications for many types of
devices that we haven't previously certified, bringing us closer to
one day having a pool of certified devices that could meet all of
a user's needs.

There is an incredible number and variety of devices currently working
their way through our certification program, so keep an eye out for
upcoming announcements.

There is more information about RYF, including a list of certified
devices, on \url{fsf.org/ryf}.\ender

\ 

\begin{figure}
  \includegraphics[width=0.9\columnwidth]{wpe-00}

  \small{Images are from \textit{Wires for Empathy}, directed by
    Bassam Kurdali and made using Blender: \url{wiresforempathy.org}.}
\end{figure}

\begin{figure}
  \includegraphics[width=0.9\columnwidth]{wfe-03}
\end{figure}

\section{Join the federation}

\myauthor{Georgia Young}{Program Manager}

\cap{S}ince 2004, online interaction between friends and people
with shared interests has slowly become dominated by a few giant social
networking sites. You probably know of them: Facebook, Twitter, and
Instagram are among those with the most users, and focus on sharing
images, links, video, and chat.

These sites want to control your computing. They use their own servers,
which you can't access. They force you to run their preferred systems
for accessing these sites. They promote use of nonfree software by
serving users nonfree JavaScript (for example, Facebook does this
for some features) that runs on users' local machines, and by promoting
and distributing proprietary mobile apps to use their services.\footnote{Facebook, Twitter, and Instagram all use and contribute individual
components that are available under licenses included in the GNU Project's
list of free software licenses: \url{u.fsf.org/lb}} They control what technologies you can use to access their servers,
what you are allowed to do on their site, and the data you generate.

\textbf{Federated and free: Why it's good}

Luckily, there's an option that allows more people to have direct
control over their social network activity: free software federation.\footnote{\url{u.fsf.org/284}}
There are many reasons why free software federation is great, including: 
\begin{itemize}
\item Interoperability: On a federated (also known as "distributed") network,
people whose accounts are located on different instances can communicate
with each other.\footnote{\url{u.fsf.org/286}} 
\item Freedom: In theory, federated networks can include nodes pushing proprietary
software, but in practice, it's an approach favored more by free software.
You can examine the code yourself in order to understand what it does
and determine whether it can be trusted. You can modify it, too. The
microblogging software Mastodon is an alternative implementation of
GNU social\textendash and that's possible because GNU social is free
software.\footnote{Mastodon: \url{u.fsf.org/285}, GNU social: \url{gnu.io/social} }
So the ideal social web isn't just federated, it's a federation of
free software nodes. 
\item Resilience: Because a federated network is made up of multiple instances,
each used by a different set of people, rather than being operated
by one company with all users relying on the same server, the failure
of one instance doesn't affect all users. 
\item Privacy: Using a federated network means it is harder for a large
company to spy on you. And if you run your own node in the network,
you can inspect the code to make certain that the privacy of data
associated with your account is being respected. 
\item Preserving your data: When you place photos or other documents that
are important to you in the hands of centralized, corporate-controlled
social media software, you could unexpectedly lose those things if
the company that controls the servers decides to discontinue the program
or block access to your account. If you host your own instance, you
decide. 
\end{itemize}
\textbf{Federation sounds weird. How does it work?}

In practice, someone using a federated social network is likely to
detect only a slight difference. Take the experience of GNU social
versus Twitter, for example. If you want to use Twitter, you need
to create an account on \url{twitter.com}, nowhere else. You can
only reply to another person if they also have an account on twitter.com,
and each handle looks like this: \texttt{@fsf}. (Yes, the FSF does
use Twitter, in a way that avoids using any proprietary software.\footnote{\url{fsf.org/twitter}})

But if you use a federated social network, like GNU social, you might
create your account on a GNU social instance, like \url{quitter.se},
but that site is only one of many options.\footnote{\url{gnu.io/social/try}}
If the FSF (\texttt{fsf@status.fsf.org}) wants to talk to 2016 Free
Software Award winner Alexandre Oliva, we would tag his full handle:
\url{@lxoliva@social.libreplanetbr.org}.

The protocols underlying free decentralized social media are continuing
to advance. Three years ago, the World Wide Web Consortium (W3C) created
a Social Web Working Group whose goals include creating a Web protocol
for ``federating social information such as status updates,\textquotedblright{}
explicitly to ``facilitate access to social communication on the
Web.\textquotedblright{} The working group's charter includes in its
use cases user control over personal data and cross-organization ad-hoc
federation.\footnote{Social Web Working Group charter: \url{u.fsf.org/287}}
Unlike other efforts by the W3C, it's nice to see the Social Web Working
Group engaged in some freedom-respecting goals.\footnote{\url{u.fsf.org/252}}

Now that you understand a bit more about how federated social networks
behave, and why they're good for your freedom, why not try one? Visit
a diaspora pod for a general social network, a GNU social or Mastodon
instance for microblogging, or a GNU MediaGoblin instance for sharing
media like video and images.\footnote{Diaspora: \url{podupti.me}, MediaGoblin: \url{u.fsf.org/288}}\textsuperscript{}\ender

\section{What not to miss from LibrePlanet}

\myauthor{Various LibrePlanet Attendees}{}

\cap{T}he 2017 LibrePlanet team put a lot of effort into creating
a diverse, interesting, balanced schedule full of talks we really
wanted to see. During the event itself, however, we found ourselves
lacking the time necessary to sit through a whole session. We reached
out to a few attendees for recommendations.

\textbf{Understanding the complexity of copyleft defense} by Bradley
Kuhn\footnote{\url{u.fsf.org/27w}}

I liked Bradley Kuhn's talk. I thought he made some really important
points about the place the legal system has in the fight for software
freedom. He made a convincing argument I now subscribe to.

\textemdash Carol Smith

\textbf{The set of programmers: How math restricts us} by Carol Smith\footnote{\url{u.fsf.org/27x}}

I found this to be a really thoughtful and engaging overview of a
topic I hadn't thought very much about. I wish every technical recruiter,
hiring lead, and/or admissions committee would watch it.

\textemdash Shauna Gordon-McKeon

\textbf{Freedom and loathing on the campaign trail '16}
 by Remy DeCausemaker\footnote{\url{u.fsf.org/27y}}

This is a super interesting look into the technology of a presidential
political campaign, and the opportunities for free software and open
community values to fit into that.

\textemdash Shauna Gordon-McKeon

\textbf{The Lisp machine and GNU} by Christopher Webber\footnote{\url{u.fsf.org/27z}}

I really liked Christopher Webber's talk about Lisp machines! I thought
it was a really informative history lesson about this sort of alternate
reality of what our desktops could have become\textemdash with a lot
of good research and guest star Gerald Sussman! Plus he gave it entirely
in Emacs.

\textemdash Noah Swartz

\textbf{Rock and roll bands and free software: A comparative analysis}
by Pamela Chestek\footnote{\url{u.fsf.org/27-}}

Pam Chestek's talk had stories, music and legal drama! So great! Bands
and free software projects aren't so different. We have so much to
learn from other people who started out doing something for love but
one day found themselves doing it (at least partially) for money.
Plan for success and register your trademarks!

\textemdash Deborah Nicholson

\textbf{Meet them where they are: Free software and social justice
today} by Brett Smith\footnote{\url{u.fsf.org/280}}

I loved Brett's talk on what we're really asking users to do when
we recommend free software. Software supply chains are hard but important.
Security and software freedom should be synonymous, but when they
aren't? Our community has work to do.

\textemdash Deborah Nicholson

\textbf{A fully-free cell phone experience, no baseband required}
 by Denver Gingerich\footnote{\url{u.fsf.org/281}}

I like Denver's talk about making the entire cell phone experience
as free as possible. The whole project is actually more accessible
than I thought. It's still at a ``hackers only\textquotedblright{}
stage, for sure, but it's easier to get started than I realized,
and maybe even more importantly, he showed a lot of incremental steps
you can take to get more free software on your cell phone without
completely writing off today's networks.

\textemdash Brett Smith

\textbf{Running a TV channel with free software} by Zeeshan Hasan\footnote{\url{u.fsf.org/282}}

TV is not dead as some of us would like to believe. It is alive and
aggregated to a point of absurdity. The monopolistic entities in control
now must be challenged and thwarted by independent sources for news
and information. Free TV projects are necessary for people to have
control over freedom of information and autonomy as we are ruled by
the information we receive. Zeeshan shows one important way that we
can turn that around.

\textemdash Micky Metts

\textbf{Free software \& the law: A lighthearted trip down memory
lane} by Robinson Tryon\footnote{\url{u.fsf.org/283}}

Robinson has put into words the obvious elephant in the room. How
could we spend hours, years and decades writing code and never paying
heed to the laws that bind us? The free software community is fortunate
to have such forward-looking people focused on the laws surrounding
software use and licensing. Most people never read the license of
a product or service they use. This session should inspire more people
to become lawyers for good.

\textemdash Micky Metts

We would like to thank Brett, Carol, Deb, Micky, Noah, and Shauna
for sharing their LibrePlanet recommendations with us. There are dozens
of other great presentations, including keynotes by Kade Crockford,
Richard M. Stallman, Cory Doctorow, and Sumana Harihareswara, all
of which are available at \url{media.libreplanet.org}.

\textit{Edits made for grammar and clarity.} \ender

\section{FSF ongoing\\infrastructure upgrades}

\myauthor{Andrew Engelbrecht}{Web Developer}

\cap{O}ver the last eight months, the FSF tech team has been upgrading
our physical infrastructure and software to more effectively serve
the free software community and help others do so as well.

Thanks to a generous \$40,000 donation, we are migrating to
Librebooted KGPE-D16 motherboards with 32 cores per board and are
adding 4-channel, 10 GBit Ethernet to speed up our new Ceph
(distributed storage) systems.\footnote{An RYF certified version of
  these motherboards is available from \url{vikings.net}} We are also
migrating to libvirt, which offers an awesome interface to the KVM
features in the kernel Linux. Senior systems administrator Ruben
Rodriguez made a cool hack that lets us boot MBR-free filesystems with
a custom reusable GRUB image, a method inspired by the Xen
paravirtualization system.

Our new infrastructure will propel development within and beyond GNU
by increasing the much-needed storage space of the GNU Savannah software
collaboration system, which hosts over three thousand GNU and non-GNU
projects; and by massively boosting Savannah's core count, which will
improve the performance of interactions with high-demand source code
repositories. We will also migrate many of our virtual machines\textemdash including
\url{libreplanet.org}, the Free Software Directory, and our CiviCRM
+ SQL instance\textemdash to this new infrastructure for improved
performance, fault-tolerant, high speed data storage, and the ability
to perform live migrations of virtual machines.

We're also in the process of upgrading very old servers to Trisquel
7 and 8, which I hope will be officially released quite soon.

We updated our staff and member ejabberd (XMPP) servers, which facilitate
decentralized instant messaging, hardened SSL configurations, and
optional end-to-end encryption. We migrated our FSF staff StatusNet
server to GNU social, a decentralized short message system, which
interoperates with other GNU social servers and the popular Mastodon
platform. We updated MediaWiki, the software that powers Wikipedia,
on our \url{libreplanet.org} and \url{directory.fsf.org} sites.
We also upgraded our internal instance of Request Tracker, used by
FSF staff and many volunteers.

The FSF doesn't work alone; we receive much help from volunteers who
maintain the servers that comprise Savannah and other systems, such
as \url{gnu.org}. We also benefit greatly from the programmers,
documentation writers, packagers, and artists who work on GNU and
non-GNU, and whose generous efforts everyone is free to make use of.

An important part of the FSF's role in the world is to demonstrate
to other nonprofits our ability to run exclusively free software on
Trisquel-based, Librebooted, self-hosted systems. Although our technical
team is small, we are able to deploy and maintain a large array of
services that we happily use on a regular basis. We do this for greater
autonomy, full control over our systems, and to make great use of
the awesomeness that is free software. I hope that we inspire you
to do so as well. :-) \ender

\section{Mastodon interview}

\myauthor{John Hsieh}{Deputy Director}

\cap{T}his past April, the federated social network Mastodon exploded,
rapidly gaining hundreds of thousands of users across more than a
thousand instances of the platform. These instances are being run
independently across personal and public servers\textemdash a benefit
of a federated social network.

Recently, the FSF had an opportunity to interview Eugen Rochko over
e-mail. To learn more about Mastodon, you can visit \url{mastodon.social}.

\textbf{Can you tell us a bit about yourself?} I am a recent graduate
from Friedrich-Schiller-UniversitÃ€t Jena, where I studied computer
science. I am German, of Jewish/Russian origin.

\textbf{What inspired you to create Mastodon?} I was disappointed with
Twitter, and have a love for free software.

\textbf{Can you tell us a bit about the technical side of Mastodon?}
It's made with Ruby and JavaScript. It uses Ruby on Rails as a
framework, and React.js as well.

\textbf{Who contributes and how are they organized?} Officially, the
Mastodon team is just me (main developer, founder) and
\url{@maloki@mastodon.social} (project manager). Everyone else is on a
volunteer basis\textemdash according to GitHub there are 323 different
contributors as of 5/13/2017.\footnote{Mastodon has 3,031 commits by
  335 contributors on GitHub (5/24/2017). The Patreon is supported by
  727 individuals.} There are only about a dozen regular contributors;
most of them have been given write access to the repository, which
allows them to authoritatively review pull requests. But only I and
one other person can merge into the master branch.\footnote{Write
  access grants contributors a number of permissions, including the
  creation of repositories, the ability to review pull requests, and
  manage various reported issues, project boards, and team repos.}

\textbf{How/why did you choose the GNU Affero General Public License
  version 3 for Mastodon?} Originally I started with the GPL, because
I was familiar with it from other projects like Discourse, a free
online discussion platform that can be used as a mailing list, online
forums, or chat rooms. It was suggested that I change to the AGPLv3 to
prevent the XMPP/gTalk/WhatsApp situation, and I found that point
compelling. To preserve federation, AGPLv3 was chosen.\footnote{To
  read more on licensing and federation: \url{u.fsf.org/27u}}

\textbf{How does Mastodon relate to GNU social?} Mastodon is an
OStatus application, just like GNU social.\footnote{OStatus is a
  standard for distributed status updates and includes a number of
  protocols. Microblogging applications using the same protocol are
  able to talk with one another across instances and even specific
  software.} They are both part of the same network
(``fediverse\textquotedblright ) based on this protocol.

\textbf{What kinds of technical and/or social challenges did you
  experience during development?} Technical challenges have included a
rush for large-scale optimization during the activity explosion and
pinpointing bugs in a distributed networking
environment.\footnote{Following the early-April publication of several
  articles on Mastodon, user numbers went from 20,000 to 42,000 over
  two days.} We have also been adjusting to people's expectations of
how things should work.

\textbf{How many Mastodon users are there today?} Today Mastodon has
over 620,000 users on over 1,200 instances. These numbers are
available on \url{instances.mastodon.xyz/list}. I do not track any
other specific stats, but any time I look there are about 6,000 users
accessing \url{mastodon.social} at the same time (this includes
websockets connections of online users).

\ 

We'd like to thank Eugen for taking the time to do the interview,
as well as thank the entire Mastodon team for their efforts. If you
have suggestions for future interview candidates, email \url{campaigns@fsf.org}.

\textit{Responses edited for content and clarity.}\ender

\begin{minipage}[t][1\totalheight][c]{0.8\columnwidth}%
\begin{shaded}%
\begin{center}
\textbf{\large{}{}Get 10\% off!}{\large{} }
\par\end{center}{\large \par}
\begin{center}
\rule[0.5ex]{0.9\columnwidth}{0.5pt} 
\par\end{center}
\begin{center}
\textbf{Support the Free Software Foundation by purchasing GNU Press
merchandise. } 
\par\end{center}
\begin{onehalfspace}
\begin{center}
\textbf{Visit \url{shop.fsf.org}! Enter discount code} SPRING2017. 
\par\end{center}
\end{onehalfspace}
\end{shaded}%
\end{minipage}

\section{On the road with RMS}

\myauthor{Jeanne Rasata}{Assistant to the president}

\cap{R}ichard M. Stallman, president of the Free Software Foundation,
is known around the world as RMS, the founder of the free software
movement. He continues to travel, speaking to diverse audiences. Here
is a little bit about what he's been up to between November 2016 -
May 2017. In the past six months, Richard has:

\begin{itemize}
\item visited 29 cities,
\item given 32 talks, and
\item participated in 1 panel.
\end{itemize}

\begin{figure}[H]
\includegraphics[width=1\columnwidth]{richard_11-5-2017}
\textbf{Where has RMS been?}
\end{figure}

Richard has been to schools, conferences, and organizations like UNESCO
across Canada, France, Germany, Iceland, Italy, Portugal, Spain, and
the United States.

Talks given include: 
\begin{itemize}
\item El software libre en la administraciÃ³n 
\item El software libre y tu libertad 
\item Free Software, Your Freedom, Your Privacy 
\item A Free Digital Society 
\item Le logiciel Libre, la conception libre du matÃ©riel 
\item Gouvernance et regulation de la securitÃ© numÃ©rique: Quel role pour
chacun? 
\item Free Software, Your Freedom and Medicine 
\end{itemize}
Please write to \url{rms-assist@fsf.org} with any photographs you
would like us to share on RMS's blog, at \url{fsf.org/blogs/rms};
with recordings of his speeches for our audio-video archive \url{audio-video.gnu.org};
or to extend a speaking invitation to RMS. See \url{u.fsf./org/zi}
for a list of his confirmed engagements.\ender

\clearpage{}\verbatimcopyright{2017} \donate{foo} 
\end{document}
