Re: Getting stuff done at W3C

On 9 September 2016 at 03:02, Manu Sporny <msporny@digitalbazaar.com> wrote:

> Hey folks,
>
> Here's a blog post that might be useful to folks in this group regarding
> getting stuff done at W3C.
>
> https://manu.sporny.org/2016/rebalancing/
>
> Of particular note is the "W3C Working Group Formation Checklist":
>
> http://manu.sporny.org/2016/rebalancing/#checklist
>
> While this isn't an official W3C checklist, I've found that doing things
> in this order helps you survive the W3C process:
>
> 1. Clearly identify and articulate a problem statement.
> 2. Gather and document use cases.
> 3. Perform a gap analysis.
> 4. Produce a proposed architecture and technical specification.
> 5. Produce two implementations and a test suite.
> 6. Create a draft charter for a Working Group.
> 7. Create an executive summary for W3C member companies.
> 8. Survey organizations and demonstrate that at least 35 of them are
>    supportive of the work and technical direction.
>
> We should figure out what we want the work streams to be in this group
> first. There seems to be rough consensus that "Chainpoint" would be
> interesting.
>

I think there's a great solution to help this.

So the premise is that W3C staff are busy, and that resource shortage leads
to less standarization work.

I think the problem here is W3C staff wearing too many hats.

1. One hat is to guide the standards process
2. One hat is to guide standards technically
3. One hat is to predict paths to adoption

I think W3C staff should stick to (1) in as neutral a way as possible, and
leave (2) and (3) as much as possible to the WG or CG, freeing up their
time.  (


>
>
> -- manu
>
> --
> Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
> Founder/CEO - Digital Bazaar, Inc.
> blog: Advancing the Web Payments HTTP API and Core Messages
> https://manu.sporny.org/2016/yes-to-http-api/
>
>