CommBlog Publishing Process Suggestions and Meeting Minutes from 23 May 2017

[Brian Exelbierd]

We had a CommOps meeting today and focused on the Community Blog editing
process.  I am not sure if it is just bad timing or what, but we only
had 2 people active in the meeting.  Therefore it is important that
folks respond to the issues raised here on the mailing list as we didn't
have quorum to take any actions.

Suggestion: The writing process as described on
https://communityblog.fedoraproject.org/writing-community-blog-article/
seems good.  Writers should be encouraged to use this process.

Suggestion: Editing should be defined as checking that the post is
appropriate for the commblog and is understandable.  The goal is not to
publish every article in perfect American English but instead to make su
re we are getting information out to contributors in a quick and
understandable manner.

Suggesting: Publishing should be done as soon as a post is ready.  There
is not a need to time articles on the commblog as it is a contributor
focused feed without a direct marketing initiative goal.  We would r
ather get information to our contributors faster via the RSS feeds, etc.
than hold articles longer than needed.

Action Items:
- bt0 to email all authors with draft or on hold articles to find out
what their status is
- bexelbie to email all editors and find out if they have time to edit
so we can figure out if we need more people
- bt0 to open a ticket with infra to find out who on their team must
have access for administrative reasons so we don't accidentally remove
them

Note: In the meeting today the article from PyCon Slovakia was
published.

Minutes:
https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/commops.2017-...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/commops.2017-...
Log:
https://meetbot.fedoraproject.org/fedora-meeting/2017-05-23/commops.2017-...