Speaking personally, I am delighted to see this initiative happen, and
I very much hope that it will be successful. As someone who has been
heavily involved in standards over the past decade, I am more than
happy to help make it a reality.
I don't think that this here group has to come up with any
particularly strong political position on specific topics. Adopting a
political position would require finding consensus on this list,
having someone represent it there, and then circle back in case
feedback on the WG's list brings up aspects that could cause the
consensus position here to change. It seems like a recipe for
frustration.
Instead, I think that this list could become a voice for developers
stating for a given problem that "this is what we want to do, and this
is one way we think it could be done". For people writing standards,
understanding use cases and usage patterns is key. Sorting out the
dirty details can (and should) happen over there. In W3C groups, there
are often people advocating the voice of developers, usually in good
faith. But those voices can be wrong, and do not have the clout and
reach that jQuery has. That is definitely an area where I hope that
this gang will help.
Speaking more specifically as chair of the Device APIs WG, if you have
input of any kind, be it feedback on existing stuff or proposals for
new things that can be done with native code but not yet on the Web,
send it! You're the people we're working for, so if you want things
done your way, speak up!
--
Robin Berjon