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

Re: CSS or bust???

From: Julee <julee@adobe.com>
Date: Tue, 30 Apr 2013 13:31:03 -0700
To: Eliot Graff <Eliot.Graff@microsoft.com>, "public-webplatform@w3.org" <public-webplatform@w3.org>
Message-ID: <CDA57817.7312C%julee@adobe.com>
Hi, Eliot:

Funny you should bring this up. We talk a lot about it during the
community meeting today. You weren't there, so we decided it is, indeed,
all your fault! ;-)

Seriously tho, the CSS properties spreadsheet pivot table [1] shows Total
of 269 P0-P2 properties, 158 of which essentially have not even been
looked at.[1]

Reaching a milestone is always a matter of balancing time and resources
and features, right? So, yes, I think that there's a general understanding
that CSS properties should be in the beta. Here are just some of the
things that we're doing to address issues with Beta health. (This is on
the agenda item for our Friday meeting.[2])

1. We assigned project owners. Those owners should review the beta
criteria[3] and update it with what their "group" thinks should be in the
beta. We'll remind folks in the Friday meeting.

2. Beta criteria needs to be clarified at the higher level as well. For
example:

* CSS properties are probably a must
* For each content area, we should have exemplar content
* Each page should be clearly designated as either ready to consume or
needing additional contributions

3. We need to ensure that new contributors are properly supported. Julee
(that's me) will write up a plan for helping contributors with CSS
properties, including having a set times for content-wrangling.

4. The CSS properties sheet is overwhelming folks. Julee is going to
update it.

5. We need more folks vetting the content that's there. The community TF
will do a recruiting plan.

6. We need folks to work on content, especially CSS properties pages. We
may ask folks to own certain portions, to be divvied up amongst their
friends and family, or otherwise focus on that.

What you can do:

* If you're a project leader:
** discuss beta criteria with stakeholders and update the Project Status
page.
** make sure you have tasks and bugs relating to beta in
project.webplatform.org, and that they're assigned to someone.
** if you find blockers, file a bug, and broadcast it to the public list

* If you're an individual contributor:
** work on some CSS properties

** if you find blockers, file a bug, and broadcast it to the public list

Looking forward to feedback from all, especially for those who have
attempted to do a CSS property recently.

Regards.



Julee

[1] 
https://docs.google.com/spreadsheet/ccc?key=0AkRs-89PKiZpdE0xdm9Sb1ZvRW1ZRz
MtWEdyU0Z4OEE (Pivot Table 1)
[2] http://docs.webplatform.org/wiki/WPD:Community/Meetings/Content
[3] http://docs.webplatform.org/wiki/WPD:Project_Status


----------------------------
julee@adobe.com
@adobejulee





-----Original Message-----
From: Eliot Graff <Eliot.Graff@microsoft.com>
Date: Tuesday, April 30, 2013 12:37 PM
To: "public-webplatform@w3.org" <public-webplatform@w3.org>
Subject: CSS or bust???

>Hi All.
>
>[[Before I ask these questions, I want to say that I am as guilty of
>contributing to this as anyone, having recently introduced the 400+
>JavaScript pages in to the mix.]]
>
>Are we really placing our energies in the right places? Are we working on
>the right things? Or are we losing focus?
>
>I thoroughly understand that there are a _many_ important and wonderful
>aspects of WPD that we could be creating, enhancing, and building, but I
>think we may be drifting from our original decisions (and if not, this
>will serve as a verification of our course of action). I was under the
>impression that we determined that we would identify and work on one
>section of WPD at a time to get that area up to what we considered "beta
>content", and that we were going to do that starting with the CSS
>properties. We're not anywhere near complete on those, are we? If we are,
>I apologize, and carry on. But I look at the CSS Properties spreadsheet
>[1] and I see a ton of work left to go. Yet, over the past couple of
>weeks, we are all (myself included) very eager to start work on
>JavaScript reference, Beginner's Guide, DOM, and other large projects
>(I'm sorry to pick on these in particular).
>
>My call to this community is this: We should validate that our priorities
>are sound (from time to time) and strive to stay focused on our highest
>priority items prior to embarking on new work. In short, we need to hold
>ourselves accountable to our goals. Certainly, this is true while our
>community is still small but growing. Maybe later, when we're a robust
>and enormous group, we can have the luxury of being less strident.
>
>Can we reiterate (in mail or during upcoming telcons) what our priorities
>are currently, and make sure that we're staffed to accomplish them in a
>timely manner?
>
>I welcome discussion about this. My main goal is to help us get to beta
>as soon as possible under our chosen criteria.
>
>Most sincerely,
>
>Eliot
>
>[1] 
>https://docs.google.com/spreadsheet/ccc?key=0AkRs-89PKiZpdE0xdm9Sb1ZvRW1ZR
>zMtWEdyU0Z4OEE#gid=14
>
>
Received on Tuesday, 30 April 2013 20:32:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:13:46 UTC