[release-notes/f17] Added copy of an email asking devel-announce for help with RNs. It is both a historical reference, a

[Pete Travis]

commit 4366d88daa9ebc6133fde806726bafce999ac014
Author: Pete Travis <immanetize at fedoraproject.org>
Date:   Mon Sep 17 18:27:42 2012 -0600

    Added copy of an email asking devel-announce for help with RNs.
    It is both a historical reference, and a reminder that it might
    be a good idea to send a similar email next time.

 DEVELOPER_APPEAL |   17 +++++++++++++++++
 1 files changed, 17 insertions(+), 0 deletions(-)
---
diff --git a/DEVELOPER_APPEAL b/DEVELOPER_APPEAL
new file mode 100644
index 0000000..db07b70
--- /dev/null
+++ b/DEVELOPER_APPEAL
@@ -0,0 +1,17 @@
+###
+# This is a message composed for the devel-announce mailing list for the F18 release cycle.
+# I'm committing it to the repo not necessarily to be reused, but as more as a reminder 
+# to open communications with the developers as we compose documentation for each release.
+###
+
+Greetings!
+
+	As the Fedora Documentation Project prepares the release notes for Fedora 18, we'd like to ask for your help.  Each Fedora release marks the inclusion of new features and the retirement of others, and with the help of the development community, we won't skip a beat. The Docs team would like you to assign us some homework.
+	The release notes are divided up into categories, or 'beats.' Each beat is kept by a volunteer who follows mailing lists, changelogs, announcements, and features in the space. Many beats also have a developer point of contact for technical questions and cooperation. We track these responsibilities with http://fedoraproject.org/wiki/Category:Documentation_beats , which includes links out to wiki pages for each individual beat.  As we reach the end of the release cycle, developers and docs maintainers populate these pages, then they are converted from wiki markup to Docbook XML and published. With a little help, we can put out release notes that can't be beat.
+	If you're working on something for Fedora, we'd like to make sure you get the credit you deserve. Leave us a quick note on a beats page, send it to our mailing list ( http://lists.fedoraproject.org/mailman/listinfo/docs ), or join us in #fedora-docs. You don't need to worry about language and composition or even spelling - just let us know what you've been working on that you'd like documented and we'll take it from there. 
+	We *really* don't want you to beat yourself up about presentation. A simple "make sure you mention this new feature" is enough. We're happy to do the research and compose the prose. Knowing where to start writing makes the process considerably more efficient, just as a brief note on hundreds of features from each developer is more effective than a handful of docs maintainers trying to follow all of hundreds of features. 
+	
+	Thanks for helping us represent your work to the users, 
+
+
+The Fedora Docs Team
\ No newline at end of file