12:00:00 #startmeeting Magazine editorial board 12:00:01 Meeting started Wed Oct 23 12:00:00 2019 UTC. 12:00:01 This meeting is logged and archived in a public location. 12:00:01 The chair is stickster. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:00:01 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:00:01 The meeting name has been set to 'magazine_editorial_board' 12:00:03 #meetingname magazine 12:00:03 The meeting name has been set to 'magazine' 12:00:04 #topic Roll call 12:00:05 .hello pfrields 12:00:06 stickster: pfrields 'Paul W. Frields' 12:00:30 #chair asamalik cverna ryanlerch bcotton gregbartholomew sub_pop 12:00:30 Current chairs: asamalik bcotton cverna gregbartholomew ryanlerch stickster sub_pop 12:00:42 * cverna waves 12:01:19 #info asamalik is on PTO this week, betting he won't be here, but hopefully ryanlerch and a few others will, and we'll muddle through :-) 12:01:27 #topic 1/ Last week's stats 12:02:44 Wow, either Ipsilon or the Magazine is slow today 12:03:39 * cverna tries login in 12:03:44 #info Week of Oct 14: 66.6K pageviews 12:05:22 #info About average... But the good news is several new authors popped up from our contribution article, thanks asamalik for that :-) 12:05:36 #topic 2/ In progress followup 12:05:37 #topic 2/ In progress followup 12:05:41 #undo 12:05:41 Removing item from minutes: 12:05:57 yes it is really cool to see so many article proposals 12:06:01 asamalik++ 12:07:01 Anyone see jflory7 around? He still has a pending article on swiss-army, not sure if that is on its way to complete or should be put aside 12:07:26 not sure either 12:08:05 #action stickster ping jwf to ask about swiss-army article 12:08:27 The other article on disk space math was literally just picked up, so no need to check that 12:09:26 Sorry, a little slow with new agenda... working on it! 12:09:37 no worries :-) 12:09:38 #topic 3/ Finished articles to review 12:10:12 Looks like we have a COPR article to review, and bcotton has the ball 12:11:21 Also looks like Wireguard article was completed by Pete Maynard, so I'm adding that to the Review column 12:11:32 I think there may be some In Progress also not represented on the board properly 12:11:52 * bcotton is here now 12:12:04 Hey bcotton! Good morning :-) 12:12:16 good morning, stickster! 12:12:22 bcotton: o/ 12:12:32 hi cverna! 12:12:57 OH HEY BTW... I forgot to say at the top... I have a crew coming to do some work in our kitchen. They are supposed to be here in the *next* hour but frequently contractors show up early. So I may have to leave on very short notice and ask someone to conclude the meeting for me 12:13:12 bcotton: Did I understand right that you're reviewing the COPR article? 12:14:28 * stickster volunteers to edit the Wireguard article 12:14:36 well right now i'm spilling coffee everywhere, but yes 12:16:06 ha 12:16:33 OK, so it sounds like we have two things that can complete soon. bcotton, you think it'll be ready for Friday? I don't think we have anything else scheduled 12:17:12 yeah, i think so. it can probably be scheduled now. the edits i made were trivial enough that the author shouldn't object 12:17:38 but i'd just like to note for the record how annoyed I am that we use both "Copr" and "COPR" willy-nilly in the docs 12:18:10 Yeah, it should always be an acronym as far as I know. 12:18:22 bcotton: Are these docs on docs.fp.o? 12:18:30 Like things we could pull-requst against? 12:19:10 not on docs.fp.o, but they might be in a pull-requestable location 12:19:23 my annoyance hasn't risen to the level of doing work yet ;-D 12:20:07 the website itself is using Copr 12:20:13 https://copr.fedorainfracloud.org/ 12:20:24 Ah OK 12:20:29 Well, for another day then 12:20:35 https://pagure.io/copr/copr 12:20:50 OK, I can have the Wireguard article ready for Monday, no problem. 12:21:30 I realized just now I've hopped topics. 12:21:38 #topic 4/ Articles to edit 12:21:51 #action bcotton edit COPR article for Friday 12:21:58 #action stickster edit Wireguard article for Monday 12:22:45 * stickster wonders if ryanlerch is around 12:22:53 We could sock him with at least one image if not more :-) 12:23:13 bcotton: You can use the stock COPR image, no work to do there! 12:23:22 #aciton stickster do image for Wireguard article 12:23:27 #action stickster do image for Wireguard article 12:23:32 spelin cownts 12:24:02 #topic 5/ Publishing schedule 12:24:12 bcotton: How are we looking for Fedora 31 release date? 12:24:56 the general consensus is that we'll be Go tomorrow for a 29 October release. i have been reminding mattdm about his article obligation 12:25:18 mattdm: I can make a shell for you now with your name on it, and bcotton if you could make a card that would be awesome 12:25:25 shell article, that is 12:25:30 stickster: ack 12:26:49 #info F31 release announcement article is saved at https://fedoramagazine.org/wp-admin/post.php?post=29530&action=edit 12:26:59 #action mattdm to write release announcement for Tuesday publication 12:27:02 oh hey, i already did! 12:27:04 https://teams.fedoraproject.org/project/asamalik-fedora-magazine/us/74 12:27:14 Nice! 12:27:25 This means we also need a couple other articles... 12:27:40 * A "how to upgrade from Fedora 30 to 31" article (mainly copy/paste) 12:28:17 * A "What's new in Fedora 31 Workstation" article 12:28:45 bcotton: ^ Can you create cards for those? 12:28:51 stickster: on it 12:29:16 can make sure the URL of the release announcement article is correct, it is always biting us ( i think mboddu is using it in his release announcement email) 12:29:39 I think I did, but please double check cverna 12:29:45 Should be '/announcing-fedora-31' 12:29:47 * cverna checks 12:30:20 Also, same for the Workstation article. I just set it to /whats-new-fedora-31-workstation which should be correct -- kalev may be the guy who can verify this is the right URL to work automagically in GNOME Software 12:30:26 stickster: i'll even take wrtiging the upgrading article 12:30:57 the URL slug is set to announcing-the-release-of-fedora-31 12:30:58 bcotton: That's awesome! bcotton -- I do recall there is a thing going on with libgit2 that caused an issue, so it would be good to make sure there is a link to Common bugs or maybe even a tip on that iff. it's not solved already 12:31:07 I am not sure if this is used or not tho 12:31:09 cverna: Ugh, that means it didn't save, can you fix and save the article again? 12:31:11 stickster: that's part of the reason i volunteered to take it ;-) 12:31:18 sure 12:31:19 Thank you bcotton :-) You're a champ 12:31:28 i've been called close to that before 12:31:32 LOL 12:31:37 "I've been called worse" 12:32:10 stickster: do you want to tripple check now :P 12:32:28 I thought we had a contributor around at one point who was highly involved in GNOME and might be willing to take the Workstation article... but it's kind of short notice. I can probably take this on. 12:32:42 cverna: Can I steal your edit lock? 12:32:46 sure 12:33:31 cverna: Sigh, it keeps resetting 12:34:03 It might simply be because it's only in draft mode, and it won't keep the right URL until scheduled or published 12:34:08 I'll make a note at top 12:34:13 +1 12:35:22 Done 12:35:48 If ryanlerch were here I'd give him the Workstation article, maybe I should anyway :-) 12:36:07 #action stickster contact ryanlerch and assign What's New in F31 Workstation article 12:38:20 bcotton: I guess all of these will run Tuesday 12:38:40 i mean, we could trickle them out over the course of the week? 12:38:43 particularly the what's new 12:38:55 but i feel like most people who would upgrade on release day already know how to anyway 12:39:25 bcotton: The problem with that is (1) upgrading article is usually linked from the announcement itself, and (2) the Workstation article is linked from GNOME Software's upgrade notice, so it needs to be there on GA day 12:39:26 but from a marketing perspective, i always like to keep steady pressure instead of a burst 12:39:31 ugh 12:39:38 dependency hell is still with us 12:39:42 heh yep 12:39:53 can we modularize the articles? :-D 12:39:57 ha 12:40:49 In any case, the announcement article should be "pinned," and the other two articles published manually right after the announcement goes out 12:41:02 well if someone can do An Artâ„¢for the upgrading, i'll do it friday afternoon at the airport 12:41:12 i'll do the article friday, to be clear 12:41:17 I'll ask ryanlerch for that too 12:41:30 #action ryanlerch Do featured image for upgrade article 12:41:38 bcotton: The good news is the article should be short work 12:42:16 cverna: Would you be interested to do the Firefox article for Thursday? 12:42:19 aside: i'd like to learn how to do art for magazine headers, maybe that could be an article itself? or a video series. but anyway 12:42:36 do we have something for wednesday in case the release slips again? 12:42:42 https://docs.fedoraproject.org/en-US/fedora-magazine/creating-an-image/ 12:44:04 stickster: Thursday (ie tomorrow ?) 12:44:14 stickster: I can probably do it :) 12:44:28 cverna: I mean a week from tomorrow :-) 12:44:42 I'm not THAT mean! :-D 12:45:17 haha I can do that 12:45:26 stickster: magic! 12:46:07 stickster: hm. that assumes a lot of knowledge already, i think. but i'll play around sometime and see if i have actual suggestions for it 12:46:30 bcotton: Yeah, possibly. Suggestions highly welcome :-) There's a bit of "aesthetic skill" needed too 12:46:41 That's hard to put in a simple set of instructions :-) 12:48:03 bcotton: I usually start from an existing image and just make some modification. 12:48:15 there is a git repo with the svg's somewhere :P 12:48:27 https://pagure.io/fedoramagazine-images 12:48:48 Yeah, if you ever make one, you should put the SVG in there (or submit as PR) 12:48:49 here you go :) 12:49:01 yay 12:49:07 sorry for the distraction 12:49:10 no worries 12:49:17 #proposed #agreed PUBLISHING SCHEDULE: 12:49:53 Friday Oct 25, COPR (bcotton:edit/:image) 12:50:05 Mon Oct 28, Wireguard (pfrields:edit/pfrields:image) 12:50:34 Tue Oct 29, F31 announcement (pfrields:edit/ryanlerch:image?) 12:50:45 Tue Oct 29, F31 upgrading (bcotton:edit/ryanlerch:image?) 12:50:55 Tue Oct 29, F31 Workstation (pfrields:edit/pfrields:image) 12:51:36 Thu Oct 31, Firefox 70 (TBA:edit/:image) <-- We have a Firefox stock image 12:51:57 ^ yay/nay? 12:52:27 YAY !! 12:52:43 can we make Firefox 70 the wednesday alternate in case of slip 12:52:48 or will it only be in f31? 12:53:16 I think we can 12:53:27 cool. then i am a yea 12:53:27 it will be in F30 also 12:53:45 I don't think it will get out of freeze in F31 if the release doesn't go out, but it'll probably be in F30 12:54:25 And should be a zero-day in F31 12:54:53 But anyway... sure we can probably do the article. Let's hope for that not to be the case, though :-) 12:55:07 #agreed PUBLISHING SCHEDULE: Friday Oct 25, COPR (bcotton:edit/:image) -- Mon Oct 28, Wireguard (pfrields:edit/pfrields:image) -- Tue Oct 29, F31 announcement (pfrields:edit/ryanlerch:image?)Tue Oct 29, F31 announcement (pfrields:edit/ryanlerch:image?) -- Tue Oct 29, F31 upgrading (bcotton:edit/ryanlerch:image?) -- Tue Oct 29, F31 Workstation (pfrields:edit/pfrields:image)Tue Oct 29, F31 12:55:13 Workstation (pfrields:edit/pfrields:image) -- Thu Oct 31, Firefox 70 (TBA:edit/:image) 12:55:18 whoops 12:55:19 #undo 12:55:19 Removing item from minutes: AGREED by stickster at 12:55:07 : PUBLISHING SCHEDULE: Friday Oct 25, COPR (bcotton:edit/:image) -- Mon Oct 28, Wireguard (pfrields:edit/pfrields:image) -- Tue Oct 29, F31 announcement (pfrields:edit/ryanlerch:image?)Tue Oct 29, F31 announcement (pfrields:edit/ryanlerch:image?) -- Tue Oct 29, F31 upgrading (bcotton:edit/ryanlerch:image?) -- Tue Oct 29, F31 Workstation (pfrields:edit/pfrields:image)Tue Oct 29, F31 12:55:30 #agreed PUBLISHING SCHEDULE: Friday Oct 25, COPR (bcotton:edit/:image) -- Mon Oct 28, Wireguard (pfrields:edit/pfrields:image) -- Tue Oct 29, F31 announcement (pfrields:edit/ryanlerch:image?)Tue Oct 29, F31 announcement (pfrields:edit/ryanlerch:image?) -- Tue Oct 29, F31 upgrading (bcotton:edit/ryanlerch:image?) -- Tue Oct 29, F31 Workstation (pfrields:edit/pfrields:image) -- Thu Oct 31, 12:55:36 Firefox 70 (TBA:edit/:image) 12:55:43 oh for goodness sake 12:55:45 #undo 12:55:45 Removing item from minutes: AGREED by stickster at 12:55:30 : PUBLISHING SCHEDULE: Friday Oct 25, COPR (bcotton:edit/:image) -- Mon Oct 28, Wireguard (pfrields:edit/pfrields:image) -- Tue Oct 29, F31 announcement (pfrields:edit/ryanlerch:image?)Tue Oct 29, F31 announcement (pfrields:edit/ryanlerch:image?) -- Tue Oct 29, F31 upgrading (bcotton:edit/ryanlerch:image?) -- Tue Oct 29, F31 Workstation (pfrields:edit/pfrields:image) -- Thu Oct 31, 12:56:06 #agreed PUBLISHING SCHEDULE: Friday Oct 25, COPR (bcotton:edit/:image) -- Mon Oct 28, Wireguard (pfrields:edit/pfrields:image) -- Tue Oct 29, F31 announcement (pfrields:edit/ryanlerch:image?) -- Tue Oct 29, F31 upgrading (bcotton:edit/ryanlerch:image?) -- Tue Oct 29, F31 Workstation (pfrields:edit/pfrields:image) -- Thu Oct 31, Firefox 70 (TBA:edit/:image) 12:56:08 * bcotton brews more coffee 12:56:09 * cverna is lost :P 12:56:12 There we go 12:56:17 #topic 6/ Article proposals to clarify / approve 12:56:38 * stickster skips this topic because we haven't seen any pitches this week, plus no time 12:56:42 #topic 7/ Open floor 12:57:14 Does anyone know why a contributor wouldn't receive an invitation from Taiga? I sent one this week and George Maluf didn't receive any email 12:57:23 ^ might be a question for asamalik 12:57:44 I'll ask this on list. No need to go into it here. 12:57:48 Anything else? 12:58:16 If not, I'll close up shop and send notes 12:58:25 cverna: bcotton: Thanks for coming! 12:58:32 stickster++ thanks for hosting 12:58:37 #endmeeting