The holiday period in December will be here before you know it. The Magazine has a lot of staff who are planning vacation and PTO time over that period. That doesn't mean everyone will automatically disappear. But in my case, I tend to spend my vacation away from the keyboard and doing other things. I bet some others do likewise. The hardest period to cover will be December 23 - January 1 -- which is 5 slots in our normal schedule. So we should figure out how to pre-fill our schedule and not have the Magazine "run dry" for several weeks. Here are some ideas for how we could accomplish this. But we need other ideas and content, too. Please contribute your ideas and we can discuss in the next meeting (Wednesday 1300 UTC, 8:00am EST, 2:00pm CEST in IRC Freenode #fedora-meeting). (1) If you're a new writer we would still love to have your contributions early, so we could schedule articles to publish over the holidays. (2) We could make a "best of 2019" series that would run for 3-5 slots on the Magazine. Last year I think we chose articles that represented for developers, sysadmins, and user tools. We could use those or even add a couple categories. We could do a year-end wrap up as well. (3) We could resurrect a few articles to refresh and repost. You can reset a published article to scheduled, and it will be re-posted on the new date. If we do this, the article should be checked for accuracy and updated as needed to reflect Fedora 31 reality. (4) We could get a bunch of like-minded writers to participate in a new series that we finish and schedule to run over the holidays. Other ideas are welcome. -- Paul _______________________________________________ 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
