W3C home > Mailing lists > Public > public-w3process@w3.org > May 2014

Re: Workshop and meeting requirements

From: Sylvain Galineau <galineau@adobe.com>
Date: Tue, 13 May 2014 17:37:42 +0000
To: "Michael Champion (MS OPEN TECH)" <Michael.Champion@microsoft.com>
CC: David Singer <singer@mac.com>, "public-w3process@w3.org" <public-w3process@w3.org>
Message-ID: <50D9C7B4-2D06-4B85-A80A-BEDF626BA07D@adobe.com>

On May 13, 2014, at 10:15 AM, Michael Champion (MS OPEN TECH) <Michael.Champion@microsoft.com> wrote:

> Thanks David, I think this is a good summary.  What I've taken from this discussion is that having not-quite-a-workshop events that are loosely affiliated with W3C can be valuable if that means:
> - W3C (somehow, either the staff or a social mechanism) vets the event to ensure that it is technical rather than marketing/political
> - W3C participants get advance notice via an online calendar, dedicated mailing list, whatever.
> - Organizers commit to publishing some sort of takeaway document - summary, points of consensus and disagreement, action items, etc.
Yes; advance notice and sharing the results are the two main guidelines for such events. I still can't quite figure out why events 'loosely affiliated with W3C' are a concern for the Process document, however. I have seen small subsets of the CSSWG meet outside regularly scheduled f2f meetings, sometimes very productively. While I'd like to remind people to advertise these meetings beforehand and make sure they share the results - e.g. including by using #css for minuting - this seems good charter material, not W3C Process.
Received on Tuesday, 13 May 2014 17:38:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:35:10 UTC