search

w3c / push-api

Push API
https://w3c.github.io/push-api/
Other
145 stars 40 forks source link

Meta: wide-review tracker #265

Closed LJWatson closed 3 years ago

LJWatson commented 7 years ago

A11y: complete Issue #259 (closed)

I18n: complete Issues #276 (closed) and #275 (closed)

Privacy: completed.

Security: complete Issues #273 (closed) and #270 (closed)

TAG: complete (with comments)

LJWatson commented 7 years ago

@Beverloo @martinthomson what is your sense of time needed to resolve these (and any other critical issues, before we're ready to transition to CR? Once in CR it'll be possible to make editorial updates to the spec, but all substantive issues/features etc. will need to be included in a future update.

LJWatson commented 6 years ago

Ping @beverloo @martinthomson

martinthomson commented 6 years ago

@LJWatson, I think that we're still waiting on the conclusion to #287.

LJWatson commented 6 years ago

Thanks @martinthomson.

We also need to look at #270 and #275.

@beverloo, did you make the change arising from the Privacy review (" to clarify about UA deciding which push service to use.")? Thanks.

LJWatson commented 6 years ago

@martinthomson @beverloo loo it looks like #270 (from the security review) is still open, and that #287 is waiting for a response from one of you. Do you think we can get these wrapped up, so we can get the CR CFC out to the WG soon?

LJWatson commented 6 years ago

Ping?

martinthomson commented 6 years ago

Waiting on @beverloo.

marcoscaceres commented 3 years ago

Seems like everything got addressed.