huntr Make our process obvious to maintainers

Artefacts

[ ] Create a step by step guide
[ ] Place it along their path (somewhere relevant and timely)

Core Success Measures

[ ] Maintainer that come and don't review -50%
[ ] Maintainer that come and don't confirm fix -50%

Additional Success Measures

[ ] Maintainers notice that there is a step by step guide (15% of new maintainers click this wiki)
[ ] The wiki is easy to understand (6/10 find it helpful)

May 18 '21 06:05 JamieSlome

Hi @JamieSlome, can you please groom this ticket. If we don't have a definition yet, feel free to leave it as a note until grooming.

May 20 '21 16:05 adam-nygate

@ehuelsmann @JamieSlome do you guys still think this is necessary?

Nov 11 '21 13:11 psmoros

I just checked the site (but not any security reports); the information that I need as a maintainer isn't there in a way that it allows me to find it quickly and provide me with a consistent understanding of my role in the disclusore process. I.e. there's no indication that rejected vulnerability reports will be immediately disclosed (and not stay private or archived); similarly, there's no indication that the effect of selecting a commit SHA (as a maintainer) will directly and immediately publish the vulnerability report. There's more, but maybe it's more practical to have an initial process outline published on the site after which I can comment more?