- From: Chris Mills <cmills@w3.org>
- Date: Tue, 14 May 2013 17:52:43 +0200
- To: Doug Schepers <schepers@w3.org>, Julee AtAdobe <julee@adobe.com>, Scott Rowe <scottrowe@google.com>, Janet Swisher <jswisher@mozilla.com>, "public-webplatform@w3.org" <public-webplatform@w3.org>
I've looked through the Google spreadsheet, and picked these properties for this week (23 in total), which are all in somewhat unfinished states according to the spreadsheet border-image border-image-outset border-image-repeat border-image-slice border-image-source border-image-width break-after break-before break-inside flow-from flow-into font font-family font-feature-settings font-size font-size-adjust font-style font-variant font-weight list-style list-style-image list-style-position list-style-type These form 4 distinct groups, which I think work well together as separate pieces of work. ok? 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 14 May 2013, at 17:27, Chris Mills <cmills@opera.com> wrote: > I've read through this thread, and have ended up being confused as to what to do for this week's WPDW. For now, until a decision is made, shall I just choose the properties from the master google spreadsheet, and then fill in my choices for the week in a new section on http://docs.webplatform.org/wiki/Meta:web_platform_wednesday, and in a new page at http://docs.webplatform.org/wiki/Meta:web_platform_wednesday/2013-05-15 ? > > 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 14 May 2013, at 00:23, Doug Schepers <schepers@w3.org> wrote: > >> Hi, Julee, Scott- >> >> Scott's right that the Master List is hard to edit (as are all tables of any size in MediaWiki...). >> >> How about a compromise where we just redo the spreadsheet to have the right fields, and have the coordinators edit that? >> >> That way, we reduce the complexity of the task for coordinators, and still shield the regular contributors from dealing with the intimidating Bid Spreadsheet? >> >> I do like Julee's solution of an autogenerated final list. >> >> Ultimately, so long as we preserve the bite-size morsels for the contributors, I don't mind how we deal with the coordinator tasks. The workflow shouldn't get in our way, it should help us focus. >> >> (That said, I personally like the sortable Master List... it helped me decide what the topic areas should be for the first week.) >> >> Regards- >> -Doug >> >> On 5/13/13 5:53 PM, Julee wrote: >>> Hi, Scott: >>> >>> I think Doug didn't want to use that spreadsheet anymore. It doesn't >>> have the tasks broken out and it was felt that its complexity is >>> preventing folks from contributing. The 3 different tables were created >>> to provide simpler, more manageable views. In the wiki, these different >>> views can only be generated by creating different tables. Maintenance, >>> then, becomes painful and time-consuming. The weekly spreadsheet doesn't >>> have the priority or the the standards, and the the master doesn't have >>> notes. Otherwise, we could just rebuild the master list from the weekly >>> tables. >>> >>> If we could have the same fields in the weekly table and the master >>> table, we could call the master the to-do list. Then from the weekly >>> tables, we could simply concatenate them into a master "finished" list. >>> >>> I don't think once we have done a property, we need to keep pointer to >>> the spec (as that information would be on the page). That would mean the >>> only difference between the master and the weekly would be the priority >>> — which is something we might need a record of. >>> >>> *How about if we add the priority to the end of the weekly check list?* >>> The data is preserved, but it won't bother coordinators, which is the >>> concern with adding too many columns. The to-do and the "finished" >>> tables would not be the same, but no critical data would be lost. >>> >>> *Then, the workflow would be:* >>> >>> * The decider moves the current week's properties out of the master to >>> weekly page >>> * The coordinators update the weekly page with usernames and notes >>> * As the properties get finished, the coordinators copy the line items >>> from the weekly page to the "finished" table >>> >>> >>> J >>> ---------------------------- >>> julee@adobe.com >>> @adobejulee >>> >>> From: Scott Rowe <scottrowe@google.com <mailto:scottrowe@google.com>> >>> Date: Monday, May 13, 2013 2:12 PM >>> To: julee <julee@adobe.com <mailto:julee@adobe.com>> >>> Cc: Chris Mills <cmills@opera.com <mailto:cmills@opera.com>>, Doug >>> Schepers <schepers@w3.org <mailto:schepers@w3.org>>, Janet Swisher >>> <jswisher@mozilla.com <mailto:jswisher@mozilla.com>>, >>> "public-webplatform@w3.org <mailto:public-webplatform@w3.org>" >>> <public-webplatform@w3.org <mailto:public-webplatform@w3.org>> >>> Subject: Re: REMINDER: WPDW coordinators, please update all three tables >>> >>> Hi Julee, >>> >>> The original spreadsheet: >>> https://docs.google.com/spreadsheet/ccc?key=0AkRs-89PKiZpdE0xdm9Sb1ZvRW1ZRzMtWEdyU0Z4OEE#gid=14 >>> >>> This is just a lot easier to work with. The weekly tables are okay, not >>> a problem to work with. But the larger, "master_list" is so large that >>> working with it in wiki is very difficult. That's why I recommend using >>> the original spreadsheet to track results. >>> >>> ~Scott >>> >>> >>> >>> On Mon, May 13, 2013 at 1:15 PM, Julee <julee@adobe.com >>> <mailto:julee@adobe.com>> wrote: >>> >>> What spreadsheet are you keeping up to date? This one: >>> >>> http://docs.webplatform.org/wiki/Meta:web_platform_wednesday/2013-05-08#Border_color_properties >>> >>> ? >>> >>> Thanks. >>> >>> Julee >>> ---------------------------- >>> julee@adobe.com <mailto:julee@adobe.com> >>> @adobejulee >>> >>> From: Scott Rowe <scottrowe@google.com <mailto:scottrowe@google.com>> >>> Date: Monday, May 13, 2013 10:21 AM >>> To: julee <julee@adobe.com <mailto:julee@adobe.com>> >>> Cc: Chris Mills <cmills@opera.com <mailto:cmills@opera.com>>, Doug >>> Schepers <schepers@w3.org <mailto:schepers@w3.org>>, Janet Swisher >>> <jswisher@mozilla.com <mailto:jswisher@mozilla.com>>, >>> "public-webplatform@w3.org <mailto:public-webplatform@w3.org>" >>> <public-webplatform@w3.org <mailto:public-webplatform@w3.org>> >>> Subject: Re: REMINDER: WPDW coordinators, please update all three tables >>> >>> Folks, >>> >>> I'd like to suggest that we reduce the paperwork for coordinators >>> here by eliminating the last "master_list" table. This table is >>> nearly impossible to edit quickly and easily. We already have a >>> spreadsheet that is far easier to work with, and I'd suggest we >>> stick with it. >>> >>> It may be possible to populate the "master_list" table with >>> transclusions from the other tables, but I don't have time right now >>> to work on that. >>> >>> In any case, I've continued to keep the spreadsheet up to date with >>> my changes, and IMO, it works better than the giant "master_list" >>> table in the wiki. >>> >>> ~Scott >>> >>> >>> >>> On Fri, May 10, 2013 at 10:50 AM, Julee <julee@adobe.com >>> <mailto:julee@adobe.com>> wrote: >>> >>> Hi, WPDW coordinators: >>> >>> Please remember to: >>> >>> * update WPDW main page[1] with assigned items having check marks >>> * update this week's page [2] with status >>> * update master list [3] when things are done >>> >>> Thanks! >>> >>> Julee >>> >>> [1] http://docs.webplatform.org/wiki/Meta:web_platform_Wednesday >>> [2] >>> http://docs.webplatform.org/wiki/Meta:web_platform_wednesday/2013-05-08 >>> [3] >>> http://docs.webplatform.org/wiki/Meta:web_platform_wednesday/master_list >>> ---------------------------- >>> julee@adobe.com <mailto:julee@adobe.com> >>> @adobejulee >>> >>> >>> > >
Received on Tuesday, 14 May 2013 15:52:57 UTC