Skip to content

Latest commit

 

History

History
55 lines (39 loc) · 2.81 KB

TEAMS.md

File metadata and controls

55 lines (39 loc) · 2.81 KB
Raw

Defund12.org Team Organization

1. User that submits issue

Anyone who would like to add an email for their locale creates an issue in adherence to the email guidelines.

2. Triage Team

First to review newly created issues. Look over all issues with new-request label.

Responsibilities

Check for duplicates

  • Check if the issue is a duplicate of an existing request or existing template. In the Issues tab, search for the requested locale with is:open is:closed [LOCALE] to see if an open request or merged template already exists.
  • If the request is a duplicate, add the duplicate label and close the issue with a link to the earlier request

Check for completion

  • Check if issue has all required data
    • Does it meet basic data requirements?
      • Recipients (CC addresses)
      • Body text
    • If not, close issue and reply with the body of the email request template
    • If yes, add content-ready-for-review label and remove all other labels

3. Review, Editing, and Approval Team [Needs people!]

Ensure the email roughly adheres to email guidelines.

Responsibilities

  • If body content is not salvageable, close issue.
  • Is it good enough?
    • Does it have locale specific info?
    • Is the core statement in regards to defunding local police departments
    • Add ready-for-pr label and remove all other labels
  • Even though the issue is good enough and you added the ready-for-pr label, do you still think the email template needs work or editing?
    • Add email-needs-work label and leave comment with the outstanding tasks.

4. Email Addition Development Team

Pick up issues with the ready-for-pr label. Issues should only be assigned to a developer for ≤24 hours to ensure emails get added to the site quickly.

Responsibilities

  • Assign issue to yourself so no other developer begins working on it
  • Create a PR for the email issue
  • Ensure the email markdown is correct and properly linted.
  • Once PR is up, someone will review and merge!

Conventions to follow

  • Please refer to the Emails README with more information about email template conventions.

Join the conversation

If you'd like to help out, please join our Discord server. We’d love your help!

We have created channels in the Discord channel that correspond to each team. These will be used for team-specific communication and organization. Whichever team you'd like to join, please join the Discord appropriate channel and say hello.