Communication Tagging

****NOTE: Andrea wrote a post about tags and beat me to the publish button by one minute. I’m publishing this anyway because it addresses more than one thing and has shorter tag suggestions. People can comment on either post and we’ll collate responses.****

One of the things we need to do prior to getting the new deputiesProgram Supporter Community Program Supporters (formerly Deputies) are a team of people worldwide who review WordCamp and Meetup applications, interview lead organizers, and keep things moving at WordCamp Central. Find more about program supporters in our Program Supporter Handbook. rolled into the day to day work is to agree on a better system of triage. Using tags to identify what’s needed on a supportpress ticket is analogous to using tags on coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets to indicate what’s needed.

Consider a core tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket. It has:

  • a component like “widgets”
  • a priority like “normal” or “high” (how important is this compared to other things we have to do)
  • a severity like “normal” or “high” (are things broken/at a standstill until this is dealt with, or is just something we should do)
  • a milestone (this release? a future release? we haven’t decided yet?)
  • an assigned person that will take responsibility
  • keywords that indicate what needs to happen next, like “needs-patch,” needs-testing,” or “2nd opinion”

I propose that in supportpress, we start tagging with components, priority, assigned person, and keywords instead of the current methed of tagging with people’s names. As we distribute tasks this will make it easier for people to find the tickets they need to address.

Component: Tags that would make sense here are probably the part that we need to think about the most, but to start, I’d suggest payment, swag, application, budget, sponsors, speakers, venue, and insurance to start.

Priority/Severity: I suggest we only have one tag around this, urgent, intended to call up things that have an extremely time-sensitive nature (based on shipping times, payment deadline, WC happening that weekend, etc).

Keywords: What needs to happen. needs-review, needs-vetting, vetted, etc. This area is where the most work needs to be done to identify the states of an issue.

Suggestions for more or different tags welcome.

#applications, #community-management, #process, #supportpress, #tagging