#124 Create an editor's checklist
Closed: Complete 2 years ago Opened 3 years ago by jflory7.

Summary

Editing for the Community Blog is supposed to be easy, but the editor guidelines are long, wordy, and confusing. A quick-and-easy checklist should be created in addition to the full guidelines.

Background

Anyone who runs a publication of any kind knows how things become untidy and unorganized if not maintained correctly. For a long time, there was only one or two editors on the CommBlog. Because of this, it was mostly personal notes for how to process new posts.

We made progress with the editor guidelines, but it's still hard to attract new people to help. The guidelines are intimidating and make the work look harder than it is. On the reverse side, when someone outside of the regular editors publishes a post, it can be easy to miss a step in the guidelines because they're so lengthy.

Details

A quick and easy checklist improves the ease of editing and gives a quick reference for anyone to check off for reviewing a new post. This helps current and new editors to review posts and help get them out the door.

The goal is to make the average time spent editing per article be 10 minutes or less.

Action

We need to…

  1. Review editor guidelines, convert lengthy sections to short, actionable items
  2. Create new page in Community Blog with checklist
  3. Cross-link the checklist on the guidelines page

Metadata Update from @jflory7:
- Issue assigned to jflory7
- Issue marked as blocking: #119
- Issue priority set to: minor (3-4 weeks)
- Issue set to the milestone: Fedora 28 (to May 2018)
- Issue tagged with: Community Blog, internal operations, onboarding

3 years ago

Huge +1. I dread editing a bit because it is a word soup to get through.

Can we please also put hte editing checking list and the writing checklist on the same page? This way writers who can, can predo some of hte editing work.

I also believe we should specifically encourage, but not require that writers do things like topics, etc. to save editor time.

Metadata Update from @jflory7:
- Issue unmarked as blocking: #119

3 years ago

Metadata Update from @jflory7:
- Issue priority set to: no deadline (was: minor (3-4 weeks))

3 years ago

Metadata Update from @jflory7:
- Issue untagged with: onboarding

3 years ago

Metadata Update from @jflory7:
- Issue set to the milestone: Fedora 29 (to Oct. 2018) (was: Fedora 28 (to May 2018))

3 years ago

Metadata Update from @jflory7:
- Issue tagged with: help wanted

2 years ago

Metadata Update from @jflory7:
- Assignee reset

2 years ago

Metadata Update from @jflory7:
- Issue tagged with: team - commops

2 years ago

Metadata Update from @jflory7:
- Issue priority set to: needs review (was: waiting on external)
- Issue set to the milestone: Future releases (was: Fedora 29 (to Oct. 2018))

2 years ago

Metadata Update from @bcotton:
- Issue assigned to bcotton

2 years ago

Here's a draft of a combined writer/editor checklist:
https://fedoraproject.org/wiki/User:Bcotton/CommBlogGuidelines

I envision keeping the existing "Write an Article" page with the style content removed. This keeps the process and the requirements separate.

Metadata Update from @jflory7:
- Issue untagged with: help wanted
- Issue priority set to: waiting on assignee (was: needs review)
- Issue set to the milestone: Fedora 29 (to Oct. 2018) (was: Future releases)

2 years ago

@bcotton said…
Here's a draft of a combined writer/editor checklist:
https://fedoraproject.org/wiki/User:Bcotton/CommBlogGuidelines

These are amazing. I'm so happy to see this draft. I made an edit with some nitpicks, but otherwise, I would be delighted to see these go live. :tada:

Let us know if we can do anything to help you. I am +1 to seeing this replacing the existing guidelines whenever possible.

Perhaps @bex could review since he has used these guidelines as an editor and would probably be impacted by them. Maybe @nb and @sumantrom too.

Your edits look good to me @jflory7. I'll give this until the end of the week and move forward if there are no objections.

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

2 years ago

Login to comment on this ticket.

Metadata