Content Change request, Intake

[shawnthompson]

Context:

We have to establish a proper channel for all the intake, whatever the type of request is.

Current state:

They have the possibility to submit a request via Github,

• Broken link
• Bug
• Change request
• Feature request
• Other
• Report a security vulnerability
• They can also send an email to our generic mailbox, or to Shawn and I.

Issue:

We are missing a way to track properly the number of requests we get, when they are answered or not answered. When does it need to be an issue on github, or maybe a conversation or just a reply by email?

Solution:

To be determined

[shawnthompson]

I’d like it be 99% tracked on GitHub, if it’s a request via email, someone should create an issue to track the changes and let the person know it was created on GitHub

[shawnthompson]

Need to create a labelling taxonomy for types of request on GitHub and someone to label them properly