W3C home > Mailing lists > Public > public-coord-mechanisms@w3.org > March 2015

W3C coordination mechanism across W3C communities

From: GALINDO Virginie <Virginie.Galindo@gemalto.com>
Date: Mon, 16 Mar 2015 17:37:33 +0000
To: "public-coord-mechanisms@w3.org" <public-coord-mechanisms@w3.org>
Message-ID: <540E99C53248CE468F6F7702588ABA2AD275612F@A1GTOEMBXV005.gto.a3c.atos.net>
Dear all,

A short debrief on the recent W3C AB F2F meeting. The project status [1] was presented to the Advisory Board early February and received some constructive comments from AB members. I suggested that I would follow up by interviewing some W3C chairs of different groups (including community groups) and some W3C leaders to collect their view on how to improve the information propagation (to and from their groups/activities).

One should note that there are parallel working lead by W3C office dealing with

-          Upgrading tools for publication of specifications (Ted G from system team leading)

-          Offering a generic API from W3C group activities to build dashboard (Ted G from system team leading)

-          Animating a web developer community - including specifiction on discourse managed by Robin Berjon today, and soon with Ian Jacob support


All those fail into the plan to improve the information propagation across W3C communities, and that is great news.

If you have any contribution/idea for progressing on that project, feel free to share here.

Regards,
Virginie Galindo
W3C AB member
Multi-chair and Gemalto representative

[1] https://www.w3.org/wiki/AB/2014-2015_Priorities/w3c_synchro_consistency_plan/Project_follow_up

________________________________
This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.
Received on Monday, 16 March 2015 17:38:03 UTC

This archive was generated by hypermail 2.3.1 : Monday, 16 March 2015 17:38:04 UTC