We should generally put everything on the list, but there's no reason the email can't go to you and cc the list; that works just as well! On Fri, Jun 19, 2020, 7:38 PM Gregory Bartholomew < gregory.lee.bartholomew@xxxxxxxxx> wrote: > I'm guessing the alternate would be whoever is on duty for that week -- > assuming that we go with Ben's new system. > > I think I'm pretty responsive (at least to email) as long as you are > outside of the midnight to 9 AM CST time frame (even on weekends). A tardis > would be nice though! :) > > On Fri, Jun 19, 2020 at 6:27 PM <s40w5s@xxxxxxxxx> wrote: > >> Greg's got a point about a single point of contact within the editorial >> circle so these announcements are always directed at the same one of us, >> and an alternate that would be needed for the what if's. I'm sure glb would >> need some slack in that regard, but maybe he has his own Tardis. Another of >> my 2 cents worth. >> >> Stephen >> On Fri, 2020-06-19 at 17:41 -0500, Gregory Bartholomew wrote: >> >> Maybe we should designate someone to handle these so there isn't a >> "scramble" to figure out who needs to do it? I'd be willing if they are as >> simple as they sound. My idea is that you would send the request directly >> to me rather than the list and then only if you don't get a response from >> me within 24 hours, you would send it to the list. Does that sound >> reasonable? >> >> Also, to prevent these from bumping other articles around on the >> schedule, maybe we should only publish them on non-normal publishing days >> (i.e. not Monday, Wednesday, or Friday)? >> >> Just a suggestion; there may be other concerns that I'm unaware of. >> >> gb >> >> On Fri, Jun 19, 2020 at 4:49 PM Paul Frields <stickster@xxxxxxxxx> wrote: >> >> Even a few days notice would be great. At worst we can keep doing what we >> have been, but it depends on someone to be around and able to react, and >> on >> the eve of a weekend that's not always possible. If we can avoid a >> scramble >> we should. On the other hand these articles are easier than most to push. >> >> On Fri, Jun 19, 2020, 4:13 PM <s40w5s@xxxxxxxxx> wrote: >> >> > Hello Sumantro, >> > >> > I am fine, thank you. I hope you are doing well too. >> > I am with Paul on this one. It was handled and has been in the past, >> > and likely will in the future. The problem for us is the Editorial >> > Board makes schedules for publishing/Editing/Reviewing/Image creation, >> > etc... that are parts of all the articles. When something is dropped in >> > at the 11th hour, it can create ... difficulties. I'd say 7 days would >> > be perfect notice for us, and if the desire is to get it into the next >> > publishing schedule, try to contact us before the Wednesday 0800 EST >> > meeting time of that publish cycle. I know your world is likely very >> > dynamic WRT the releases, so I do understand notice is not always there >> > but please try harder. >> > Best regards, >> > >> > Stephen >> > >> > On Fri, 2020-06-19 at 13:44 -0400, Paul Frields wrote: >> > > Sumantro, what could be done to increase the advance notice for these >> > > announcements? It seems like this has become the rule rather than the >> > > exception. >> > > >> > > >> > > Paul >> > > >> > > On Fri, Jun 19, 2020 at 12:49 PM Sumantro Mukherjee < >> > > sumukher@xxxxxxxxxx> wrote: >> > > > Hey All, >> > > > >> > > > Hope everyone is doing well. I would like to request if someone can >> > > > help me publish the >> > > > Kernel 5.7 Test Week Announcement? >> > > > The test week begins on Monday so, it will be great if someone can >> > > > help me with this right away :) >> > > > >> > > > https://fedoramagazine.org/wp-admin/post.php?post=31290&action=edit >> > > > >> > > > -- >> > > > //sumantro >> > > > Fedora QE >> > > > TRIED AND PERSONALLY TESTED, ERGO TRUSTED >> > > > _______________________________________________ >> > > > Fedora Magazine mailing list -- magazine@xxxxxxxxxxxxxxxxxxxxxxx >> > > > To unsubscribe send an email to >> > > > magazine-leave@xxxxxxxxxxxxxxxxxxxxxxx >> > > > Fedora Code of Conduct: >> > > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> > > > List Guidelines: >> > > > https://fedoraproject.org/wiki/Mailing_list_guidelines >> > > > List Archives: >> > > > >> > >> https://lists.fedoraproject.org/archives/list/magazine@xxxxxxxxxxxxxxxxxxxxxxx >> > > _______________________________________________ >> > > Fedora Magazine mailing list -- magazine@xxxxxxxxxxxxxxxxxxxxxxx >> > > To unsubscribe send an email to >> > > magazine-leave@xxxxxxxxxxxxxxxxxxxxxxx >> > > Fedora Code of Conduct: >> > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> > > List Guidelines: >> > > https://fedoraproject.org/wiki/Mailing_list_guidelines >> > > List Archives: >> > > >> > >> https://lists.fedoraproject.org/archives/list/magazine@xxxxxxxxxxxxxxxxxxxxxxx >> > >> > >> _______________________________________________ >> Fedora Magazine mailing list -- magazine@xxxxxxxxxxxxxxxxxxxxxxx >> To unsubscribe send an email to magazine-leave@xxxxxxxxxxxxxxxxxxxxxxx >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/magazine@xxxxxxxxxxxxxxxxxxxxxxx >> >> _______________________________________________ Fedora Magazine mailing list -- magazine@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to magazine-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/magazine@xxxxxxxxxxxxxxxxxxxxxxx
