Re: CfC: transfer "Manifest for Web Applications" specification to WebApps WG; deadline 20th May

On Monday, May 13, 2013 at 6:55 PM, Mounir Lamouri wrote:

> As discussed during the SysApps F2F in April, we tried to push the idea
> of a join task force between WebApps and SysApps to work on some topics
> like the Manifest and the Runtime specifications. During the WebApps F2F
> this proposal has been exposed to the group (thank you Jonas) and the
> conclusion was that the WebApps group isn't interested in the Runtime
> specification but is quite interested in the Manifest one. They also
> prefer to take ownership of the Manifest specification because a joint
> task force creates an overhead that participants and W3C administrators
> would prefer to avoid.
> The manifest is something that we want to push for the Web, as much in a
> browsing context than a web application runtime context and having this
> work in the WebApps working group is going to help getting traction and
> implementations. Keeping this work in SysApps will probably make the
> manifest seen as "application only" simply because most of our work is
> being done in that context.
> By transferring this specification to the WebApps working group, this
> group will accept to give the ownership of the specification to the
> WebApps working group and make any further work on this specification
> happen in this working group. If the group accept to transfer the
> specification, the final decision will still be pending on the CfC that
> will have to happen in the WebApps WG to take the ownership of it.
> If you have any comments or concerns about this CfC, please reply to
> this e-mail by May 20 at the latest. Positive response is preferred and
> encouraged, and silence will be considered as agreement with the proposal.

I support moving the manifest to WebApps. 

Marcos Caceres

Received on Monday, 13 May 2013 17:59:24 UTC