@chriskrycho The rfcbot lives in the dashboard repo, so issues there are definitely welcome, but it seems like this is a good place for discussing design of the bot (as opposed to the implementation).
My understanding (@aturon, please correct me if I’m wrong), is that the concerns should only be resolvable by the one who raised them, in order to ensure that the concern has been adequately addressed according to their original intentions. So I’m not sure how the bot should interact with the concerns based on messages from the RFC author – maybe if the bot is notified a concern has potentially been addressed, it could add it to the originator’s dashboard? It’d then need to post a comment pinging the concern’s author, letting them know they should look again.
Is that dashboard visibility significantly worth it to add the indirection over just directly pinging the concern’s author in a GH comment? Am I missing something here because I only just now finished my coffee?
