Project Documentation: About the Scope, Threat / Vuln, Accessibility

[quintessence]

As part of their application, projects will need to include:

• Scope - what problem area they are trying to solve, with an understanding of what does and does not fall in their intended scope
• Threat / Vuln Assessment; Mitigation - what projected misuse of their software might look like and what steps they are taking to protect against or otherwise prevent that misuse
• Accessibility Assessment; Inclusion - primarily this goes into the Sensory Abilities section of Accessibility (see Hachyderm docs). Essentially: can people with screen readers use their software and have a complete experience? If not, what are the drawbacks? Can people who utilize captions make use of their software and have a complete experience? If not, what are the drawbacks?

Although the initial statements about the above, they will need to be incorporated in a sustainable way over the lifetime of the project.

Process doc: Nivenly will need to have a statement about what we consider "minimum expectations" for these, as failure to comply with the minima might warrant a project to review. Basically: we need to make sure that there is actual compliance rather than written intent with no follow through.