Skip to content
This repository was archived by the owner on Feb 18, 2025. It is now read-only.
This repository was archived by the owner on Feb 18, 2025. It is now read-only.

Need a better email answering solution #19

@carols10cents

Description

@carols10cents

The problems I'm hoping to solve are:

  • We lose track of some emails and never respond to them because there isn't visibility into what emails we've gotten and whether we've responded to or not
  • We also lose track of emails because no one is "assigned"
  • In some cases we've responded too much, or with conflicting information, because it seems like a quick response that someone can just handle but then it turns out we have some discussion to do that we should have taken before responding

What I'm imagining is:

  • Email to core@ comes in and gets added to some sort of tracking system automatically (GitHub issue in a private repository?)
  • (if it's garbage someone can just delete it)
  • We can discuss asynchronously who should respond with what, if there seems to be enough consensus (auto checkboxes? if 3 thumbs up and no thumbs down after 72 hrs, then sending is ok?), someone can take the initiative to respond
  • In triage meetings, we check in on anything stuck in this system
  • Permissions can be synced with GitHub+the teams repo

is this... Salesforce? ZenDesk? It feels customer-support-ey.

Crates.io also needs this functionality, and I'd love for both core and crates.io to use the same mechanism. I'm tracking my investigations for crates.io over here.

Metadata

Metadata

Labels

A-periodic-checkinsItems which we periodically check in on at a slower timeline (i.e. stuff that's blocked externally)M-triageTopic for the Core Team weekly triage meetingpausedThis agenda item is "paused" until the responsible person has an update

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions