"Open Questions" feature on vulnerability/1 page

[andymeneely]

One of the things that needs to be clearer is what we know and don't know about a given vulnerability. This would allow us to get a better "call to action" for answering an individual question instead of asking contributors to do an entire curation.

We have a list of open curation questions for each vulnerability - it's in the notes column, which is really just a copy of the yml file.

I haven't thought this through entirely. But it'd be nice if we had the ability to list the unanswered questions and then link to how to curate that particular question.

For example, you go might go to CVE-2017-5060 and have an "Open Questions" tab. You would see that How was this vulnerability discovered? was unanswered. You'd get links to instructions on how to curate that question.

What's next: let's mock up the interface first before we think about what should go in the database, etc.

[andymeneely]

Idea: what if the UI place for the open questions was like a "talk to a person" chat window like on the jellyfish.co website (or tons of others). Wouldn't be a "chat" window per se but the UI would present the open questions differently than just the tabs.

Or do we need badges?

Phrase to help the call to action:

• "Can you help us?"
• "Can you contribute?"
• "Can you donate 15 minutes of your time to curate?"

[ChristopherBanas]

A good "talk to person" window example https://www.wework.com/