Skip to content
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

Adopt Storage Access API as a deliverable #2

Closed
hober opened this issue Jan 17, 2020 · 6 comments
Closed

Adopt Storage Access API as a deliverable #2

hober opened this issue Jan 17, 2020 · 6 comments
Labels
interest: blink Implementer interest from Blink (e.g. Brave, Google/Chrome, Microsoft/Edge) interest: gecko Implementer interest from Gecko (e.g. Mozilla/Firefox, Cliqz) interest: webkit Implementer interest from WebKit (e.g. Apple/Safari, Igalia/GNOME Web) repository? Request to create a repository where we can work on an explainer for this proposal work item? Formal request to adopt this proposal as a Work Item of the CG

Comments

@hober
Copy link
Member

hober commented Jan 17, 2020

I propose we adopt the Storage Access API as a deliverable of the Community Group. It would facilitate discussion to have a separate repository for it, instead of trying to iron out all of the details in one issue thread at whatwg/html#3338.

The end goal would be to land pull requests in the HTML Standard and other applicable specifications.

@hober hober added agenda+ Request to add this issue to the agenda of our next telcon or F2F needs implementer interest Proposals cannot become work items without multi-implementer interest work item? Formal request to adopt this proposal as a Work Item of the CG labels Jan 17, 2020
@hober
Copy link
Member Author

hober commented Jan 17, 2020

WebKit is supportive of this work and of doing this work here.

@erik-anderson
Copy link
Member

Microsoft is supportive of adopting this as a deliverable. We are doing work in Chromium involving this API.

@hober hober added repository? Request to create a repository where we can work on an explainer for this proposal and removed needs implementer interest Proposals cannot become work items without multi-implementer interest labels Jan 17, 2020
@TanviHacks
Copy link
Member

Mozilla is supportive of adopting the Storage Access API. It was implemented and shipped in Firefox more than a year ago.

@hober
Copy link
Member Author

hober commented Jan 20, 2020

I propose we appoint @johnwilander editor for this deliverable, assuming we adopt it.

@hober hober removed the agenda+ Request to add this issue to the agenda of our next telcon or F2F label Feb 3, 2020
@hober
Copy link
Member Author

hober commented Feb 4, 2020

We've adopted this as a deliverable! I've updated the charter in privacycg/privacycg.github.io@872aff4

@hober hober closed this as completed Feb 4, 2020
@hober
Copy link
Member Author

hober commented Feb 4, 2020

With interest from three implementers and the merging privacycg/privacycg.github.io#1, this is done. Drafting and discussion of the Storage Access API should now happen in https://github.com/privacycg/storage-access/

@hober hober added interest: webkit Implementer interest from WebKit (e.g. Apple/Safari, Igalia/GNOME Web) interest: blink Implementer interest from Blink (e.g. Brave, Google/Chrome, Microsoft/Edge) interest: gecko Implementer interest from Gecko (e.g. Mozilla/Firefox, Cliqz) labels Apr 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
interest: blink Implementer interest from Blink (e.g. Brave, Google/Chrome, Microsoft/Edge) interest: gecko Implementer interest from Gecko (e.g. Mozilla/Firefox, Cliqz) interest: webkit Implementer interest from WebKit (e.g. Apple/Safari, Igalia/GNOME Web) repository? Request to create a repository where we can work on an explainer for this proposal work item? Formal request to adopt this proposal as a Work Item of the CG
Projects
None yet
Development

No branches or pull requests

3 participants