#fedora-meeting: Fedora CommOps (2017-05-23)

Meeting summary

1. Roll call (bexelbie, 16:35:54)
   
2. Publishing Process for the Community Blog (bexelbie, 16:36:59)
   1. AGREED: the guidelines at https://communityblog.fedoraproject.org/writing-community-blog-article/ are in good shape and don't need modification (bexelbie, 16:43:18)
   2. AGREED: we suggest a simple editing process of "review the post as appropriate and understandable" and then "publish immediately" (bexelbie, 16:55:15)
   3. ACTION: bexelbie to email editors and ask if they can still commit to checking the pending review queue at least once per week most weeks after two weeks we can determine if we have enough editors or not. (bexelbie, 16:59:34)
   4. ACTION: bt0 to open a ticket with infra and find out who needs access to the commblog for maintenance purposes (bexelbie, 17:00:54)
   5. https://communityblog.fedoraproject.org/?p=3805&preview=1&_ppp=1789cb60f7 (bexelbie, 17:16:42)
   6. published the PyCon Slovakia article (bexelbie, 17:17:05)
   7. we let the test day article writer, sumantrom, know about some needed edits (bexelbie, 17:25:49)
   8. https://paste.fedoraproject.org/paste/Rhepk5DMEItQvnsUuR~QrF5M1UNdIGYhyRLivL9gydE= (bexelbie, 17:39:49)
   9. ACTION: bt0 to email the current authors who have drafts or on hold articles and ask them what their status is (bexelbie, 17:40:40)
   10. https://communityblog.fedoraproject.org/?p=3576&preview=1&_ppp=764378c4a0 (bexelbie, 17:41:37)

Action items

1. bexelbie to email editors and ask if they can still commit to checking the pending review queue at least once per week most weeks after two weeks we can determine if we have enough editors or not.
2. bt0 to open a ticket with infra and find out who needs access to the commblog for maintenance purposes
3. bt0 to email the current authors who have drafts or on hold articles and ask them what their status is

Action items, by person

1. bexelbie
   1. bexelbie to email editors and ask if they can still commit to checking the pending review queue at least once per week most weeks after two weeks we can determine if we have enough editors or not.
2. bt0
   1. bt0 to open a ticket with infra and find out who needs access to the commblog for maintenance purposes
   2. bt0 to email the current authors who have drafts or on hold articles and ask them what their status is

People present (lines said)

1. bexelbie (117)
2. bt0 (49)
3. zodbot (10)
4. nb (1)
5. commops (0)