Staff Editors Discussion

• proposal was introduced to have staff editors to be responsible for editing all products from WG
  • this would include Newsletter, EPA, and Client Services
  • Assignments will be asked to complete editing tasks based on deadlines and subject matter
• Reason for proposal is to prevent friction with finding last minute editors for CS or Newsletter pieces. Also to improve quality of published content for EPA.
• This would change the workflow of the EPA. Not so much for CS and Newsletter. They would use the EPA for editors if necessary.
  • Some pushback on Newsletter and CS using staff editors. Then everything would flow through the EPA, isn’t that centralizing all writing?
  • It sounds like Frank and Sidd would prefer to have set, established editors to work on pieces for CS and Newsletter so they can avoid doing those tasks themselves.
• Implement, y/n?
  • there are 2 polls concerning this topic, results can be found here to implement staff editors and here for salary to pay staff editors
• Who wants to be a staff editor? How many staff editors should there be? Should we have some kind of voting process?
  • If you want to be a staff editor, please add your name here:
    • links: I’m interested, depending on time commitment
    • Trewkat
    • Ap0ll0 will refrain from being a staff editor since he’s already a role holder. He’s doesn’t want to monopolize any potential earnings that others could earn.
  • If you want to be a mentee of a staff editor, please add your name here:
• Payment structure
  • Set seasonal salary or per-article? Or some kind of hybrid?
    • links: personally in favour of a hybrid model - pay per article and have a smaller seasonal salary for mentoring
  • Nonsense believes we should still function in the way we intended when we submitted our funding requests
    • But start to implement this new workflow to determine a fair remuneration rate - based on workload
• Workshops, mentorships, and up-skilling new editors.
• How will staff editors manage their editing flow? Content and copy editor flow, like we’ve been doing? Or something completely different?