12:01:13 #startmeeting Magazine editorial board 12:01:13 Meeting started Wed Sep 25 12:01:13 2019 UTC. 12:01:13 This meeting is logged and archived in a public location. 12:01:13 The chair is asamalik. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:01:13 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:01:13 The meeting name has been set to 'magazine_editorial_board' 12:01:13 #meetingname magazine 12:01:13 The meeting name has been set to 'magazine' 12:01:13 #topic Roll call 12:01:13 #chair stickster ryanlerch cverna asamalik sub_pop gregbartholomew bcotton misc 12:01:13 Current chairs: asamalik bcotton cverna gregbartholomew misc ryanlerch stickster sub_pop 12:01:25 .hello pfrields 12:01:27 stickster: pfrields 'Paul W. Frields' 12:01:30 .hello2 12:01:31 asamalik: asamalik 'Adam Samalik' 12:01:40 .hello2 12:01:42 cverna: cverna 'Clement Verna' 12:02:00 .hello2 12:02:01 bcotton: bcotton 'Ben Cotton' 12:02:11 .hello2 12:02:12 suanand: suanand 'Sundeep Anand' 12:03:25 \o/ good attendance today! hi everyone 12:03:34 #topic Agenda 12:03:40 #info Fedora Magazine has moved to a new Editorial Workflow 12:03:40 #link https://docs.fedoraproject.org/en-US/fedora-magazine/workflow/ 12:03:40 #info Following is the meeting agenda that is a slightly different than before: 12:03:40 #info -- 1/ Last week's stats -- 12:03:40 #info -- 2/ In progress followup -- 12:03:41 #info -- 3/ Finished articles to review -- 12:03:41 #info -- 4/ Articles to edit -- 12:03:42 #info -- 5/ Publishing schedule -- 12:03:42 #info -- 6/ Article proposals to clarify / approve -- 12:03:43 #info -- 7/ Open floor -- 12:03:50 :-) 12:04:09 I love the new workflow docs. They're great. +1 on agenda 12:04:33 #info For any future chairs, the agenda is drafted here for reference: https://docs.fedoraproject.org/en-US/fedora-magazine/editorial-meetings/ 12:04:37 cool! 12:04:43 #topic 1/ Last week's stats 12:05:12 #info Week of September 16: 73.5K pageviews -- going up! 12:05:33 Yeah, the Beta announcement surely helped here. 12:05:49 yep! 12:06:12 * bcotton bets this week does pretty well too 12:06:27 One note here... If anyone has Reddit or Ycombinator/HackerNews accounts, it would be really helpful if you could help socialize articles as well. 12:06:42 I try to stay on top of Facebook and Twitter for each post 12:07:12 yeah I do have a Reddit account, although I haven't used it much, but I can sure try! 12:07:13 I try to put them on HackerNews when I think about it 12:07:21 cverna++ 12:07:33 * asamalik made a note 12:07:37 #topic 2/ In progress followup 12:07:44 #info Looking at the 'in progress' column, is there something that's been finished? Anything to follow up on with its author? 12:07:44 #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban 12:08:23 #info -- #20 Getting set up with Fedora Project services on Fedora 31 -- 12:08:24 * stickster looks 12:08:28 #link https://teams.fedoraproject.org/project/asamalik-fedora-magazine/us/20?kanban-status=196 12:09:01 I'd say this one is good to go next, we can edit and make an image, and wait with publishing whenever we need to 12:09:15 *good to go to the next stage 12:09:26 +1 to bcotton title change suggestion 12:09:33 yep +1 to that 12:09:33 sgallagh: ^ We can change the card title accordingly 12:10:09 my hacktoberfest article is still in progress. i'm finalizing project collection and i'll try to have a draft done by EOW so we can publish it next week 12:10:17 stickster: Be my guest 12:10:32 I just reused the title image from the earlier version 12:10:36 done 12:10:46 stickster++ 12:10:51 and I've moved it 12:10:57 #info -- #29 How to contribute to Fedora -- 12:11:03 #link https://teams.fedoraproject.org/project/asamalik-fedora-magazine/us/29?kanban-status=196 12:11:10 I think we can just move this one forward! 12:11:50 bcotton: thanks for the update! 12:12:08 +1 12:12:40 and that's all here 12:13:02 #topic 3/ Finished articles to review 12:13:02 +1 too 12:13:09 #info Looking at the 'review' column, let's decide which articles are good to go. Move each either to the 'to edit' (finished) or to the 'in progress' (needs more work) and provide feedback. 12:13:09 #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban 12:13:42 #info asamalik has screwed this up and already went through those article in the previous step :) 12:13:54 :-) 12:13:56 asamalik++ for efficiency 12:14:01 lol 12:14:17 and I have posted comment to bcotton's article in the board 12:14:23 so let's just go next :D 12:14:31 #topic 4/ Articles to edit 12:14:40 #info Looking at the 'to edit' column, assign an editor and a cover image creator. 12:14:40 #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban 12:15:19 #info -- #20 Getting set up with Fedora Project services on Fedora 31 -- 12:15:21 #link https://teams.fedoraproject.org/project/asamalik-fedora-magazine/us/20?kanban-status=196 12:15:22 I love this 12:15:39 so image is already done, I can edit! 12:15:45 #action asamalik to edit #20 12:15:47 Neato :-) 12:16:09 #info -- #29 How to contribute to Fedora -- 12:16:14 #link https://teams.fedoraproject.org/project/asamalik-fedora-magazine/us/29?kanban-status=196 12:16:33 any volunteers for an image? 12:16:42 and editing? :) 12:16:57 I can do both 12:17:03 stickster++ 12:17:11 #action stickster do image and edit US #29 on how to contribute 12:17:14 #action stickster to edit and make an image for #29 12:17:17 twice 12:17:21 #undo 12:17:21 Removing item from minutes: ACTION by asamalik at 12:17:14 : stickster to edit and make an image for #29 12:17:25 oops 12:18:02 #info #28 Hacktoberfest 12:18:10 #link https://teams.fedoraproject.org/project/asamalik-fedora-magazine/us/28 12:18:33 this one is in progress, but since it's going to be done by EOW, let's do this one as well 12:18:46 asamalik: When a card moves to "to edit," does it get reassigned to the editor? 12:19:02 stickster: that's a good question, we should probably do that, yeah 12:19:35 if we want, i can try to ask the Digital Ocean folks if we can modify their official branding for the header. but if we'd rather do something that doesn't involve cross-mojination, i'm fine with that, too 12:19:46 stickster: we can even assign two people — for image and edit 12:19:58 this years logo is suh-weet https://hacktoberfest.digitalocean.com/ 12:20:11 Yup 12:20:16 that looks great! 12:20:26 stickster: thanks for fixing the assignees! 12:20:44 so am I reading it correctly that bcotton is making the image? :) 12:20:53 oh no 12:20:54 :-) 12:20:59 that sounds tragic for all involved 12:21:11 maybe it would attract attention 12:21:56 i'm going and forth on it. i certainly don't want to imply endorsement in either direction, but i do think it would be cool to have our image involve theirs, or at least have the same feel to it 12:23:08 bcotton++ 12:23:36 bcotton: so I'll assign you, and if your plan doesn't work you can always ask here for help with another image, that works? 12:23:46 * asamalik can edit! 12:23:53 so we want to see if we can use https://hacktoberfest.digitalocean.com/HF19_logo.png as-is? 12:24:06 #action asamalik edit #28 when ready 12:24:29 bcotton: even with the logos? 12:24:50 i don't feel like we can crop them out in good conscience 12:24:50 * asamalik might be missing something here btw 12:25:11 I would imagine if they met muster already for display there, they'll likely be OK for us to use too, but I agree to ask permission 12:25:16 asamalik: you're probably not. i just don't have fully-formed thoughts 12:25:37 I don't think we should put the Fedora logo around or near it in the image. 12:25:41 stickster: yeah, i'm just worried that they wouldn't want their logo used on third-party sites. but they can always say no 12:25:55 yeah, i'm not really sure how i'd modify it to fedora-ize it, tbh 12:26:00 That's definitely possible. One way to cut down on the uncertainty here is just don't bother. 12:26:43 yeah, i'm leaning towards don't bother 12:26:56 oh, hacktoberfest is their thing! right? that's what I was somehow missing 12:27:13 and let someone who can make pretty pictures make a pretty picture that incorporates some of the visual je ne sais quoi of the original 12:27:31 asamalik: yes. we're just driving people toward fedora-related projects so they can get a free t-shirt 12:27:49 * asamalik can absolutely put text over stock images, but for anything more than that I'd probably involve ryanlerch 12:27:59 bcotton: now I get it :) 12:28:10 it only took me a few weeks to realize that 12:28:18 sounds like ryanlerch is our winner, then :-) 12:28:36 he's not here, but let's try :P 12:28:46 all the more reason to assign it to him 12:29:09 * Southern_Gentlem wonders if the design teammay have an idea 12:29:30 #action ryanlerch to make a beautiful image for #28 (hacktoberfest), ideally somehow incorporating a design similar to this: https://hacktoberfest.digitalocean.com 12:31:19 Southern_Gentlem: Good point. Although I think ryanlerch is on the design team (right?) and we need this fast 12:32:03 he is. it's rather convenient 12:32:14 \o/ 12:32:16 #topic 5/ Publishing schedule 12:32:18 if we involve the design team we could also get design to use to promote the initiative on social media 12:32:24 not just via the magazine 12:32:29 #info Looking at the 'queued' and 'to edit' columns, decide the publishing schedule for the next week period. 12:32:29 #info If there is not enough content, we might also need to look at the 'in progress' or even the 'article spec' columns come up with additional content. 12:32:29 #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban 12:32:36 cverna: actually, that's a good idea 12:33:08 although the cover images we do are quite compatible with social media thanks to the template 12:34:28 so I propose: #29 (how to contribute) on Friday, #29 (hacktoberfest) on Monday, and some kind of improvisation on Wednesday 12:34:44 oops 12:34:48 * #28 (hacktoberfest) 12:35:02 #29 (how to contribute) on Friday, #28 (hacktoberfest) on Monday, and some kind of improvisation on Wednesday 12:35:11 asamalik's effectivity++ 12:35:14 how about we improve on monday? 12:35:19 improv, too 12:36:07 that works for me 12:36:12 This sounds reasonable to me, +1 12:36:19 1. i might not get it done in time to get review before monday AM and 2. hacktoberfest starts on tuesday (not a big deal either way, but at least if it publishes on wednesday i can just say "It's October" instead of "it's almost october") 12:36:37 but if we don't have anything ready to go, i'll just make sure i have it done enough by EOD thursday 12:38:07 fair enough! 12:38:28 sounds good to me 12:38:30 I'd ask on the list for something for Monday 12:39:02 will #20 be ready to go by Monday? 12:39:28 it might, although we wanted to wait for f31 GA 12:39:36 ah, okay, nevermind then 12:39:52 Ohh right. 12:39:57 So we need something for Monday? 12:40:06 #proposed #agreed PUBLISHING SCHEDULE: Friday 27 Sep, #29 how to contribute (asamalik:edit) -- Monday 30 Sep, asking on the list for something -- Wednesday 2 Oct, #28 Hacktoberfest (stickster:edit/stickster:image) 12:40:10 that's what we have so far 12:40:12 stickster: yep 12:40:33 +1, with the note that i'll make hacktoberfest happen if we can't find anything else 12:40:36 OK. I will probably put something in the hopper but will look for someone else to contribute. 12:40:44 +1 on schedule 12:40:56 stickster++ 12:40:58 +1 on schedule too 12:41:14 #agreed PUBLISHING SCHEDULE: Friday 27 Sep, #29 how to contribute (asamalik:edit) -- Monday 30 Sep, asking on the list for something -- Wednesday 2 Oct, #28 Hacktoberfest (stickster:edit/stickster:image) 12:41:23 Wow, this is pretty darn efficient agenda asamalik -- nice work 12:41:27 #topic 6/ Article proposals to clarify / approve 12:41:34 #info Review the the article proposals and decide about what's next — a new article spec? more discussion? 12:41:34 #link Article proposals: https://teams.fedoraproject.org/project/asamalik-fedora-magaz 12:41:43 stickster: it just feels like it, I moved this to the end :P 12:41:55 oops and again I screwed up! 12:41:58 #undo 12:41:58 Removing item from minutes: 12:42:06 #link Article proposals: https://pagure.io/fedora-magazine-proposals/issues 12:42:26 #action asamalik to fix link to Article proposals in the agenda in the docs 12:42:48 How do we vote on these? Just a +1/lgtm in the comments? 12:42:54 although we don't need to go through it now, we can do that anytime 12:43:30 stickster: yes, probably, and maybe adding some specifics of what we want to see in the article if that would help (like if the proposal is too broad) 12:44:23 but I'd say if something get's (now I'm making a process up) three +1s it's good to go, or no -1 in a week it's good to go? and someone would need to write the article spec in Taiga 12:45:32 I'd say two +1's would be good enough 12:45:34 ideally, we won't be looking there during the meeting 12:45:45 +1 to two +1's 12:46:05 asamalik: Whose responsibility is it to write the spec? That should appear in the magazine docs, probably, so it's clear 12:46:05 1 plus two plus two plus one 12:46:16 equals pi I'm pretty sure 12:46:24 <-- real gud at the maths 12:46:31 lol 12:46:54 #agreed proposals with two +1's in the ticket are good to go 12:47:06 so let's just do that offline! 12:47:09 One idea... if an editor writes the spec, they will probably get more of what they expect. However, it puts a burden on the editor to actually do it :-) 12:47:30 editors are here to lead, not to read^Wwrite 12:48:12 yeah it's a good point — who writes the spec? because just "good to go" is not enough here 12:49:07 "Contribute as an article spec writer to the Fedora Magazine!" 12:49:43 anyway 12:49:52 sorry I have not followed, what is exactly the spec ? 12:50:01 what we used to call the pitch ? 12:50:28 getting used to new process is hard :P 12:50:49 cverna: it's basically like a pitch: https://docs.fedoraproject.org/en-US/fedora-magazine/workflow-article-proposal/#_a_specific_pitch_example 12:50:52 cverna: Yeah, basically a short, simple description of what the article should cover 12:51:01 it's going from "I have this idea" to "this is the article we want" 12:51:13 I just realized it's documented on a wrong place in the docs, I'll fix that 12:51:18 ^ asamalik Yes! That may help prevent articles showing up that are incomplete, or not at all what was expected 12:51:29 #action asamalik fix the docs for "what is an article spec" explanation 12:51:37 And we want to make things easier on writers, vs. easier on editors, if we have to chose 12:51:41 *choose 12:51:43 cool, thanks for the clarification 12:52:00 yes, exactly 12:52:27 ideas are cheap! so we're sorting through them and making them into specific articles that are relevant for the Magazine 12:52:35 (although they're valuable) :) 12:52:50 * cverna finds it difficult to vote on an idea without the spec 12:52:59 cverna: ok that is a very good point 12:53:12 and sounds super obvious now that you mention it :) 12:53:31 :thi🤔 12:53:41 like I have an idea about an article on playing game on Fedora, how do we vote on that ? 12:53:45 we need more info 12:53:49 Yeah 12:53:49 yep! 12:53:53 You're right cverna. 12:54:14 so let's make people either submit a spec directly, or an idea which we make into a spec and then vote on it 12:54:23 +1 12:54:31 (or trash it, that happens too, asking for "just good ideas" is not realistic) 12:55:02 yes just submitting an idea is still fine, but we should use the ticket in pagure to refine the scope if needed 12:55:14 then writing the spec should be easy 12:55:58 #proposed #agreed We can't vote on an idea, we need to vote on a spec. So we either ask people to either propose specs, or to propose ideas that we turn into a spec, and then we vote on that. 12:56:08 yep! 12:56:18 +1 12:56:19 +1 12:56:24 and because it's in Pagure, we can easily ping whoever we need to to get it to a more specific state 12:56:34 * stickster does https://pagure.io/fedora-magazine-proposals/issue/13 as an example 12:56:41 #agreed We can't vote on an idea, we need to vote on a spec. So we either ask people to either propose specs, or to propose ideas that we turn into a spec, and then we vote on that. 12:56:54 so we keep using the pagure repo as the idea collection point and help them spec it up if needed? 12:57:06 #action asamalik to update the docs regarding ideas, spec, and voting we've just discussed and agreed on 12:57:18 bcotton: yep 12:57:38 cool, then i'm a late +1 :-) 12:57:48 to collect ideas and to make them into specific... specs :) 12:57:54 \o/ 12:58:19 Once that spec is agreed we can just copy it into the Taiga card too 12:58:25 That seems pretty simple 12:58:27 yep! 12:58:35 that makes sense from a process standpoint as well! 12:58:54 ok, one minute left! 12:59:05 #topic 7/ Open floor 12:59:13 * asamalik waits 60 seconds! 12:59:24 Hmm, we ran out of time, but at some point we need to discuss how to get more writers inbound here. 12:59:46 Having our *process* ready is definitely needed first. So it doesn't make sense to run out and wave our arms around right now :-) 12:59:52 yes 13:00:06 I agree :) 13:00:13 I've proposed an article about contributing 13:00:19 it's in Pagure 13:00:23 so that might be a good first step 13:00:40 but we should also think about more sophisticated strategy 13:00:46 Once we have our process in good shape (and as simple from writer POV as possible), we *should* definitely start looking to mattdm and whoever our upcoming FCAIC is about how to pull in some more writers here 13:00:49 * asamalik will at least think about it 13:00:52 an article layingout the steps for those wanting to contribute 13:01:03 stickster: yeah 13:01:10 Southern_Gentlem: I agree 13:01:39 I think we mentioned in one of our conversation with stickster even a short youtube video walking through the process 13:01:40 Southern_Gentlem: We have https://docs.fedoraproject.org/en-US/fedora-magazine/ which is where we want to point everyone, even from an article itself 13:01:47 oh! 13:01:55 asamalik: ^ yes, that too. I can work on that when I get some weekend time. 13:02:01 I have updated the homepage pointing to the docs: https://fedoramagazine.org/ 13:02:03 I'll start by writing a script for it. 13:02:05 I did that like 2 hours ago 13:02:10 Nice! 13:02:21 * cverna goes in another meeting 13:02:22 * stickster notices we're over time 13:02:25 stickster: cool! I'm happy to help with/do that as well 13:02:31 thanks all 13:02:33 yep, we're over time here 13:02:56 ok, thanks all! 13:03:04 #endmeeting