I have removed the "closed" templates from all the beats and reset the beats table at https://fedoraproject.org/wiki/Category:Documentation_beats
If you would like to help on a beat, please add your name to the "Writer" column. Even if someone is already on a beat I'm sure they wouldn't mind some help, but if a beat is an orphan, please consider standing up and taking the beat.
If you are relatively new to Docs, this is a great way to get involved. In some cases, taking the beat is nothing more than wordsmithing some text from the feature pages. If some research is needed, it is a great way to start to find your way around the Fedora Project. There are plenty of opportunities, and many hands make light work.
I have placed an asterisk next to the name of any beat writer I haven't heard from this cycle. If your name is in the table and you are willing to help for Fedora 14, please remove the asterisk next to your name. If your situation prevents you from helping this release, then please email me and let me know so I can recruit another writer.
I have also made an annotated copy of the Release Notes schedule with additional comments on places where the short description on John's schedule might not have been clear. The dates are from his schedule, however some milestones etc. that we don't specifically do something for have been omitted. To see these look at John's schedule at http://poelstra.fedorapeople.org/schedules/f-14/. Also, his "docs-and-trans-tasks" schedule which combines the L10N tasks with ours can be very helpful.
The schedule linked to from the beats page is for Release Notes only, and does not contain the Guides tasks.
--McD
On Sun, Jul 25, 2010 at 04:31:17PM -0400, John J. McDonough wrote:
I have removed the "closed" templates from all the beats and reset the beats table at https://fedoraproject.org/wiki/Category:Documentation_beats
If you would like to help on a beat, please add your name to the "Writer" column. Even if someone is already on a beat I'm sure they wouldn't mind some help, but if a beat is an orphan, please consider standing up and taking the beat.
If you are relatively new to Docs, this is a great way to get involved. In some cases, taking the beat is nothing more than wordsmithing some text from the feature pages. If some research is needed, it is a great way to start to find your way around the Fedora Project. There are plenty of opportunities, and many hands make light work.
I have placed an asterisk next to the name of any beat writer I haven't heard from this cycle. If your name is in the table and you are willing to help for Fedora 14, please remove the asterisk next to your name. If your situation prevents you from helping this release, then please email me and let me know so I can recruit another writer.
I have also made an annotated copy of the Release Notes schedule with additional comments on places where the short description on John's schedule might not have been clear. The dates are from his schedule, however some milestones etc. that we don't specifically do something for have been omitted. To see these look at John's schedule at http://poelstra.fedorapeople.org/schedules/f-14/. Also, his "docs-and-trans-tasks" schedule which combines the L10N tasks with ours can be very helpful.
The schedule linked to from the beats page is for Release Notes only, and does not contain the Guides tasks.
John, are you planning a similar announcement for the devel-announce list?
On Tue, 2010-07-27 at 11:19 -0400, Paul W. Frields wrote:
On Sun, Jul 25, 2010 at 04:31:17PM -0400, John J. McDonough wrote:
I have removed the "closed" templates from all the beats and reset the beats table at
(clip)
John, are you planning a similar announcement for the devel-announce list?
Paul
Step 2 is to email previous beat writers directly. This will pick up those few folks who earlier took beats but aren't on the docs list, and perhaps light a fire under those who just haven't found one of them round tuit thingies.
Step 3 is to recruit new beat writers, through a posting to devel, but also perhaps a few direct emails to candidates I identify by studying review requests. Yeah, sneaky, I know, but it seems like someone who has been pushing a lot of, say, Sci/Tech packages might be interested in bragging on them. (Although we have a physicist already in our midst who might have an interest in that specific task!)
The dev posting has to have quite a different flavor. Here we are mostly trying to incent folks relatively new to the project to roll up their sleeves. In dev I suspect we are mostly trying to talk contributors, perhaps quite experienced contributors, into bragging about their work. That comes about the same time we are reminding the developers that we are getting the alpha one-page ready and they might want to put a little shine on their feature pages.
--McD
On Tue, Jul 27, 2010 at 1:15 PM, John J. McDonough wb8rcr@arrl.net wrote:
On Tue, 2010-07-27 at 11:19 -0400, Paul W. Frields wrote:
On Sun, Jul 25, 2010 at 04:31:17PM -0400, John J. McDonough wrote:
I have removed the "closed" templates from all the beats and reset the beats table at
(clip)
John, are you planning a similar announcement for the devel-announce list?
Paul
Step 2 is to email previous beat writers directly. This will pick up those few folks who earlier took beats but aren't on the docs list, and perhaps light a fire under those who just haven't found one of them round tuit thingies.
Step 3 is to recruit new beat writers, through a posting to devel, but also perhaps a few direct emails to candidates I identify by studying review requests. Yeah, sneaky, I know, but it seems like someone who has been pushing a lot of, say, Sci/Tech packages might be interested in bragging on them. (Although we have a physicist already in our midst who might have an interest in that specific task!)
The dev posting has to have quite a different flavor. Here we are mostly trying to incent folks relatively new to the project to roll up their sleeves. In dev I suspect we are mostly trying to talk contributors, perhaps quite experienced contributors, into bragging about their work. That comes about the same time we are reminding the developers that we are getting the alpha one-page ready and they might want to put a little shine on their feature pages.
Brilliant summary, John -- thank you for taking the time to write it! And thanks for the reminder -- I confess I don't track this work as often as I used to when I was really sleeves-up all the time in the Docs team. You answered all the questions lurking in my noggin, thanks.
Paul
docs@lists.stg.fedoraproject.org
-
John J. McDonough -
Paul W. Frields