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

[sysadmin]

Author: brett
Date: Wed Sep 23 17:31:48 2009
New Revision: 9670

Log:
add background info for Holmes

Modified:
   trunk/campaigns/gnubucks/bountyprogrampressrelease.mdwn

Modified: trunk/campaigns/gnubucks/bountyprogrampressrelease.mdwn
==============================================================================
--- trunk/campaigns/gnubucks/bountyprogrampressrelease.mdwn     Wed Sep 23 
16:13:20 2009        (r9669)
+++ trunk/campaigns/gnubucks/bountyprogrampressrelease.mdwn     Wed Sep 23 
17:31:48 2009        (r9670)
@@ -1,12 +1,63 @@
 ## Basic information I need:
 
 * 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.
+
 [If you're going to write a press release, be sure to follow
 [[our_style_guidelines|fsf-style-guide/]].  One particular point to
 keep in mind: don't capitalize people's titles in the body text.  So