...
Consider if it is “spam” - this is always a possibility and you may close the issue if it is. Add a comment saying it is spam.
Thank the person giving the feedback
Add a short comment to the issue saying thank you and give some indication of how the feedback will be reviewed
Drop an email to the person giving feedback. To obtain their email address, copy the code in the issue title and use base64decode.com to decode it to an email address. We encode the email addresses people supply so that they are not easily scraped by spam engines. We do, however, warn those submitting feedback that the email address they supply will be share with GovStack community members.
An example email text might be
Thank you for your feedback, we really appreciate your thoughts on this. You will see that we are tracking your feedback on our systems at xxxxxxxxx and we would very much like to give you credit for your contribution, unless you prefer otherwise? Are there any other ways in which we could collaborate? I would be happy to explain more how we developed the materials so far and how we work with many people to ensure they are relevant and impactful.
If you notice multiple items of feedback from the same person, you might want to consider inviting them to our Jira instance and then making them the reporter of the issue, rather than the default “GovStack Bot”. This is a key way in which we can draw more people into the project over time and then support further work on GovStack.
Process the issue and any change needed to the specifications
When an issue is finally closed, especially if it is closed with their comments added to the specification, make sure to say thank you once again. If they are engaging in the Jira issue, then that would be the right place, otherwise use their email address.
Supporting Building Block leads during a post-publication rush
In the weeks following a release of the specifications, it is possible that there would be a large influx of feedback that might overwhelm Building Block Leads. To assist them in their responsibilities, we will have a response team in place for four weeks following publication.
The response team will assist building block leads by:
Reviewing all incoming Jira issue feedback for spam and closing it
Review Jira issues and assess if they have been placed in the correct project, moving if necessary
Move any feedback issues that are not really related to the content of the specifications into the product-committee project and respond to them as required
Where an issue has a clear change that can be made, creating a change request and noting it in the Jira issue with a comment
Assigning issues to the Building Block Lead
Checking in with the Building Block Lead and ensuring they are able to respond with thanks to the person giving feedback