Molly E. Holzschlag @mholzschlag

It is the true teacher who leaves the class knowing they have learned the most.

 Tucson, AZ
Joined September 2006
  • Tweets 64,757
  • Following 13,801
  • Followers 26,057
Filter
Exclude
Time range
-
Near
Load newest
Moving to CSS Regions here at #css #tpac2011 - much more fun than issue tracking, don't you agree?
1
Replying to @semiBad
@semiBad Actually, our co-chair Peter Linss just suggested that - building a tool, or building on to an existing tool (HTML5 tracking) #css
Wiki pages don't scale, when you get to 300 issues, it becomes very difficult to manage. #tpac2011 #css
3
Side comment from me. It's kind of astonishing how we at #w3c seem to be stuck in older, less effective methods for tracking. #css #tpac2011
2
RESOLVED: Editors must use one of four methods: bugzilla, wiki, tracker, inline. #css #tpac2011
1
1
Link to tracking on Editor's Draft and not Working Draft? #css #tpac2011
1
Elika @fantasai advocates plain text tracking. I love it. Organic! Easy for one person, not for many however. #css #tpac2011
1
David Baron from Mozilla "I write good commit messages" @dbaron #css #tpac2011
1
We have four tracking options: Wiki, tracker, bugzilla, and plain text. #css #tpac2011
1
1
RESOLVED: Add link to issues list from spec header #css #tpac2011 - @glazou states "not comfortable" with spec editors choosing method.
Man @t is back in #css and kicking ass. #tpac2011
@fvsch I'd love to suggest it except it's adding another choice to editors who already have a unique process. IMO, we should do it openly.
Replying to @StuRobson
@StuRobson That makes the most sense. I'll make you a big chocolate cake (or your favorite, if not chocolate) if you can get folks to agree
so @t prefers wiki, Hakon wants email, Mozilla wants bugzilla. How do we improve the system with such disparate user issues? #tpac2011
3
1
Replying to @ravidor
@ravidor LOL, it was Hakon who suggested email. #justsayin' #css #lol
Spec editors have to respond to feedback, regardless of the tracking mechanism. Everyone is using different processes. #css #tpac2011
How do we properly address issues in the #css wg when we have multiple tracking rather than a coordinated process? #tpac2011
Challenge: Tracking changes in specs in a coordinated way. Which is the best way? Email, wiki, large bug management system? #tpac2011
2
2
Topic: Issue tracking in the #css wg, specifically around animation-timing-function inside keyframe rules. #tpac2011
Day 1, #css Working Group meeting, now open. Discussing agenda, variables and hierarchy. #tpac2011
2
1
Load more