W3C home > Mailing lists > Public > spec-prod@w3.org > October to December 2016

Re: New TR design in 2017?

From: Tobie Langel <tobie@codespeaks.com>
Date: Tue, 22 Nov 2016 17:28:07 +0100
Message-Id: <1479832087.3656080.795977561.5C940245@webmail.messagingengine.com>
To: Philippe Le Hégaret <plh@w3.org>, spec-prod@w3.org
Cc: Antonio Olmo Titos <antonio@w3.org>, fantasai.lists@inkedblade.net
On Tue, Nov 22, 2016, at 17:19, Philippe Le Hégaret wrote: 
> On 11/22/2016 11:04 AM, Tobie Langel wrote:
> > Hi all,
> >
> > First, thanks so much to Fantasai whose work really helped improve the
> > UX of using specs this past year. <3
> >
> > Secondly though, and sorry for ranting, but W3C is a standard org whose
> > main output is specs. That it relies on volunteering from members and IE
> > to improve the design of its specs is baffling. Making specs as easy to
> > consume as possible should be paramount.
> >
> > I'd like to see W3C put more resources in areas that actually matter to
> > itself, its community and the Web at large. If the UX of consuming its
> > specs isn't one of those, then what is?
> Right now, we have multiple things on our list: /TR pages (in progress), 
> /TR versioning (in progress), old drafts on /TR (aka SEO issue, no 
> progress), support for FPWD/CR in Echidna (won't happen for Q2 2017 at 
> least), documentation improvements everywhere (especially /Guide), 
> support for Process 2017 (needs to happen in Q1 2017). In terms of 
> systeam, my list contains things like better GitHub/W3C integration 
> (account, mirroring), ash-nazg enhancements, better office like tooling 
> (aka the google docs issue). I also need to provide a better management 
> of W3C TR milestones as part of the reorganization. Now, if the only 
> change we make in 2017 is your scroll proposal, that's something that 
> can be relatively easily handle by ourselves. However, thanks to 
> Fantasai, we just did a new design a few months ago so doing a new major 
> one is nowhere close to the top of my list at the moment.
> In addition, the W3C team has failed to update on /TR design for years 
> and this new /TR design process was designed to prevent that from 
> happening again. I'm a big believer in enabling the W3C community to 
> change W3C itself. That's why I push things off the internal W3C 
> repository into GitHub whenever I get the chance.
> Lastly, as strangely as it might sound, I'm far from convinced the W3C 
> team is the best at Web design (starting with myself :). I'd rather give 
> a chance to someone who is better at it.

Glad to see you have a lot of exciting and useful work lined-up for the
upcoming year.

I've enjoyed seeing you push more stuff in the open and applaud that
effort. I'm by no means suggesting the community shouldn't be able to
participate if it's able and wants to, but community help shouldn't
become a cop-out.

I'd really like to see W3C take UX more seriously. Especially in areas
which are critical such as specifications.

Received on Tuesday, 22 November 2016 16:28:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 22 November 2016 16:28:35 UTC