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

[sysadmin]

Author: brett
Date: Wed Sep 30 16:27:15 2009
New Revision: 9860

Log:
additional bits suggested by John, plus minor cleanups

Modified:
   trunk/campaigns/gnubucks/eligibility-criteria.mdwn

Modified: trunk/campaigns/gnubucks/eligibility-criteria.mdwn
==============================================================================
--- trunk/campaigns/gnubucks/eligibility-criteria.mdwn  Wed Sep 30 16:10:41 
2009        (r9859)
+++ trunk/campaigns/gnubucks/eligibility-criteria.mdwn  Wed Sep 30 16:27:15 
2009        (r9860)
@@ -1,14 +1,28 @@
-### Short Version ###
+## Reporting Bugs For GNU Bucks ##
 
-In order to be recognized by our GNU Bucks program, you need to file a
-detailed and actionable bug report about software that does not meet
-[our guidelines][fsdg] with one of our [endorsed
-distributions](#distros), and send us a copy at <address@hidden>.
-You will receive recognition after the maintainer has confirmed that
-the bug is valid.
+Thanks for using a free system distribution!  If you've found
+materials in the distribution&mdash;like software, documentation,
+fonts, or even graphics or music&mdash;that don't meet [our guidelines
+for free distributions][fsdg], we'd really appreciate it if you could
+report it.  That way, we can help ensure that these distributions are
+always free for everyone to share.  It's a great way to contribute to
+the free software community that has brought all this together.
+
+This page provides instructions for how you can report this bug and be
+credited by our [GNU Bucks program][].
 
+[GNU Bucks program]: gnu-bucks-main-page-FIXME.html
 [fsdg]: /distros/free-system-distribution-guidelines.html
 
+### Short Version ###
+
+In order to be recognized by our GNU Bucks program, you need to file a
+detailed and actionable bug report with one of our [endorsed
+distributions](#distros) about materials that do not meet [our
+guidelines][fsdg], and send us a copy at <address@hidden>.  You will
+receive recognition after the maintainer has confirmed that the bug is
+valid.
+
 ### Long Version ###
 
 To help make sure everyone's on the same page, here's a little more
@@ -51,7 +65,7 @@
   <address@hidden>.  If you are filing the report in a bug-tracking
   system, please send along a link to that report when it's done.
   This enables us to keep track of when people should be recognized,
-  and spread information about valid reports to other endorsed
+  and share information about valid reports with other endorsed
   distributions.  See below for information about where to report bugs
   for each distribution.
 
@@ -60,7 +74,7 @@
 Below is a list of where you can report bugs for all of the
 distributions we endorse.  Web addresses point to bug trackers or
 forums you can use.  After you file the bug, please send a link to it
-to <address@hidden>.  If an e-mail address is provided instead, you
+to <address@hidden>.  If an email address is provided instead, you
 can send your report there directly, and CC: <address@hidden>.
 
 * **BLAG**: 
@@ -72,3 +86,16 @@
 * **Trisquel**: <http://trisquel.info/en/project/issues>
 * **Ututo**: 
 * **Venenux**: 
+
+### Thanks! ###
+
+While we do listen to feedback from distribution maintainers to
+determine what reports are eligible for recognition, ultimately the
+decision about who receives a GNU Buck rests with the FSF.  If you
+have questions about the program in general, or about the eligibility
+of a particular bug, please write to us at <address@hidden>.
+
+Thanks again for taking the time to submit this report.  We understand
+the amount of effort that goes into it&mdash;it's a valuable
+contribution to free software, and we're grateful to those who offer
+it.