vague requirements

Date: 2017-03-24 08:09 pm (UTC)
From: (Anonymous)
There are at least a couple occurrences of vaguely defined requirements in the document. For example, "There should also be well-signed PGP keys to use when contacting these people in the event of a situation." How are you defining "should"? Will requests be rejected if there aren't keys? How are you defining "well-signed"?

I understand that each case is ultimately going to be handled individually, but ultimately it'll help applicants meet the expected quality bar if the bar is well defined.
From:
Anonymous
OpenID
Identity URL: 
User
Account name:
Password:
If you don't have an account you can create one now.
Subject:
HTML doesn't work in the subject.

Message:

If you are unable to use this captcha for any reason, please contact us by email at support@dreamwidth.org


 
Notice: This account is set to log the IP addresses of everyone who comments.
Links will be displayed as unclickable URLs to help prevent spam.

Profile

Matthew Garrett

About Matthew

Power management, mobile and firmware developer on Linux. Security developer at Google. Ex-biologist. @mjg59 on Twitter. Content here should not be interpreted as the opinion of my employer.

Expand Cut Tags

No cut tags