Re: [w3c/manifest] Status report and planning for TPAC 2021 (#999)

Hey WebApp Manifest folks. @xeenon and I are co-chairs of the [WebExtensions Community Group](https://www.w3.org/community/webextensions/). We're a relatively new CG focused on seeking alignment between  various stakeholders in the browser extension space in order to pave the way toward standardization.

The first major project we're tackling is a (rough) specification of the manifest.json file used by various browsers. As such, we are very interested in meeting with you to learn more about how you work, your experiences in this space, and any recommendations you have to help guide us in our work.

If you are open to it, the [TPAC guidebook page](https://www.w3.org/Guide/meetings/tpac.html) seems to indicate that we should either be targeting a joint session or a dedicated breakout session. 

If we were to do a joint session, I think we should focus on

* The process used to create the initial drafts of the WebApps Manifest specification.
* How changes are introduced to the WebApps Manifest spec.
* Technical issues related to manifest specification.
* Lessons learned and recommendations to help guide our manifest specification efforts.

If we were to do a breakout session, I think it may be useful to focus on the current state of specifying well structured JSON files for use in web browsers. Based on reading a few specific issues in this repository, it seems like the current tools available for specifying how browsers should parse and handle errors in large JSON objects are lacking. At the moment the only well defined JSON files I'm aware of are our respective manifests, but this seems like it may be a topic of general interest and use for the broader web community.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/999#issuecomment-919494457