W3C home > Mailing lists > Public > public-webplatform@w3.org > February 2013

Re: draft blog post

From: Chris Mills <cmills@w3.org>
Date: Thu, 7 Feb 2013 14:11:40 +0000
Cc: public-webplatform@w3.org
Message-Id: <25DBF84A-B39F-407F-BB47-773F1EA653CD@w3.org>
To: Doug Schepers <schepers@w3.org>
Thanks Doug - I've fixed all of these except the title. I like the title, because I think it sounds human and down to earth, and not too stuffy and academic. I just like the comma, and don't think it sounds clumsy. 

Chris Mills
Opera Software, dev.opera.com
W3C Fellow, web education and webplatform.org
Author of "Practical CSS3: Develop and Design" (http://goo.gl/AKf9M)

On 7 Feb 2013, at 14:00, Doug Schepers <schepers@w3.org> wrote:

> Hi, Chris-
> 
> A few more comments...
> 
> * "How we’re working, at WebPlatform.org"
> This seems clumsy to me... I don't know if it's the comma, or what. Maybe "Workflow at Web Platform Docs" or "Getting Stuff Done at Web Platform Docs", or just removing the comma.
> 
> * "discussion methods"
> This link leads to [TEST:discuss]. Please move this page into the WPD namespaces, and link to it from [WPD:Index].
> 
> * "including IRC, and a mailing list"
> Remove comma. Add link to mailing list archives.
> 
> * "regular weekly meetings." ->
> "regular weekly community meetings, simultaneously held on teleconference and IRC."
> 
> * "such as announcing Doc Sprints" ->
> "such as announcing in-person Doc Sprints"
> 
> * "with subtasks." ->
> "with subtasks and people assigned to complete them."
> 
> * "The next Doc Sprint we have coming up is in Berlin, Germany" ->
> "The next Doc Sprint we have coming up is in Berlin, Germany, this week"
> 
> Regards-
> -Doug
> 
> On 2/7/13 6:47 AM, Chris Mills wrote:
>> Cheers  Peter - these were all great suggestions, and I've included
>> most of them verbatim.
>> 
>> The post is now published - see
>> http://blog.webplatform.org/2013/02/how-were-working-at-webplatform-org/
>> 
>> Chris Mills Opera Software, dev.opera.com W3C Fellow, web education
>> and webplatform.org Author of "Practical CSS3: Develop and Design"
>> (http://goo.gl/AKf9M)
>> 
>> On 6 Feb 2013, at 16:27, Peter Lubbers <peterlubbers@google.com>
>> wrote:
>> 
>>> Looks good, Chris. Some very minor suggestions for tightening up
>>> the content. Feel free to ignore!
>>> 
>>> Consider changing Moving forward with the huge amount of content
>>> we’ve got was always going to be a challenge, especially as we are
>>> but a few people, with a finite amount of time, many of us
>>> volunteers. To: We knew it would be challenging to deal with this
>>> much content, especially as we are mostly volunteers with only a
>>> finite amount of time.
>>> 
>>> Consider changing We’ve already achieved much, working towards our
>>> goal of making WebPlatform.org the definitive client-side web
>>> technology documentation site. But there is still much more to do,
>>> which is why we opened it up to the wider community as an alpha.
>>> To: We’ve already achieved much, working towards our goal of making
>>> WebPlatform.org the definitive client-side web technology
>>> documentation site, but there is still much more to do. That is why
>>> we opened the site up to the wider community as an alpha. (The bold
>>> "the" looks a little weird. consider italic)
>>> 
>>> Consider paragraph break before "The plan was always"
>>> 
>>> The sentence The plan was always to include the public as early as
>>> possible, so more folks can join in and contribute. The web does
>>> after all belong to all of us, and this is going to be such a great
>>> tool, which will be useful to so many! does not read well How about
>>> simply: The plan has always been to include the public as early as
>>> possible. The web does, after all, belong to all of us.
>>> 
>>> The text "For a start, we" leads me to think there will be a "Next,
>>> we..." but it just becomes the bulleted list. Maybe just remove the
>>> "For a start."
>>> 
>>> Tighten the first bullet: To make the work more manageable, we have
>>> started to split it into chunks, and then work on each in turn,
>>> moving on to the next task when we have finished each one. Sounds
>>> obvious, but it is so easy to become bogged down when you have so
>>> much work to do. Maybe something like this: To make the work more
>>> manageable, we have started to split it into manageable chunks and
>>> we work on each item in turn. Sounds obvious, but it is so easy to
>>> become bogged down when you have too much work to do. PL: Not sure
>>> the last sentence "Sounds obvious..." adds very much. consider
>>> dropping it.
>>> 
>>> Drop comma in "who is working on each task, at"
>>> 
>>> Stray bullet: * Get on with the tasks!
>>> 
>>> Consider rewriting: We have a plan to get most pages relating to
>>> these major areas sorted out in the next 2-3 months, but we need
>>> your help! To: Our plan is to perfect the topic pages for these two
>>> major areas over the next two to three months. This is where you
>>> come in!
>>> 
>>> Consider changing: bits of work To: focus areas
>>> 
>>> 
>>> Regards, --Peter
>>> 
>>> 
>>> On Wed, Feb 6, 2013 at 5:17 AM, Chris Mills <cmills@opera.com>
>>> wrote: Hi all,
>>> 
>>> I've put a draft of my webplatform blog post up at
>>> http://blog.webplatform.org/?p=180&preview=true (How we're working,
>>> at WebPlatform.org)
>>> 
>>> Ok to publish this today or tomorrow?
>>> 
>>> Chris Mills Opera Software, dev.opera.com W3C Fellow, web education
>>> and webplatform.org Author of "Practical CSS3: Develop and Design"
>>> (http://goo.gl/AKf9M)
>>> 
>>> 
>>> 
>> 
>> 
> 
Received on Thursday, 7 February 2013 14:11:56 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:57:39 UTC