-
Notifications
You must be signed in to change notification settings - Fork 57
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
Performance Timeline #644
Comments
Thanks for bringing this to our attention (and sorry for the delay!) - we were curious if we could get a delta of the parts that we are supposed to review, so we don't nitpick at stuff that has already been shipped as CR. Thanks! |
As this is a Level 2, pointing out what changes were actually made would really help us. We might have comments to the existing parts of Level 1 but as those are shipping, looking at those parts is not the best use of our time. |
Hi @caribouW3 sorry but I think we really need to see an explainer here. The spec may be understood to the group working on it. However one of the points of "wide review" is that people who are unfamiliar with the spec review it (or at least review the delta) with fresh eyes. Can you please provide a little more info for us here? Otherwise we are going to close this as not satisfactory. |
I'm working on an explainer and will probably have it ready by next week. |
Explainer: https://github.com/w3c/performance-timeline/blob/gh-pages/explainer.md |
@cynthia and I looked though the changes and we don't have any concerns. Thank you for the explainer! |
Ya ya yawm TAG!
I'm requesting a TAG review of Performance Timeline.
This is actually a request to confirm or amend previous review, as requested in the CR transition
w3c/transitions#339 (comment)
This specification was originally developed in levels, Level 1 in REC in 2013,
Level 2 has had a wide review in 2016 before entering CR
https://www.w3.org/TR/2016/CR-performance-timeline-2-20161208/
There is no fundamental change to the goals of the spec. The processing model is more detailed and
data structure updated.
We plan to drop levels and use a living standard development model (from process2020).
We'd prefer the TAG provide feedback as (please delete all but the desired option):
🐛 open issues in our GitHub repo for each point of feedback
💬 leave review feedback as a comment in this issue and @-notify [github usernames]
Thank you!
The text was updated successfully, but these errors were encountered: