#111 Community Blog Editor Cleanup
Closed: Complete 4 years ago Opened 4 years ago by bex.

Problem: Community Blog articles are sometimes stuck waiting for review and posting. One identified challenge was a lack of editors.

Action Taken: On 23 May all editors were emailed by @bex and asked if they could continue to commit to reviewing and publishing at least one time per
week.

This ticket will track the results.

Administrator:
- bee2502: Responded to bex that she doesn't have time right now - is confirming her willingness to move to a contributor role
- bexelbie: is @bex and is willing to help with admin and editing
- chrisroberts
- decause
- jflory7
- mattdm: Happy to edit
- nb
- pfrields: needs admin access as backup since the system is similar to magazine
- puiterwijk: needs admin access for Fedora Infra
- ryanlerch
- tatica

Editor:
- bproffit: Available to edit after 12 June
- cprofitt
- jkurik: per email to bex doesn't need editing rights
- jzb: responded and debating
- nardasev: per email to bex doesn't have time to edit
- ralph: per email to bex didn't realize he had editing rights and doesn't need them


updated with information from ralph

updated with information from jzb, jkurik, bproffit, mattdm

Metadata Update from @jflory7:
- Issue assigned to bex
- Issue priority set to: critical (next week)
- Issue set to the milestone: Fedora 26 (to June 2017)
- Issue tagged with: community blog, internal operations

4 years ago

Editor guidelines

This morning, I created a new page on the Community Blog for editor guidelines. The information on this page tries to make the operating procedure that I've followed for the past year and a half more transparent. As far as currently active editors go, I've been managing the editing for the Community Blog solo since July 2016 – I haven't done an effective job at motivating and involving others into the process.

Community Blog editor guidelines

Longer analysis / retrospective

I posted a much more detailed analysis / retrospective on the CommOps mailing list. You can read the thread below.

Mailing list retrospective on Community Blog

updated with nardasev

Hello @bex ,@jflory7

I see some articles in Pending Review status (one in magazine and the other in community blog), do you think we need do some kind of friendly reminder to the editors?

If you need help with this or another task about this ticket, just ask :smile:

@bt0dotninja Yeah, I might have missed some of the pending review articles. If something has been sitting for a while, feel free to send a follow-up email to the author to see if they are interested in publishing or if they changed their mind. Most of the time, they just forget to ask for it to be reviewed on the mailing list. :sweat_smile:

Also, I'm thinking this ticket could be closed now? I think we have an active list of the editors now. If anyone responds later, we can always just update it as we go.

+1 to close, Follow-up mail sended :smiley:

@bt0dotninja Yeah, I might have missed some of the pending review articles. If something has been sitting for a while, feel free to send a follow-up email to the author to see if they are interested in publishing or if they changed their mind. Most of the time, they just forget to ask for it to be reviewed on the mailing list. 😅
Also, I'm thinking this ticket could be closed now? I think we have an active list of the editors now. If anyone responds later, we can always just update it as we go.

Should we put this active list of editors in wiki somewhere before closing.

I am willing to help with admin and editing. I help publish occassionally when jwf is not available.

Should we put this active list of editors in wiki somewhere before closing.

Thanks, not a bad idea, @amsharma. I added an Editors section to the CommBlog wiki page.

I am willing to help with admin and editing. I help publish occassionally when jwf is not available.

@nb It would be awesome to have your help with this! Now that the editor guidelines exist, it should hopefully be a little easier (although they do still need polish as Brian has suggested). You should already have permissions.

Closing ticket

Since we have a list of some editors who are interested in helping, this ticket's purpose should be fulfilled. However, it will still be helpful to polish the editor guidelines and try to work some of those guidelines into the writing guidelines, so it's less work on an editor.

Closing this ticket as complete…

Metadata Update from @jflory7:
- Issue close_status updated to: Complete
- Issue status updated to: Closed (was: Open)

4 years ago

Login to comment on this ticket.

Metadata