Re: Some Feedback On Our Developer Meetup

On Sunday, 16 June 2013 at 20:55, Charles McCathie Nevile wrote:

> On Thu, 06 Jun 2013 10:40:11 +1000, Marcos Caceres <w3c@marcosc.com (mailto:w3c@marcosc.com)> wrote:
>  
> > On Wednesday, 5 June 2013 at 23:08, Appelquist Daniel (UK) wrote:
> >  
> > > Some blogged feedback on our TAG developer meet-up from Bruce Lawson  
> > > and Jo Rabin that I think is worth reading:
> > >  
> > > http://www.brucelawson.co.uk/2013/i-met-the-tag  
> > > (http://www.brucelawson.co.uk/2013/i-met-the-tag/#comment-1507233)
> > >  
> > > http://jorabin.blogspot.co.uk/2013/06/meet-developer-yes-but-what-for.html
> > These are great, but it's quite sad that many in the dev community are  
> > still not seeing us as representing them here at the w3c :(
>  
> by "us" do you mean the TAG, a few people in the TAG, or…?

The TAG.   
> > We need to do a better job at communicating what we are doing - and
> > showing proof that we are being effective.
>  
>  
> Sure...
>  
> > This is why I argued that Promises and NavController should be seen as a
> > TAG deliverable (or an outcome of the TAG - I mean, 3 tag members, not
> > including me, worked together on those).
>  
>  
> I think that's a terrible "layering violation". I have worked on making  
> sure the web apps group can have good dinners, but I don't think that  
> means I should regard the dinner as an outcome of the group.


Yes, this was the conclusion at the last F2F actually. The TAG is good at identifying, and potentially kicking off, some work items.  

> > That will have real impact throughout the whole web platform
>  
> Yes.
>  
> > and is something the TAG could point to and say "see! we did something  
> > in collaboration with TC39 and others that directly helps a massive  
> > number of Web devs".
>  
>  
>  
> To which my reply would be "why on earth did you do this work in the TAG,  
> which actually should be working on other stuff, and not in a normal  
> working group which is where it belongs?"


Right, good at starting off work then handing it off to the appropriate WG. This is what is happening ATM.  
  
> > Other stuff the TAG has worked on is also important, but it's not so
> > directly in the hands of developers.
>  
>  
>  
> In some cases it isn't particularly *meant* to be in the hands of  
> developers. Helping different Working Groups choose design patterns for  
> APIs is really important work the TAG should be doing. The raw discussion  
> probably isn't even useful in the hands of developers, although the  
> results should be since developers also create APIs and the lessons are  
> relevant to them.

Yep.  
> > Also having the public list of APIs that are being reviewed/improved by  
> > the TAG would be a great thing…
>  
>  
> Yes.
>  
> > and maybe having some kind of voting system for people to tell us which
> > one we should review next would hep.
>  
>  
>  
> Also, some explanation of how you would choose the next one in the absence  
> of a voting system. (The TAG's purpose is not to be super popular, it is  
> to do some specific and important work).

Sure.   
> > We should also now start pointing people to GitHub… maybe w3c comms team  
> > can help tweet about some of this stuff. Their reach is pretty massive  
> > on twitter.
>  
>  
> Updating your webpage would be a good start.
>  

Web pages? Do people still use those? we should probably also make an iOS app, just to be safe:)

Received on Monday, 17 June 2013 07:04:08 UTC