12:03:36 #startmeeting Magazine editorial board 12:03:36 Meeting started Wed Apr 29 12:03:36 2020 UTC. 12:03:36 This meeting is logged and archived in a public location. 12:03:36 The chair is stickster. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:03:36 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:03:36 The meeting name has been set to 'magazine_editorial_board' 12:03:40 #meetingname magazine 12:03:40 The meeting name has been set to 'magazine' 12:03:42 #topic Roll call 12:03:46 .hello pfrields 12:03:48 stickster: pfrields 'Paul W. Frields' 12:04:02 hello SSnow 12:04:51 o/ 12:04:56 o/ 12:05:42 I wonder who else will be here today 12:06:25 I understand Adam is busy, I was browsing the Redhat virtual tour yesterday and will be going back today 12:07:12 hello 12:07:27 cverna: o/ 12:09:21 Hi cverna 12:09:39 OK, sorry about delays guys. I have a lot going on and running this meeting is not easy anymore unfortunately :-( 12:10:10 np 12:10:18 #chair stickster ryanlerch cverna asamalik sub_pop gregbartholomew bcotton misc rwaltr 12:10:18 Current chairs: asamalik bcotton cverna gregbartholomew misc rwaltr ryanlerch stickster sub_pop 12:10:33 #topic Agenda 12:10:33 #link https://docs.fedoraproject.org/en-US/fedora-magazine/workflow/ 12:10:33 #info -- 1/ Last week's stats -- 12:10:33 #info -- 2/ In progress followup -- 12:10:33 #info -- 3/ Finished articles to review -- 12:10:35 #info -- 4/ Articles to edit -- 12:10:38 #info -- 5/ Publishing schedule -- 12:10:40 #info -- 6/ Article proposals to clarify / approve -- 12:10:43 #info -- 7/ Open floor -- 12:10:57 #topic 1/ Last week's stats 12:11:31 stickster: I can take over if that helps 12:11:56 cverna: If you could help prompt if I get slow that would be great 12:11:56 are we using this https://docs.fedoraproject.org/en-US/fedora-magazine/editorial-meetings/ as the script ? 12:12:23 #info Week of Apr 20: 87.5K pageviews -- quite an increase from previous week, YAY!!!! 12:12:46 The Fedora on Lenovo article seems to have been a BIG deal for stats, no big surprise there :-) 12:12:48 that works 12:13:16 #topic 2/ In progress followup 12:13:16 #info Looking at the 'in progress' column, is there something that's been finished? Anything to follow up on with its author? 12:13:19 #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban 12:13:33 yeah this was a really big news :-) 12:14:09 It was *very* cool to see this announced, yeah. I may be switching back to Lenovo for my next system :-) 12:14:34 I use Lenovo laptops for my industrial programming 12:14:57 In fact I still have my first IBM Thinkpad 12:15:13 from the 90's 12:16:13 So for in progress stuff on the board -- the GOOD news is we have lots of articles in progress 12:17:06 I don't see that any of these are fully done yet, but most are active in the last week 12:17:26 two firewald articles 12:19:08 Yeah, that's going to be cool when they get done 12:19:50 I can't see any clear TODO here since these are in flight 12:20:01 it does seem so 12:20:06 Let's check again late in the week then. Shall we move on? 12:20:32 please do 12:21:27 #topic 3/ Finished articles to review 12:21:45 We have two articles ready to review, it looks like 12:22:19 #link #144 -- to edit by jakfrost? https://teams.fedoraproject.org/project/asamalik-fedora-magazine/us/144?kanban-status=192 12:22:31 ^ How's that one going jakfrost? 12:22:39 yes I will be editing today later 12:23:00 The article looked pretty good when I briefly looked it over 12:23:02 Cool! Could we publish this one Friday? 12:23:08 I think so 12:23:38 Was I supposed ot do the image I think 12:23:39 #action jakfrost do edits on #144, target for publishing Friday May 1 12:23:50 jakfrost: It's up to you -- if you need help we can find some 12:23:58 okay 12:24:15 jakfrost: You can find tips at https://docs.fedoraproject.org/en-US/fedora-magazine/creating-an-image/ 12:24:32 cool I'll check it out 12:24:39 If you do the image, you'll want the git repo, and please submit the SVG image back as a PR :-) 12:25:07 There are some tips there to scale your background image so the commit won't be huge 12:25:39 I'll use the list if I need assistance 12:26:00 #link to edit by stickster -- https://teams.fedoraproject.org/project/asamalik-fedora-magazine/us/160 12:26:11 I can edit/image the COPR article and schedule for Monday. 12:26:44 My hope is that one of these firewall articles will be ready shortly, and we can use it next week 12:27:01 that would be cool 12:27:06 I can commit to do https://teams.fedoraproject.org/project/asamalik-fedora-magazine/us/156 for wednesday 12:27:33 Oh whoops, I did the wrong column for this section, apologies folks 12:27:50 #action stickster edit/image for COPR article #160 12:27:52 no problem 12:27:53 #topic 4/ Articles to edit 12:27:53 #info Looking at the 'to edit' column, assign an editor and a cover image creator. 12:27:56 #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban 12:28:04 #info stickster covered this erroneously already :-) 12:28:11 #topic 5/ Publishing schedule 12:28:12 #info Looking at the 'queued' and 'to edit' columns, decide the publishing schedule for the next week period. 12:28:14 #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:28:17 #link Board: https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban 12:29:41 #proposed #agreed Fri May 1: Using mergerfs (edit/image: jakfrost) -- Mon May 4: COPR (edit/image: stickster) -- Wed May 6: TBD, whoever finishes first :-) 12:29:55 +1 from me obviously 12:30:01 +1 12:30:16 +1 12:30:29 #agreed Fri May 1: Using mergerfs (edit/image: jakfrost) -- Mon May 4: COPR (edit/image: stickster) -- Wed May 6: TBD, whoever finishes first :-) 12:30:49 #topic 6/ Article proposals to clarify / approve 12:30:49 #info Review the the article proposals and decide about what's next — a new article spec? more discussion? 12:30:52 #link Article proposals: https://pagure.io/fedora-magazine-proposals/issues 12:31:55 OK, so we have a *lot* of issues in the queue. This weekend I swept through and did comments on many. We could use review from other editors, it would be nice to have two (2) +1's agreeing for someone to go forward, or else ask for info that would help us decide on an article proposal 12:32:31 wow 22 open issues 12:32:45 * cverna looking at some now 12:33:09 \me looks too 12:33:15 Do you guys think we could use a tag like "Needs writer" to help identify things that are open for assignments? 12:33:31 sounds reasonable to me 12:34:27 yeah we could advertise them on the list also 12:35:01 Cool, I just made the tag 12:36:57 I just started tagging a few. Could I ask each of you to do this: (1) Go through any articles that only have one comment, and if that comment is +1, consider whether or not you approve, and add a comment (either +1 or a question) 12:37:37 (2) If you see any article that has no *recent* response from the suggester/author, add a comment like I just did in https://pagure.io/fedora-magazine-proposals/issue/22 12:37:42 sure, I can edit my recent comment on #77 12:37:55 I ll create the taiga card for the articles that have a +2 12:38:07 jakfrost: That looks like a clear +1 to me :-) 12:38:36 cverna: Cool 12:38:51 cverna: cool also 12:39:22 I'm also not sure what to do with a card that then sits without action. I personally feel like we should clear out those old cards, because they don't look like proposals anymore, they look like something that is supposed to be done. And then we have *two* places tracking that 12:40:19 certainly some will have time limits due to subject matter 12:40:44 the extra tracking of unnecessary items becomes a burden 12:40:53 Yes, that's true. For instance, a card near the top in Taiga is an event that happened quite a while ago. 12:41:42 https://teams.fedoraproject.org/project/asamalik-fedora-magazine/us/131 12:41:56 Yeah I agree we should probably just close old card and tickets 12:42:06 yes, that would qualify 12:42:08 I left a comment in that one for the author because it seems like it would be a bit unfortunate to write and publish it right now 12:43:07 we should always give a reason we close something I would think, by comment on Taiga perhaps 12:43:41 Agreed. Never close without a comment (unless the card was a mistake or no one else would be affected) 12:43:54 +1 12:46:45 What else can we take action on here? 12:47:05 there are several good ideas 12:47:52 jakfrost: Are you saying you want to pick up an article in that list? 12:48:43 #action cverna jakfrost Go through proposal issues, and add +1 or comments where needed, or tag with 'Needs writer' 12:48:52 not really, but I can look through for something authorless 12:49:17 I wasn't expecting us to take up authorship here, but you're welcome to do that anytime! 12:49:22 #topic 7/ Open floor 12:49:55 the author of the Fedora Origins story is working on the second part 12:50:42 #topic 7/ Open floor 12:50:47 oops, sorry 12:51:03 for?? 12:51:54 Extra /topic :-) This does segue into a topic of interest. I was talking to asamalik last week, and one of the things that we noted was, we still have *two* tracking systems and even though it's definitely improved over previous, it still makes things more difficult than necessary for editors (and contributors) 12:52:28 Yes the issues and taiga 12:52:58 I definitely like using the kanban style to track the work, but having to move things across systems from Pagure to Taiga is painful 12:53:38 Yeah I agree too 12:53:46 I agree about the disconnect between the two, is there no java api we could leverage, I'd volunteer to write code for that 12:53:47 Does anyone here have experience using GitHub for a project? My understanding is there's kanban built in, but does that make things any easier to move issues -> cards or vice versa? 12:54:14 Or GitLab for that matter, I don't know either one that well. 12:54:40 not I for large projects, just small stuff 12:55:20 This feels like the kind of thing we could easily solve by moving the work to one place that handles all the operations we need 12:55:36 Also using GitHub or GitLab means that we can't use our Fedora Accounts for login :( 12:55:42 Ugh, correct 12:55:54 Yeah, that would suck. 12:56:27 Pagure is written in Python 12:56:40 OTOH I wonder how many people in Fedora land don't have GH accounts :-) 12:57:19 yeah I guess not many indeed 12:57:51 Anyway, something to think about. 12:57:52 (we just got a couple of tickets on the infra tracker about an app hosted on GH because the person didn't want to interact with it) 12:58:10 ¯\_(ツ)_/¯ 12:58:25 (it's anecdotal but just aims to illustrate that it is != 0, though it may be very low in %) 12:59:17 Some people may not want to. I have found over the years that the set of people who are interested in writing helpful docs and articles does not cross over much with the set of people who put a very stringent value on what tool they're using 12:59:18 good point 12:59:46 Anyway, we won't solve this today, but something to think about for the future. 12:59:54 I need to run to a call -- so thank you everyone for attending! 13:00:05 #endmeeting