+1
I especially like the bulleted list at the end. I was never quite sure what
my duties were as an editor. Also, sorry that I haven't been around for a
while. I'll try to volunteer for a week sometime in the near future. Maybe
I'll even find some time to write up a few articles for the Magazine.
On Mon, Jun 8, 2020 at 3:40 PM Ben Cotton <bcotton(a)redhat.com> wrote:
Hi Magazine team,
As discussed in last week's meeting, I've drafted a proposal for the Editor
of the Week:
https://fedoraproject.org/wiki/User:Bcotton/Magazine_Editor_of_the_Week
The idea is two-fold:
1. Ensure tasks don't fall through the cracks by having an assigned person
2. Spread the load by rotating the assignee on a weekly basis
FESCo uses a similar model. At the end of each meeting, they select a chair
for the following week's meeting. It's also like how Fedora Infrastructure
(and many other sysadmin teams) handle on call duties.
I explicitly did not address the question of how we promote people to
Editor (or remove inactive Editors), because that's a separate discussion.
For the purposes of this proposal, we have an editorial team that people
become a member of *somehow*.
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
Fedora Magazine mailing list -- magazine(a)lists.fedoraproject.org
To unsubscribe send an email to magazine-leave(a)lists.fedoraproject.org
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@lists.fedoraprojec...