-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Horizontal Review: offer review opportunity to TAG #119
Comments
We will start this up when the document text is a little more coherent. |
Discussed on 2020-04-14: when the current §3 and §6 gets filled in (which means that the final structure of the document is in place), we can go out to get the horizontal review done. |
When ready, we need to create an issue here that will begin the TAG review. Note that we should have already completed the DID explainer and the PING security review and know whether we want them to respond with one issue in our repo for each point, one issue for all of their points, or to leave feedback as a comment to this new issue in their repo. |
Chairs have reached out to the TAG and asked them to review the spec. |
We had a preliminary discussion with TAG. We offered to meet with them to go over the specification. TAG is waiting on security/privacy questionnaire from us. |
The TAG issue we opened to request review from them has been updated with a link to the Security and Privacy Questionnaire |
TAG is meeting today (right after WG meeting) specifically about this, so you should hear more soon. |
TAG has indicated their review is complete: w3ctag/design-reviews#556 (comment) |
Horizontal review is complete, closing |
The chairs need to offer the Technical Architecture Group an opportunity to review if they wish, making clear that our group does not consider their input to be blocking for progress. In other words, our document will continue to progress whether we receive their input or not, but they are encouraged to give us any feedback they may have earlier in the process rather than later.
The text was updated successfully, but these errors were encountered: