office-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Office-commits] r9681 - trunk/campaigns/gnubucks


From: sysadmin
Subject: [Office-commits] r9681 - trunk/campaigns/gnubucks
Date: Thu, 24 Sep 2009 15:05:37 -0400

Author: www-data
Date: Thu Sep 24 15:05:37 2009
New Revision: 9681

Log:
web commit by holmes

Modified:
   trunk/campaigns/gnubucks/bountyprogrampressrelease.mdwn

Modified: trunk/campaigns/gnubucks/bountyprogrampressrelease.mdwn
==============================================================================
--- trunk/campaigns/gnubucks/bountyprogrampressrelease.mdwn     Thu Sep 24 
14:55:32 2009        (r9680)
+++ trunk/campaigns/gnubucks/bountyprogrampressrelease.mdwn     Thu Sep 24 
15:05:37 2009        (r9681)
@@ -1,16 +1,23 @@
 ###Free Software Foundation announces new bounty program: offers awards for 
unearthing non-free code in free software
 
-BOSTON, Massachusetts, USA -- Thursday, September 24, 2009 -- The Free 
Software Foundation (FSF) today introduced a new program to reward those who 
find non-free code in free software operating system distributions.
+BOSTON, Massachusetts, USA -- Thursday, September 24, 2009 -- The Free 
Software Foundation (FSF) today introduced a new program to reward those who 
find non-free code in free software operating system distributions.  FSF has 
defined a list of guidelines covering what it means to be a free distribution, 
and it maintains a list of distributions which meet guidelines.  
 
-"This new awards program will help make sure that free distributions of 
GNU/Linux are really and truly free," said FSF executive director Peter Brown.
+"This new awards program will help make sure that the FSF-endorsed free 
distributions of GNU/Linux are really and truly free," said FSF executive 
director Peter Brown.
 
-In order to qualify for the "GNU Buck" award, someone first submits a 
detailed, actionable report about non-free code in a free distribution to both 
FSF and the maintainer of the distribution. If the maintainer confirms the 
report and removes the non-free part, the person will receive an award and, if 
desired, public recognition.
+"Ever since we published the guidelines for what we consider to be a free 
system distribution, we have been looking for practical ways to deal with the 
issue of nonfree software that is accidentally included in these 
distributions-- steps that are within our means and the means of distribution 
maintainers," said FSF licensing compliance engineer Brett Smith, "This new 
program does a good job of striking that balance."
 
-"***," said FSF licensing compliance engineer Brett Smith.
+Those qualifying for the award will receive a "GNU Buck" certificate, in the 
amount of Pi signed by Free Software Foundation president and "Chief Gnuisance" 
Richard Stallman.
+
+In order to qualify for the "GNU Buck" award, someone first submits a 
detailed, actionable report about non-free code in a free distribution to both 
FSF and the maintainer of the distribution. If the maintainer confirms the 
report and removes the non-free part, the person will receive an award and, if 
desired, public recognition.  When that happens, the FSF will also notify other 
free distros, through the gnu-linux-libre list, to make sure they can address 
the issue too. 
 
 The awards follow in the tradition of the checks written by legendary computer 
scientist Donald Knuth to anyone who found errors in his seminal textbook "The 
Art of Computer Programming."  To receive a check was such an honor that they 
were more often displayed on office walls than cashed. (Knuth stopped writing 
actual checks in 2008 due to check fraud.)
 
-Those qualifying for the award will receive a "GNU Buck" certificate, in the 
amount of [Pi], signed by Free Software Foundation president and "Chief 
Gnuisance" Richard Stallman.
+For more information on the FSF's criteria for classifying a distribution as 
free, see:
+<http://www.gnu.org/distros/free-system-distribution-guidelines.html>
+
+For the full list of FSF-endorsed distributions, see:
+<http://www.gnu.org/distros/free-distros.html>
+
 
 ### About the Free Software Foundation
 
@@ -47,70 +54,3 @@
 Free Software Foundation  
 +1 (617) 542 5942  
 address@hidden
-
-
-
-
-PRESS RELEASE ENDS!!!!!!!!
-
-
-## Extra info from Brett:
-
-* History?
-
-  If you mean for the GNU Buck specifically, I'm not sure there's
-  much.  The maintainer e-mail probably explains what there is well
-  enough, in colloquial terms.
-
-* Reference Knuth Check thing and the story of why it stopped?
-* Who qualifies? 
-* How do they qualify?
-
-  In order to qualify, someone has to submit a detailed, actionable
-  report about nonfree software to a specific distro, and send us a
-  copy as well.  The report should go directly into the distro's bug
-  tracker system or whatever -- we'll have a list of links that people
-  can use to submit a report for each distro we endorse.
-
-  If the distro maintainer confirms the report, and as a result
-  nonfree software is removed from the distro, they'll get the GNU
-  Buck, as well as public acknowledgment on our web page if they want
-  it.  At that point, we'll send the information around to other
-  distros so they can take action as well.
-
-  Probably the most important part to emphasize -- maybe not as much
-  in the press release, but in other materials -- is that this needs
-  to be a clear, detailed report.  Saying "such-and-such package is
-  nonfree" is not good enough.  It needs to point to specific files,
-  provide supplementary license information as appropriate, etc.
-
-  We have not discussed any restrictions on age, geography, etc.  I
-  don't know if we need any.  Do we need to check that with a lawyer?
-
-* What's the desired outcome?  (
-
-  Well... it depends on what you mean.  If I can hazard a guess about
-  the question I *think* you're asking, probably the point to make in
-  the press release is similar to the one I made in the e-mail to
-  distro maintainers: this is a *practical* measure (in the strongest
-  sense of that word) that we can take to help make sure that we're
-  promoting free software.
-
-  This isn't really a program where success can be tied to outcomes.
-  If we don't get any reports through the program, maybe it's because
-  the free distros have already done a great job of removing the
-  nonfree software -- which is an awesome place to be from our
-  perspective!
-
-* What are examples of people finding non-free code in free products?
-
-  There are a couple, but I'm not sure we want to call any attention
-  to them, usually because they have some attached baggage.  For
-  example, there was an incident where nonfree code from SGI was
-  discovered in xorg, but the information was floating around the
-  Internet for a while, so it's hard to identify one source.  There
-  was also a time when a Fedora maintainer brought our attention to
-  problems in afio (<http://spot.livejournal.com/303000.html>) -- but
-  he did that as part of criticizing our guidelines for free distros
-  and the way they go about dealing with these issues.
-




reply via email to

[Prev in Thread] Current Thread [Next in Thread]