16:00:51 #startmeeting magazine 16:00:51 Meeting started Thu Jan 20 16:00:51 2022 UTC. 16:00:51 This meeting is logged and archived in a public location. 16:00:51 The chair is zinebot[m]. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:00:51 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:51 The meeting name has been set to 'magazine' 16:00:52 #meetingname magazine 16:00:52 The meeting name has been set to 'magazine' 16:00:52 #topic roll call 16:00:52 #chair zinebot glb rlengland theevilskeleton 16:00:52 Current chairs: glb rlengland theevilskeleton zinebot zinebot[m] 16:01:30 .hello rlengland 16:01:30 .hello glb 16:01:31 RichardEngland[m: rlengland 'Richard England' 16:01:34 glb: glb 'Gregory Bartholomew' 16:02:10 β‹„ next topic 16:02:10 #link https://docs.fedoraproject.org/en-US/fedora-magazine/workflow/ 16:02:11 #topic agenda 16:02:11 #info -- 1/ last week's stats -- 16:02:11 #info -- 2/ articles in progress -- 16:02:11 #info -- 3/ articles to review -- 16:02:11 #info -- 4/ articles to edit -- 16:02:11 #info -- 5/ publishing schedule -- 16:02:12 #info -- 6/ editor of the week -- 16:02:12 #info -- 7/ open floor -- 16:03:27 β‹„ next topic 16:03:27 #topic 1/ last week's stats 16:04:00 7.8k views. About comparable to last week 16:04:17 Um, that seems a little low. 16:04:40 Maybe you are looking at the daily view? 16:05:05 Also, beware that the weekly stats are for "weeks" that begin on Monday. 16:06:35 I'm getting caught in "login" hell right now.... 16:07:15 It's always something. πŸ™‚ 16:07:50 I set up SSO a long time ago and that seems to work pretty good. 16:08:45 Okay 44.8k views for the week. But still comparable to last week which was ~46k 16:09:15 That should be prefixed with #info though so that it will go into the record. 16:09:57 #info 44.8k views for the week. Slightly lower but comparable to last week 16:10:16 Works for me. πŸ™‚ 16:10:28 β‹„ next topic 16:10:36 #topic 2/ articles in progress 16:10:37 #link board: https://pagure.io/fedora-magazine-newsroom/boards/articles 16:10:38 #info Looking at the 'in-progress' column, is there something that's been finished? Anything to follow up on with its author? 16:10:38 #info 059: Commands providing views into the system (author: zexcon) (fpca: signed) (status: in-progress) 16:10:38 #link status: https://pagure.io/fedora-magazine-newsroom/issue/59 16:10:38 #link preview: https://fedoramagazine.org/?p=34935&preview=true 16:10:38 #info 068: Spam classification with neural networks (author: fed500) (fpca: signed) (status: in-progress) 16:10:39 #link status: https://pagure.io/fedora-magazine-newsroom/issue/68 16:10:39 #info 069: Build a file server solution with Microsoft AD authentication using Fedora server and samba (author: dklima) (fpca: signed) (status: in-progress) 16:10:40 #link status: https://pagure.io/fedora-magazine-newsroom/issue/69 16:10:40 #info 070: Fedora server edition on a raspbery pi (author: pboy) (fpca: signed) (status: in-progress) 16:11:10 I wonder if adding a small delay would help? 16:11:12 #link status: https://pagure.io/fedora-magazine-newsroom/issue/52 16:11:12 #link preview: https://fedoramagazine.org/?p=35824&preview=true 16:11:13 #info 072: Introduction to OpenFOAM (author: thunderbirdtr) (fpca: signed) (status: in-progress) 16:11:13 #link status: https://pagure.io/fedora-magazine-newsroom/issue/72 16:11:13 #link preview: https://fedoramagazine.org/?p=35214&preview=true 16:12:07 There is obviously a rate limit for how fast posts can be made to matrix. 16:12:37 πŸ™‚ I leave that to the "engine room" team πŸ™‚ 16:13:47 I've reviewed the in progress and I didn't see any that could take further prompting (without seeming to be pushy). Any that you see that could be pinged? 16:14:22 Nah. I think we actually have enough for the upcoming week anyway. 16:15:05 I'm assuming that the test days article will be ready for Monday. 16:15:36 :crossed_finger:. 16:16:02 β‹„next topic 16:16:22 β‹„ next topic 16:16:23 #info Are there any upcoming test days? 16:16:23 #link https://calendar.fedoraproject.org/QA/ 16:16:34 Need a space in there... 16:17:17 Let's go ahead and move that test days card (#82) to the to-edit column so we can get it on the schedule. 16:17:54 #info F36 Kernel 5.16 test week start on 23 jan 16:18:07 β‹„ show testdays 16:18:08 Sun 23 Jan 2022: [F36] Kernel 5.16 Test Day (8 days) 16:19:00 (thank you) 16:19:41 We probably ought to have zinebot prefix that with '#info" whenever there is a test day. 16:20:16 You're taking notes on all this right Richard. πŸ™‚ 16:20:30 ahhh.....right 16:22:32 I've moved the test day article, Pagure is being a bit of a problem child for me today 16:23:24 I find that I sometimes have to press F5 (refresh) after doing something in Pagure before it shows up. 16:23:58 If you know the card number, zinebot also has a function for moving cards around. 16:24:28 πŸ‘οΈ . 16:24:39 β‹„ show schedule 16:24:42 Tue 08 Mar 2022: Prepare Beta release announcement... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/5c1b4a8808fafc34672dca4b57d6383131bd4404) 16:25:37 #info nothing scheduled until March 16:26:22 We ought to have that 'show schedule' function refuse to run if we aren't in the right topic. 16:26:36 Make note of that Richard. πŸ˜› 16:26:56 Maybe I'm having too much fun. πŸ˜› 16:27:30 Was that schedule out of order? That's in the current topic, correct? 16:27:41 Sort of. 16:28:08 The testday and schedule "topics" each have their own heading. 16:28:30 The headings are printed out when you enter "next topic". 16:29:03 Maybe things could be rearranged or merged if you see a better way to do it though. 16:29:07 ...This is why I thing we need a "roadmap" for using zinebot in the docs. Other wise a newby doesn't know when to move to the next topic 16:29:25 thing - think 16:29:49 I thought that was the meeting script that is in the docs? 16:30:20 Maybe it would help if zinebot presented a preview of what was coming up next though? 16:30:21 It doesn't call out how to use zinebot and that is where the "roadmap" could be included. 16:30:31 I'll work on adding that. 16:30:41 Sounds good to me. πŸ™‚ 16:30:54 back at it... 16:31:02 β‹„ next topic 16:31:02 #info Check the release schedule. 16:31:03 #link https://fedorapeople.org/groups/schedule/f-36/f-36-magazine-tasks.html 16:31:22 β‹„ show scheduel 16:31:31 β‹„ show schedule 16:31:33 Tue 08 Mar 2022: Prepare Beta release announcement... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/5c1b4a8808fafc34672dca4b57d6383131bd4404) 16:31:39 Again.... 16:31:54 # nothing until March 16:32:02 I skip it sometimes because I know it doesn't change much. 16:32:16 Wow, so loud. 16:32:20 πŸ™‚ 16:32:39 β‹„ next topic 16:32:43 #topic 3/ articles to review 16:32:44 #info Looking at the 'review' column, let's decide which articles are good to go. Move each either to the 'to-edit' (finished) column or to the 'in-progress' (needs more work) column and provide feedback. 16:32:44 #link board: https://pagure.io/fedora-magazine-newsroom/boards/articles 16:32:45 #info 081: Using Quarkus and Mutiny to write Java asynchronous code (author: daveome) (fpca: signed) (status: review) 16:32:45 #link status: https://pagure.io/fedora-magazine-newsroom/issue/81 16:32:45 #link preview: https://fedoramagazine.org/?p=35869&preview=true 16:33:23 I saw 81 being worked on earlier. 16:34:10 I think he is just trying to fix up some of the formatting in the code blocks. 16:34:22 Otherwise, I think this one is ready for editing. 16:34:58 I picked up #13 since I've recently worked on that a bit on my own 16:35:09 Any chance you can get 81? 16:35:10 I'll take 81 16:35:44 I guess there ought to be a zinebot command to assign and editor. πŸ™‚ 16:36:24 s/and/an/ 16:37:23 looks like daveome has done an image 16:37:36 I've assigned it to you. 16:39:09 I can pick up #82 when it comes in unless you want it. 16:39:17 (the test week) 16:39:31 It doesn't matter to me. 16:39:39 That one should be very easy. 16:39:47 It is just a template. 16:39:58 We've pinned those in the past. 16:40:07 But I think maybe we should stop doing that. 16:41:02 Part of the reason that I started pinning them was because there was another pinned article (the IRC announcement) that would prevent newer non-pinned articles from showing up as the first item. 16:41:19 So it was a battle of the pinned articles for a while there. 16:41:28 But that is no longer necessary IMO. 16:41:53 πŸ‘Œ 16:42:15 gotta remember that size of those... or not use them 16:42:25 β‹„ next topic 16:42:31 #topic 4/ articles to edit 16:42:32 #info Looking at the 'to-edit' column, assign an editor and a cover image creator. 16:42:32 #link board: https://pagure.io/fedora-magazine-newsroom/boards/articles 16:42:32 #info 013: VNC Server in Fedora Linux (author: lruzicka) (fpca: signed) (status: to-edit) 16:42:32 #link status: https://pagure.io/fedora-magazine-newsroom/issue/13 16:42:33 #link preview: https://fedoramagazine.org/?p=35875&preview=true 16:42:33 #info 082: [Fedora Test Week] Fedora Kernel 5.16 from 2022-01-23 through 2022-01-29 (author: sumantrom) (fpca: signed) (status: to-edit) 16:42:33 #link status: https://pagure.io/fedora-magazine-newsroom/issue/82 16:42:34 #info 081: Using Quarkus and Mutiny to write Java asynchronous code (author: daveome) (fpca: signed) (status: to-edit) 16:42:34 #link status: https://pagure.io/fedora-magazine-newsroom/issue/81 16:42:34 #link preview: https://fedoramagazine.org/?p=35869&preview=true 16:43:18 I've got #13 down for tomorrow (with luck I can get through the testing today) 16:43:24 editing is done 16:43:42 #82 ASAP I assume 16:43:53 Scheduling is actually the next section 16:44:08 (oy) 16:44:09 That has thrown me off several times too. 16:44:26 I think this section is actually for assigned the editors. 16:44:36 s/assigned/assigning/ 16:45:57 yes, your right. Any way I've got #13 and you have #81. I'll take 82 16:46:07 I guess 82 should go out Monday. 16:46:47 I probably ought to have zinebot automatically show the editor for the cards when we get to this section. 16:46:58 β‹„ card 82 editor 16:46:58 editor: @rlengland 16:47:15 β‹„ card 81 editor 16:47:15 editor: @glb 16:47:27 Looks good. πŸ™‚ 16:48:15 β‹„ list 16:48:21 #info 013: VNC Server in Fedora Linux (author: lruzicka) (fpca: signed) (status: to-edit) 16:48:22 #link status: https://pagure.io/fedora-magazine-newsroom/issue/13 16:48:23 #link preview: https://fedoramagazine.org/?p=35875&preview=true 16:48:23 #info 082: [Fedora Test Week] Fedora Kernel 5.16 from 2022-01-23 through 2022-01-29 (author: sumantrom) (fpca: signed) (status: to-edit) 16:48:23 #link status: https://pagure.io/fedora-magazine-newsroom/issue/82 16:48:23 #info 081: Using Quarkus and Mutiny to write Java asynchronous code (author: daveome) (fpca: signed) (status: to-edit) 16:48:23 #link status: https://pagure.io/fedora-magazine-newsroom/issue/81 16:48:24 #link preview: https://fedoramagazine.org/?p=35869&preview=true 16:48:45 I take that back. 82 (test day) should go out Sunday (if you can manage it) since that is when the test week begins. 16:49:18 We won't need to run anything Monday though since we ran something on Sunday instead. 16:49:44 I figure ASAP Whne 82 shows up I'll push it out 16:50:00 Or that. πŸ™‚ 16:51:48 β‹„ next topiic 16:51:56 β‹„ next topic 16:52:03 #topic 5/ publishing schedule 16:52:04 #info Looking at the 'to-edit' column, decide the publishing schedule for the upcomming week. 16:52:05 #info If there is not enough content, we might also need to look at the 'in-progress' or even the 'ideas' columns come up with additional content. 16:52:05 #link board: https://pagure.io/fedora-magazine-newsroom/boards/articles 16:52:05 #info 013: VNC Server in Fedora Linux (author: lruzicka) (fpca: signed) (status: to-edit) 16:52:05 #link status: https://pagure.io/fedora-magazine-newsroom/issue/13 16:52:06 #link preview: https://fedoramagazine.org/?p=35875&preview=true 16:52:06 #info 082: [Fedora Test Week] Fedora Kernel 5.16 from 2022-01-23 through 2022-01-29 (author: sumantrom) (fpca: signed) (status: to-edit) 16:52:07 #link status: https://pagure.io/fedora-magazine-newsroom/issue/82 16:52:08 #info 081: Using Quarkus and Mutiny to write Java asynchronous code (author: daveome) (fpca: signed) (status: to-edit) 16:52:08 #link status: https://pagure.io/fedora-magazine-newsroom/issue/81 16:52:10 (need a spell checker on zinebot) 16:52:23 I'll leave that one to you. πŸ˜› 16:53:02 13 tomorrow, 82 Sunday, 81 Wednesday or Friday? 16:53:16 Sounds good to me. πŸ™‚ 16:53:35 81 is yours how is your schedule? 16:53:48 Wednesday should be fine. 16:55:00 β‹„ show proposed 16:55:00 #proposed PUBLISHING SCHEDULE: Fri 21 Jan 2022: #13 VNC Server in Fedora Linux (editor: @rlengland) β€– Mon 24 Jan 2022: #82 [Fedora Test Week] Fedora Kernel 5.16 from 2022-01-23 through 2022-01-29 (editor: @rlengland) β€– ??? ?? ??? ????: #81 Using Quarkus and Mutiny to write Java asynchronous code (editor: ) 16:55:04 +1 16:55:29 Assuming the question marks mean Wednesday. πŸ™‚ 16:56:40 That's interesting. Pagure shows the data for 81 but zinebot didn't pick it up. Timing issue? 16:56:55 Oh yeah. 16:56:58 shall I try that again? 16:57:15 Actually, I'm not sure. 16:57:38 I didn't think that should be running from cached data. 16:57:58 Go ahead and try again. 16:58:02 β‹„ show proposed 16:58:03 #proposed PUBLISHING SCHEDULE: Fri 21 Jan 2022: #13 VNC Server in Fedora Linux (editor: @rlengland) β€– Mon 24 Jan 2022: #82 [Fedora Test Week] Fedora Kernel 5.16 from 2022-01-23 through 2022-01-29 (editor: @rlengland) β€– ??? ?? ??? ????: #81 Using Quarkus and Mutiny to write Java asynchronous code (editor: ) 16:58:13 How about if you run the list command? 16:58:22 β‹„ list 16:58:32 #info 013: VNC Server in Fedora Linux (author: lruzicka) (fpca: signed) (status: to-edit) 16:58:32 #link status: https://pagure.io/fedora-magazine-newsroom/issue/13 16:58:32 #link preview: https://fedoramagazine.org/?p=35875&preview=true 16:58:33 #info 082: [Fedora Test Week] Fedora Kernel 5.16 from 2022-01-23 through 2022-01-29 (author: sumantrom) (fpca: signed) (status: to-edit) 16:58:33 #link status: https://pagure.io/fedora-magazine-newsroom/issue/82 16:58:33 #info 081: Using Quarkus and Mutiny to write Java asynchronous code (author: daveome) (fpca: signed) (status: to-edit) 16:58:34 #link status: https://pagure.io/fedora-magazine-newsroom/issue/81 16:58:34 #link preview: https://fedoramagazine.org/?p=35869&preview=true 16:58:36 I'll have to fix that if it is pulling from the cache instead of directly from Pagure. 16:59:06 β‹„ show proposed 16:59:06 #proposed PUBLISHING SCHEDULE: Fri 21 Jan 2022: #13 VNC Server in Fedora Linux (editor: @rlengland) β€– Mon 24 Jan 2022: #82 [Fedora Test Week] Fedora Kernel 5.16 from 2022-01-23 through 2022-01-29 (editor: @rlengland) β€– Wed 26 Jan 2022: #81 Using Quarkus and Mutiny to write Java asynchronous code (editor: @glb) 16:59:19 Yep. It looks like that is the problem. 16:59:23 I'll get that fixed. 16:59:25 +1 16:59:30 +1 16:59:48 β‹„ show agreed 16:59:49 #agreed PUBLISHING SCHEDULE: Fri 21 Jan 2022: #13 VNC Server in Fedora LinuxπŸ”Έ (editor: @rlengland) β€– Mon 24 Jan 2022: #82 [Fedora Test Week] Fedora Kernel 5.16 from 2022-01-23 through 2022-01-29πŸ”Έ (editor: @rlengland) β€– Wed 26 Jan 2022: #81 Using Quarkus and Mutiny to write Java asynchronous codeπŸ”Έ (editor: @glb) {πŸ”Ή=β€―forum calendar update succeeded, πŸ”Έ=β€―forum calendar update failedβ€―} 17:00:10 Hmm, it is failing to update the forum. 17:00:36 This is the first time we've had something for it to actually try to post. 17:01:04 One of us should update the forum calendar manually. 17:01:17 And I'll have to figure out why that didn't work. 17:01:40 I'm EOW so I guess that would fall to me. πŸ™‚ 17:02:11 We're out of time 17:02:23 Wow that went fast. 17:02:28 β‹„ next topic 17:02:28 #topic 6/ editor of the week 17:03:11 more crickets. πŸ™‚ 17:03:19 OK. I'll do it. πŸ™‚ 17:03:30 β‹„ king glb 17:03:31 #info glb will be editor of the week starting Sun 23 Jan 2022 17:03:43 β‹„ next topic 17:03:44 #topic 7/ open floor 17:03:49 nada here 17:04:16 Jim Hall will be posting some bogus article proposals in the coming weeks. 17:04:40 He has a class doing a usability study on Fedora Magazine's workflow. 17:04:58 okay. How will we know them? 17:05:28 He said he would put a note in the proposals and dummy articles so we could identify them. 17:05:47 okay 17:05:47 I guess we are supposed to just leave them alone for the most part. 17:06:13 clean up on aisle 7 hten πŸ™‚ 17:06:30 I guess we should go 17:06:51 Good meeting. You'll have to do it again sometime. πŸ™‚ 17:06:54 β‹„ next topic 17:07:17 Trying to change the topic huh. 17:07:18 How is your schedule for next week? πŸ™‚ 17:07:30 It's pretty open. 17:07:44 #endmeeting 17:08:16 I'm slightly busier than usual because the semester just started. But it hasn't been bad so far. 17:08:29 I wonder why zodbot isn't responding. 17:08:37 Do you want me to give it a try? 17:08:50 #endmeeting 17:09:30 Thanks for coming to the rescue misc. πŸ™‚ 17:09:36 didn't work tho :( 17:09:56 It might be because you aren't on the list of chairs. 17:10:01 #chair misc 17:10:01 Current chairs: glb misc rlengland theevilskeleton zinebot zinebot[m] 17:10:45 #endmeeting