Publish as a Note

[mmccool]

• Update to reflect needs of 2021 May 1 drafts
• Resolve all outstanding issues, e.g. Oauth2, discovery/directory recommendations, etc.
• Publish as a note aligned with second charter publications
• Update links from other documents

[mmccool]

• Regarding links, we can avoid linking to it directly and continue to link from the security document
• Alternatively, we can fold the content into the security and privacy considerations doc (the idea was to have a separate shorter document that we could update more frequently, but since we have NEVER published this doc...)... if no other decision, should continue with the existing plan, but that means we need to do the initial publication of THIS document, at least once, then updates will be easy.
• Short URL should be wot-security-best-practices (consistent with the repo; Phillipp, McCool concur); a shorter form like wot-security-bp might also be useful (Kaz suggestion), however (note the other document is wot-security)

[mmccool]

Let's aim to have a resolution at the F2F to publish. F2F wiki updated with discussion and call for resolution. We need to have a draft ready two weeks in advance. To meet that for a June 21 first meeting, we should aim to announce the availability of the Draft on June 2 (next week... not really feasible... hmm).

[mmccool]

TPAC/vF2F is in mid-late October; so we should aim for a ready-to-publish draft by end of September, e.g. 1mo from now... or four meetings.