16:35:32 #startmeeting Fedora CommOps (2017-05-23) 16:35:32 Meeting started Tue May 23 16:35:32 2017 UTC. The chair is bexelbie. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:35:32 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:35:32 The meeting name has been set to 'fedora_commops_(2017-05-23)' 16:35:39 #meetingname commops 16:35:39 The meeting name has been set to 'commops' 16:35:45 #nick commops 16:35:54 #topic Roll call 16:35:58 .hello bex 16:35:59 bexelbie: bex 'Brian (bex) Exelbierd' 16:36:10 .hello bt0dotninja 16:36:14 bt0: bt0dotninja 'Alberto Rodriguez Sanchez' 16:36:19 o/ 16:36:29 Anyone else joining us? 16:36:49 bt0, I'll move on to the topic we both came to discuss :) 16:36:59 #topic Publishing Process for the Community Blog 16:37:09 bt0, do you ahve editor access to the blog? 16:37:17 no, i dont 16:37:34 usually Justin do it 16:38:01 ok 16:38:19 so, looking at the backend, we have 2 posts pending review 16:38:21 and 9 posts in draft 16:38:27 3 on hold 16:39:09 of the two in draft, one seems to meet the requests made on https://communityblog.fedoraproject.org/writing-community-blog-article/ 16:39:45 the other is close, but needs some more context in the writing, a tag or two and a pic (we can probably use the stock pic) 16:39:50 a stock pic 16:40:00 bt0, do you think the guidelines at https://communityblog.fedoraproject.org/writing-community-blog-article/ are good ones? 16:40:32 * bexelbie thinks they are not too heavy and work but is open to discussion 16:41:27 they are quite simple 16:41:47 do you think they need modification? 16:42:57 No, they give us a basic pattern of quality, more complex rules could discourage writers 16:43:08 cool - I'll "agreed" that 16:43:18 #agreed the guidelines at https://communityblog.fedoraproject.org/writing-community-blog-article/ are in good shape and don't need modification 16:43:25 cool 16:43:29 as for the review process, what would you suggest? 16:43:39 hi 16:43:46 * bexelbie has ideas but would like to hear yours first, if possible 16:43:48 o/ nb 16:43:51 hi nb 16:43:57 we are discussing the publishing process for the commblog 16:46:11 anyone have suggestions? 16:47:13 Ok, what about this idea 16:47:29 umm, maybe additional than the final mail one ticket on pagure with tags #commblog, #review 16:48:11 I understand that - I wonder if we could keep the process more light weight. Having a ticket that gets opened just to get closed feels heavy when there is a list provided by Wordpress 16:48:27 I was thinking that if we defined editing more carefully to be lightweight 16:48:38 and verified that all of hte current editors are actually ... editing/publishing and if not adding new people 16:48:46 we could hopefully get to a place where we just got things rolling again 16:48:56 wdyt? 16:49:22 ok, I agree 16:51:01 How about this process: 1. Editors should review the article for content and make sure it is 1) appropriate and 2) understandable. The goal is not to produce a perfect post that is highly polished like the magazine, but is instead to convey the information our contributors need in a timely manner. 16:51:12 so, for example, all of the English doesn't have to be 100% perfect American English. 16:51:23 2. Editors should publish as soon as a review is complete. 16:51:44 no need to batch this as it isn't a targetted marketing effort, like magazine, it is our internal communications feed - akin to planet in many ways 16:51:47 wdyt? 16:53:26 simple, but the most important bottleneck is the editors, we need more active editors for the commblog 16:53:32 100% agreed 16:53:54 I am also going to suggest that we contact every editor we have today and find out how committed they are - based ont hat we can get more editors if needed 16:54:10 to keep the log easy to read though, does the above process sound good for editing? 16:54:24 this way we can summarize this out for feedback to the rest of commops via mail 16:54:31 yeah, sounds likea good plan 16:54:43 Cool 16:55:15 #agreed we suggest a simple editing process of "review the post as appropriate and understandable" and then "publish immediately" 16:55:46 I think we should send an email to everyone who has editing rights and ask them to either commit to visiting at least one day per week most weeks to check for pending review articles to to step back so we can get more editors in place. wdyt? 16:56:30 I think we should also ask infra who needs access as admins from their side so we don't accidentally remove those people 16:57:45 sounds good for me 16:58:10 cool 16:58:29 I'll take that action since I have the email addresses in the tool, ok? 16:59:14 ok 16:59:32 do you want to take the action to open an infra ticket and find out who on their team needs admin access for infra maintenance purposes? 16:59:34 #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. 17:00:39 Is there anything I can help with? 17:00:50 oh, i open the ticket 17:00:54 #action bt0 to open a ticket with infra and find out who needs access to the commblog for maintenance purposes 17:00:56 cool? 17:01:00 yes 17:01:05 sweet 17:01:19 I also think you and I should at least deal with the two articles in pending review as one is quite old 17:01:20 ok? 17:01:42 maybe even some in draft if they sent emails but didn't do the right settings 17:02:26 The first article is https://communityblog.fedoraproject.org/?p=3790&preview=1&_ppp=baee40543d 17:02:27 ok 17:03:49 I think it is ready to go 17:03:52 wdyt? 17:04:32 it looks great, i think it is ready 17:04:39 it doesn't have a feature image, what about using the first one with the bag? 17:06:13 yep, and match with the title 17:06:44 If I did it right, the preview should be updated 17:08:08 bt0, these tags? Community, Conference, Fedora Loves Python, pycon, 17:09:12 oh wow - ok the tag list is already there - ignroe me :) 17:09:19 :) 17:09:23 I am going to push the button 17:10:12 The button pushes quite slowly :P 17:10:46 The icon that spins while it works is quite boring to look at 17:12:51 hmm, it looks like I needed to fix the date 17:12:53 trying again 17:13:01 I wonder what timezone the blog thinks it isin 17:13:24 boom - published! 17:13:34 :P 17:13:38 awesome 17:14:07 hmm, do you think we should have done a "continue reading" like with the Heroes of Fedora article? 17:15:27 nah - I think it is fine 17:15:31 shall we do the next one? 17:15:36 a lot of numbers 17:15:41 yep 17:16:39 What's next? 17:16:42 https://communityblog.fedoraproject.org/?p=3805&preview=1&_ppp=1789cb60f7 17:17:05 #info published the PyCon Slovakia article 17:18:24 wdyt? 17:20:00 umm, maybe a human readable summary of the bug can help 17:20:48 agreed, it is confusing to me 17:21:02 I think it would be cool if we knew who participated, if possible too 17:21:15 and one list of the testers (for public thanks) 17:21:20 yes, agree 17:22:23 ok, I'll add some notes about that in the draft right quick - do you know if sumantro sent an email to the list annoucing this was ready? 17:22:26 i can ping sumantrom (email/irc) 17:22:42 let me check 17:23:28 yes, he does 17:24:56 mind replying to him/the list and letting him know we added some editing notes? I also set hte image and tags while I was there so he can review it. 17:25:34 ok 17:25:49 #info we let the test day article writer, sumantrom, know about some needed edits 17:27:18 hmm, do you see emails asking for any more reviews? 17:27:20 * bexelbie is looking 17:27:24 no more articles are set pending review 17:28:40 no, no more 17:29:53 I think we should email the people with drafts and ask them to work on finishing them or let us know they can be deleted or whatever ... wdyt? 17:31:07 a deadline? 17:32:41 I'd rather give a push than a deadline 17:33:22 like a choice, let us know if a) you need more time; b) this article is not going to be finished and we stop watching it; c) it is ready - you should follow the guidelines at XXX and let us know ont he list if you need help? 17:33:28 ok, better 17:34:45 sounds good for me 17:34:58 wanna help send emails? 17:35:04 I can get you a list of names and article titles? 17:35:51 yes 17:36:32 i can do it today :) 17:37:30 ok, getting list one sec 17:39:49 https://paste.fedoraproject.org/paste/Rhepk5DMEItQvnsUuR~QrF5M1UNdIGYhyRLivL9gydE= 17:39:53 does that work bt0? 17:40:18 unfortunately you may have to take some guesses on the names->fas ID 17:40:40 #action bt0 to email the current authors who have drafts or on hold articles and ask them what their status is 17:40:42 ok? 17:41:08 yeah, i see the list 17:41:28 Actually, I think one of them can be dealt with now 17:41:37 I think this one should just be trashed as it looks like a pure test 17:41:37 https://communityblog.fedoraproject.org/?p=3576&preview=1&_ppp=764378c4a0 17:41:42 wdyt? 17:42:50 delete? 17:43:14 trash - it will still be there, just sittting in the trash can 17:43:19 so it isn't in drafts 17:43:29 * bexelbie doesn't think fedoradevelopment is a real person 17:44:51 ok 17:45:16 .fas fedoradevelopment 17:45:17 bt0: fedoradevelopment '' 17:45:43 .fasinfo fedoradevelopment 17:45:44 bt0: User: fedoradevelopment, Name: None, email: fedora.development@live.jp, Creation: 2009-01-25, IRC Nick: None, Timezone: None, Locale: None, GPG key ID: None, Status: active 17:45:47 bt0: Approved Groups: cla_fedora cla_fpca cla_done 17:46:08 just the basic cla groups 17:46:32 actually, if they are a real person, let's email them then :) 17:46:34 sound good? 17:48:13 yeah 17:48:35 ok 17:48:39 so you'll send those emails 17:48:48 I can summarize the meeting and mail out the minutes 17:48:49 yes, today 17:48:52 I'll also email the editors 17:48:58 anything else we need to do today? 17:49:15 no really 17:49:29 if you want me to read your draft before you email, let me know 17:49:40 I'll ping you with mind shortly (email for the editors) 17:49:43 s/mind/mine/ 17:50:32 * bexelbie is going to end the meeting 17:51:07 ok, 17:51:32 i send you the mail draft for review 17:52:48 cool - expect email from me shortly too 17:52:52 bt0++ 17:52:53 bexelbie: Karma for bt0dotninja changed to 7 (for the f25 release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:52:55 thanks 17:52:59 #endmeeting