/irc-logs / w3c / #css / 2009-03-18 / end

Options:

  1. # Session Start: Wed Mar 18 00:00:00 2009
  2. # Session Ident: #css
  3. # [01:07] * Quits: fantasai (fantasai@208.201.242.19) (Ping timeout)
  4. # [01:07] * Joins: fantasai (fantasai@208.201.242.19)
  5. # [01:22] * Joins: dbaron (dbaron@216.132.92.66)
  6. # [02:13] * Quits: dbaron (dbaron@216.132.92.66) (Ping timeout)
  7. # [02:44] * Joins: dsinger (mobile@67.218.107.10)
  8. # [02:44] * Quits: dsinger (mobile@67.218.107.10) (Quit: Rooms • iPhone IRC Client • http://rooms.derflash.de)
  9. # [02:55] * Joins: MikeSmith (MikeSmith@mcclure.w3.org)
  10. # [03:04] * Joins: dbaron (dbaron@216.132.92.66)
  11. # [05:41] * Quits: dbaron (dbaron@216.132.92.66) (Quit: 8403864 bytes have been tenured, next gc will be global.)
  12. # [05:54] * Quits: MikeSmith (MikeSmith@mcclure.w3.org) (Quit: Tomorrow to fresh woods, and pastures new.)
  13. # [05:54] * Joins: MikeSmith (MikeSmith@mcclure.w3.org)
  14. # [07:03] * Quits: anne (annevk@77.163.243.203) (Ping timeout)
  15. # [08:07] * Quits: jdaggett (jdaggett@202.221.217.78) (Quit: jdaggett)
  16. # [08:33] * Joins: jdaggett (jdaggett@202.221.217.78)
  17. # [09:43] * Quits: MikeSmith (MikeSmith@mcclure.w3.org) (Quit: Tomorrow to fresh woods, and pastures new.)
  18. # [10:55] * Joins: anne (annevk@77.163.243.203)
  19. # [12:09] * Joins: myakura (myakura@122.29.116.63)
  20. # [12:39] * Quits: Lachy (Lachlan@85.196.122.246) (Quit: This computer has gone to sleep)
  21. # [13:00] * Joins: Lachy (Lachlan@213.236.208.22)
  22. # [13:18] * Quits: anne (annevk@77.163.243.203) (Ping timeout)
  23. # [13:19] * Joins: anne (annevk@77.163.243.203)
  24. # [16:02] * Quits: Lachy (Lachlan@213.236.208.22) (Quit: This computer has gone to sleep)
  25. # [16:15] <fantasai> yayyyy, Skype works
  26. # [16:15] * fantasai hopes the connection doesn't cut out
  27. # [16:23] * fantasai wonders why meyerweb is blocked from here
  28. # [16:28] * Joins: emilyw (chatzilla@74.43.146.33)
  29. # [16:37] * Joins: Lachy (Lachlan@85.196.122.246)
  30. # [16:42] * Quits: emilyw (chatzilla@74.43.146.33) (Ping timeout)
  31. # [16:50] <anne> is the telcon at 5 today due to US time changes?
  32. # [16:50] <Bert> That's what I'm assuming.
  33. # [16:51] <anne> I guess I can hardly attend then
  34. # [16:53] * Joins: sylvaing (sylvaing@131.107.0.105)
  35. # [16:54] * Joins: glazou (glazou@80.118.184.70)
  36. # [16:55] * Joins: Zakim (rrs-bridgg@128.30.52.30)
  37. # [16:55] * Joins: RRSAgent (rrs-loggee@128.30.52.30)
  38. # [16:55] <RRSAgent> logging to http://www.w3.org/2009/03/18-css-irc
  39. # [16:55] <glazou> Zakim, this will be Style
  40. # [16:55] <Zakim> ok, glazou; I see Style_CSS FP()12:00PM scheduled to start in 8 minutes
  41. # [16:57] * Joins: dsinger (mobile@67.218.102.170)
  42. # [16:58] <Zakim> Style_CSS FP()12:00PM has now started
  43. # [16:58] * Parts: dsinger (mobile@67.218.102.170)
  44. # [16:58] <Zakim> +[Microsoft]
  45. # [16:59] <Zakim> +dsinger
  46. # [16:59] * Joins: dsinger (mobile@67.218.102.170)
  47. # [16:59] <dsinger> Zakim, mute me
  48. # [16:59] <Zakim> dsinger should now be muted
  49. # [16:59] * Joins: ChrisL (ChrisL@128.30.52.30)
  50. # [17:00] <dsinger> Zakim, who is here?
  51. # [17:00] <Zakim> On the phone I see [Microsoft], dsinger (muted)
  52. # [17:00] <Zakim> On IRC I see ChrisL, dsinger, RRSAgent, Zakim, glazou, sylvaing, Lachy, anne, myakura, jdaggett, fantasai, krijnh, arronei, Bert, Hixie, shepazu, plinss_, plinss, trackbot
  53. # [17:00] <Zakim> + +1.858.354.aaaa
  54. # [17:00] <ChrisL> rrsagent, here
  55. # [17:00] <RRSAgent> See http://www.w3.org/2009/03/18-css-irc#T15-57-48
  56. # [17:00] <ChrisL> rrsagent, make logs public
  57. # [17:00] <RRSAgent> I have made the request, ChrisL
  58. # [17:00] <anne> Zakim, passcode?
  59. # [17:00] <Zakim> the conference code is 78953 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), anne
  60. # [17:00] <plinss> zakim, +1.858.354 is me
  61. # [17:00] <Zakim> +plinss; got it
  62. # [17:00] <Zakim> +Daniel_Glazman
  63. # [17:01] <dsinger> Morning all!
  64. # [17:01] <sylvaing> Zakim, [Microsoft] has sylvaing
  65. # [17:01] <Zakim> +sylvaing; got it
  66. # [17:01] <sylvaing> hi dave !
  67. # [17:01] <Zakim> +??P21
  68. # [17:01] <anne> Zakim, ??P21 is me
  69. # [17:01] <Zakim> +ChrisL
  70. # [17:01] <Zakim> +anne; got it
  71. # [17:02] * Joins: melinda (melinda.gr@67.47.246.6)
  72. # [17:03] <anne> I will have to leave in about 20 minutes.
  73. # [17:03] * Joins: emilyw (chatzilla@129.21.80.247)
  74. # [17:03] <ChrisL> zakim, who is noisy?
  75. # [17:03] <anne> WIP on my action items is on public-css-testsuite
  76. # [17:03] <Zakim> ChrisL, listening for 10 seconds I heard sound from the following: [Microsoft] (45%), Daniel_Glazman (15%), anne (4%)
  77. # [17:04] <Zakim> +Bert
  78. # [17:04] <anne> I believe Bert is getting MQ to CR at this point.
  79. # [17:04] * anne turns off music
  80. # [17:04] <glazou> yes
  81. # [17:04] <Zakim> +[IPcaller]
  82. # [17:04] * ChrisL heard no music, but typing
  83. # [17:05] * glazou blames the too low quality of the mac kbd, it should be totally silent :)
  84. # [17:05] <fantasai> Zakim, [IPcaller] is me
  85. # [17:05] <Zakim> +fantasai; got it
  86. # [17:05] <dsinger> Lots of wind and mike noise
  87. # [17:05] * fantasai likes clicky keyboards
  88. # [17:05] * emilyw will be on IRC only for this week and next week's meetings. :(
  89. # [17:05] * anne turns his music back on
  90. # [17:05] * ChrisL likesy using them but not hearing them
  91. # [17:05] <dsinger> Cool
  92. # [17:05] <fantasai> I may or may not be able to make next week's telecon
  93. # [17:06] <ChrisL> zakim, mute Microsoft
  94. # [17:06] <Zakim> [Microsoft] should now be muted
  95. # [17:06] <fantasai> if I do, I likely won't have net access at the same time
  96. # [17:06] <anne> Zakim, who is noisy?
  97. # [17:06] <fantasai> but we'll see
  98. # [17:06] <ChrisL> zakim, unmute Microsoft
  99. # [17:06] <Zakim> [Microsoft] should no longer be muted
  100. # [17:06] * fantasai will have to see whether Skype over dial-up still works ok
  101. # [17:06] <Zakim> anne, listening for 10 seconds I heard sound from the following: fantasai (71%), Daniel_Glazman (13%)
  102. # [17:06] <ChrisL> zakim, unmute Daniel_Glazman
  103. # [17:06] <Zakim> Daniel_Glazman was not muted, ChrisL
  104. # [17:06] * fantasai hits mute
  105. # [17:06] <ChrisL> zakim, mute Daniel_Glazman
  106. # [17:06] <Zakim> Daniel_Glazman should now be muted
  107. # [17:06] <ChrisL> zakim, unmute Daniel_Glazman
  108. # [17:06] <Zakim> Daniel_Glazman should no longer be muted
  109. # [17:07] * sylvaing is wow, Skype over dial-up
  110. # [17:07] * ChrisL Daniel its your keyboard
  111. # [17:07] * fantasai is on adsl atm, but won't be here next week
  112. # [17:07] <glazou> no i was not typing any more
  113. # [17:07] * Bert waits for TCP/IP over skype over dial-up :-)
  114. # [17:08] <Zakim> +Melinda_Grant
  115. # [17:08] * ChrisL proposes fax over skype over ip over http over ip over adsl, for backup
  116. # [17:08] <dsinger> Mpeg2 transport over skype?
  117. # [17:08] * sylvaing could probably run his Minitel on ChrisL's network stack
  118. # [17:09] * ChrisL has in fact seen ip over http deployed to get out of corporate firewalls
  119. # [17:09] * ChrisL has also seen ip over dns
  120. # [17:09] <fantasai> zakim, mute me
  121. # [17:09] <Zakim> fantasai should now be muted
  122. # [17:09] * anne can scribe for 12 more minutes...
  123. # [17:10] * anne sorry
  124. # [17:10] * shepazu would like to remind CSS folks about 3D Transforms spec...
  125. # [17:10] <Bert> Scribe: Bert
  126. # [17:10] <glazou> shepazu: yes we know
  127. # [17:10] <Bert> ScribeNick: Bert
  128. # [17:10] * ChrisL hears really poor quality from peter and bert. will reconnect
  129. # [17:10] * shepazu @glazou :D
  130. # [17:10] <Zakim> -ChrisL
  131. # [17:11] <anne> http://lists.w3.org/Archives/Public/public-css-testsuite/2009Mar/0042.html
  132. # [17:11] <Bert> Topic: today's agenda
  133. # [17:11] <Zakim> +??P22
  134. # [17:11] <Bert> Anne: I suggest talking about test suite [see pointer above]
  135. # [17:12] <fantasai> Topic: Publishing Transforms in coordination with SVG
  136. # [17:12] <Bert> Topic: 3D transforms
  137. # [17:13] * shepazu Zakim, call shepazu
  138. # [17:13] * Zakim ok, shepazu; the call is being made
  139. # [17:13] <Zakim> +Shepazu
  140. # [17:13] <Bert> Chris: SVG understood that CSS would publish it last week, but then they stopped the process when they noticed CSS wasn't publishing.
  141. # [17:13] <dsinger> Dave is puzzled at the lack of reaction to dean's comments to svg
  142. # [17:13] <dsinger> And also puzzled with chrisl
  143. # [17:13] <dsinger> Lack of pib
  144. # [17:14] * Bert is now puzzled why everyone is puzzled...
  145. # [17:14] <dsinger> Pub
  146. # [17:14] <shepazu> dsinger, what do you mean?
  147. # [17:14] <anne> We did not publish because the CSS WG did not formally go on record for publishing.
  148. # [17:14] <dsinger> Zakim, unmute me
  149. # [17:14] <Zakim> dsinger should no longer be muted
  150. # [17:14] <Bert> Chris: We agreed to publish jointly with SVG, but CSS wasn't ready and nothing was published.
  151. # [17:14] <Bert> DaveS: Why were we not ready?
  152. # [17:15] <ChrisL> Beryt, whats up with these four documents?
  153. # [17:15] <fantasai> zakim, unmute me
  154. # [17:15] <Zakim> fantasai should no longer be muted
  155. # [17:16] <Bert> Bert: I couldn't find any resolution in the minutes, so couldn't publish a 1st WD.
  156. # [17:16] <Zakim> +SteveZ
  157. # [17:16] <Bert> Doug: I couldn't find resoltuion either, maybe it was just not correctly minuted?
  158. # [17:16] <ChrisL> ok so since we all recall agreeing this a couple of weeks ago lets have a minuted resolution today
  159. # [17:16] * Joins: szilles (chatzilla@192.150.10.200)
  160. # [17:16] <Bert> Fantasai: There was indeed no resolution, only discussion.
  161. # [17:16] <Bert> DaveS: We got stuck on talking on one para in 2D.
  162. # [17:17] <ChrisL> hearing no objections here
  163. # [17:17] <Bert> Steve: We approved 2D provided that para was added.
  164. # [17:17] <Bert> Doug: SVG really wants to see all 4 published. CAn we get resolution on that?
  165. # [17:18] <Bert> Doug: 2D, 3D, animation and transition.
  166. # [17:18] <fantasai> Steve: Think we had approval on all but 3d
  167. # [17:18] <fantasai> DavidSinger: We agreed to publish 3d, but make it clear it's on a longer timescale
  168. # [17:18] <ChrisL> so we can publish all four
  169. # [17:19] * Quits: dsinger (mobile@67.218.102.170) (Quit: Rooms • iPhone IRC Client • http://rooms.derflash.de)
  170. # [17:19] <Bert> RESOLUTION: publish all four: anim, 3D, 2D and transtions.
  171. # [17:19] <glazou> anne, I think we hear your music
  172. # [17:20] <Bert> Doug: SVG said to Dean already we are very interested in cooperating on all four.
  173. # [17:20] <anne> glazou, ok, it's off now :)
  174. # [17:21] <Bert> Chris: Last weeks SVG's meeting we talked about Dean's comments.
  175. # [17:21] <Bert> Doug: Yes, the SVG editor has an action to work on them.
  176. # [17:21] <ChrisL> the editor in svg has an action to fold in all deans commentsbefore publication
  177. # [17:21] <Bert> Doug: Might be good to have joint telcon SVG-CSS. Maybe even a taskforce.
  178. # [17:21] <glazou> Zakim, who is here ?
  179. # [17:21] <Zakim> On the phone I see [Microsoft], dsinger, plinss, Daniel_Glazman, anne, Bert, fantasai, Melinda_Grant, ??P22, Shepazu, SteveZ
  180. # [17:21] <Zakim> [Microsoft] has sylvaing
  181. # [17:21] <Zakim> On IRC I see szilles, emilyw, melinda, ChrisL, RRSAgent, Zakim, glazou, sylvaing, Lachy, anne, myakura, jdaggett, fantasai, krijnh, arronei, Bert, Hixie, shepazu, plinss_, plinss,
  182. # [17:21] <Zakim> ... trackbot
  183. # [17:22] <Bert> DaveS: But not middle of the night for Dean...
  184. # [17:22] * fantasai is so happy SVG and CSS are cooperating happily
  185. # [17:22] * ChrisL is too
  186. # [17:22] <Zakim> -Shepazu
  187. # [17:22] * shepazu yays
  188. # [17:22] <Bert> Topic: test review process
  189. # [17:22] <plinss> http://lists.w3.org/Archives/Public/public-css-testsuite/2009Mar/0042.html
  190. # [17:23] <Bert> Anne: At ftf we decided that if you review a test, you would indicate that.
  191. # [17:23] * Joins: dsinger (dsinger@17.202.35.52)
  192. # [17:23] <Bert> Anne: Also decided you could change and somebody else would review that.
  193. # [17:23] <Bert> Anne: But not clear from the test itself who reviewed it.
  194. # [17:23] <Zakim> +[Apple]
  195. # [17:23] <Zakim> -dsinger
  196. # [17:24] <dsinger> zakim, [apple] has dsinger
  197. # [17:24] <Zakim> +dsinger; got it
  198. # [17:24] <Bert> Anne: So proposal is a small change to tets format.
  199. # [17:24] * Bert can't hear fantasai
  200. # [17:24] <Bert> Melinda: So anybody who makes a change should add a link?
  201. # [17:25] <Bert> Anne: yes, add a "reviewer" link.
  202. # [17:25] <Bert> Fantasai: "Author" is who wrote the test, maybe has copyright.
  203. # [17:25] <Bert> Melinda: So are we adding "author" "contributor" or "reviewer" links?
  204. # [17:26] <fantasai> Add "author" if you make a significant contribution to the test
  205. # [17:26] <fantasai> i.e. not fixing a typo or tweaking the title
  206. # [17:26] <fantasai> actually changing the test
  207. # [17:26] <Bert> Fantasai: [writing in IRC]
  208. # [17:26] * anne has to run, will hopefully review his tests soonish
  209. # [17:26] <sylvaing> so if I submit a test, then fantasai edits it then anne approves it we'll have...
  210. # [17:27] <fantasai> The problem I had with the reviewer link idea, is that it's not clear when the complete test is reviewed
  211. # [17:27] <sylvaing> a link rel=author for fantasai's edit
  212. # [17:27] <fantasai> for example
  213. # [17:27] <fantasai> a test is submitted with some problems
  214. # [17:27] <fantasai> I review it
  215. # [17:27] <fantasai> it's mostly good
  216. # [17:27] <sylvaing> then a link rel=reviewer for anne ?
  217. # [17:27] <fantasai> but this one part needs a fix
  218. # [17:27] <fantasai> I can fix it and then ask the author to review my chang
  219. # [17:27] <fantasai> in that case
  220. # [17:27] <fantasai> we're both actually reviewers
  221. # [17:27] <anne> sylvaing, yes
  222. # [17:27] <sylvaing> ok
  223. # [17:27] <anne> sylvaing, but you can review it yourself as well
  224. # [17:28] <fantasai> that doesn't help fantasai programmatically figure out whether the test is *approved* yet or not
  225. # [17:28] <anne> (dates should be clear from SVN)
  226. # [17:28] <Bert> Melinda: So probably the review needs a date field as well.
  227. # [17:28] <fantasai> Anyone can review
  228. # [17:28] <anne> fantasai, "reviewer" means approved
  229. # [17:28] <fantasai> peers will approve the tests and move it over, and that might mean rubber-stamping a review by someone competent
  230. # [17:28] <Bert> Chris: We have a list of who reviews which chapter in principle.
  231. # [17:28] <anne> fantasai, is what we decided
  232. # [17:28] <sylvaing> right, not sure I as microsoft should review our own tests. am open to reviewing other tests
  233. # [17:28] * anne has to go
  234. # [17:28] <fantasai> e.g. if jdaggett is reviewing the fonts test,s I'll assume he's rgith
  235. # [17:28] <fantasai> if someone I've never heard of reviews them, I will probably take another look first
  236. # [17:28] <Bert> Melinda: No record of who "approves" a test?
  237. # [17:29] <fantasai> before copying the tests into CVS
  238. # [17:29] <fantasai> no, just cvs record for that bit
  239. # [17:29] <fantasai> So
  240. # [17:29] <Bert> Melinda: So whoever approves must do a CVS check-in?
  241. # [17:29] <fantasai> there's two levels of "review" one is mainly about reviewing the test
  242. # [17:29] <fantasai> the other is mainly checking that the test has been appropriately reviewed
  243. # [17:30] <fantasai> the first level is where we send comments to public-css-testsuite
  244. # [17:30] <fantasai> and mark reviewr in the test case itself
  245. # [17:30] <fantasai> the second level is mainly about copying it into the main repo
  246. # [17:30] * fantasai wonders if everyone's on irc, or if someone should read her comments
  247. # [17:30] * dsinger wonders who is speaking with that echo?
  248. # [17:31] <glazou> dsinger: everyone
  249. # [17:31] <glazou> :)
  250. # [17:31] <fantasai> peter's breaking up, too
  251. # [17:31] * fantasai can hear everyone else fine
  252. # [17:31] * sylvaing is glad there actually is an echo and it's not just yesterday's guinness
  253. # [17:31] <Zakim> -anne
  254. # [17:32] <fantasai> it should mean that you looked at the test and approve of it
  255. # [17:32] <Bert> Peter: Confused about the "reviewer" link: is that marking review or approval? Or both?
  256. # [17:32] <fantasai> at least
  257. # [17:32] <fantasai> that was the goal
  258. # [17:32] <Bert> Peter: And the "contributor" link?
  259. # [17:32] <fantasai> the main purpose of the reviewer link isn't to say who revieed the test for posterity
  260. # [17:32] <fantasai> it's so that someone knows the test has been approved
  261. # [17:32] <fantasai> "contributor" doesn't exist
  262. # [17:32] <fantasai> we are using "author'
  263. # [17:33] <Bert> Sylvain: OK, so there is no "contributor." Fine.
  264. # [17:33] <fantasai> The *point*
  265. # [17:33] <fantasai> of this link
  266. # [17:33] <fantasai> was to mark "this test has been reviewed"
  267. # [17:33] <Bert> Peter/Melinda: Is this for all existing tests as well?
  268. # [17:33] <fantasai> without creating a new system for recording which test have been reviewed
  269. # [17:34] <Bert> Steve: Do the tests already have "author" links?
  270. # [17:34] <Bert> melinda: Yes, I think they do.
  271. # [17:34] <fantasai> yes, they have "author" links
  272. # [17:34] <Bert> Fantasai: Yes, all tests have "author." I put them in.
  273. # [17:35] <Bert> Fantasai: Goal is not to know who reviewed, but to approve.
  274. # [17:35] <Bert> Fantasai: There were other ideas, such as a wiki page. I don't really care about the mechnaism, but we need some way to track.
  275. # [17:35] <Bert> Fantasai: Depending on who is the reviewer I may or may not do another review myself.
  276. # [17:36] <Bert> Melinda: So "reviewer" means approval.
  277. # [17:36] <Bert> Steve: Except when reviewer makes changes inthe process.
  278. # [17:36] <Bert> Melinda: But then you would use an "author" link reahter than reviewer, wouldn't you?
  279. # [17:36] <Bert> Steve: OK, I see.
  280. # [17:37] <Bert> Fantasai: The fixes by a reviewer need to be reviewed, by the original author, e.g.
  281. # [17:37] <Bert> Fantasai: We could put a date in comments or something.
  282. # [17:38] <Bert> Steve: Idea is to know that last reviewer is not not the same as the last author.
  283. # [17:38] <Bert> Steve: Author has signed off that *he* believes it is correct. Just need somebody else after that.
  284. # [17:39] <Bert> Steve: Can we put a date field in the link?
  285. # [17:39] <Bert> Fantasai: A comment on the same line migfht work.
  286. # [17:39] <Bert> Steve: Or just an unknown attribute?
  287. # [17:39] <Bert> Fantasai: It needs to validate.
  288. # [17:40] <Bert> Fantasai/Steve: OK, so a date in a comment, then.
  289. # [17:40] <fantasai> <link rel="author reviewer" title="Elika Etemad"/> <!-- 2009-03-17 -->
  290. # [17:40] <ChrisL> it will do
  291. # [17:40] <fantasai> meaning "everything looks ok except the stuff I changed, and the stuff I changed needs to be reviewed"
  292. # [17:41] * dsinger that is a GREAT sound effect
  293. # [17:41] <Bert> Fantasai: rel="author reviewer" (plus a date) means I reviewed everything except for the parts I changed.
  294. # [17:41] <Bert> Steve: and thus rel="reviewer" means you did not change anything.
  295. # [17:42] <Bert> Fantasai: I'm working on a Perl script to add anything you need to add.
  296. # [17:42] <fantasai> That was a side-comment to Melinda
  297. # [17:42] <Bert> Steve: Can you point to example?
  298. # [17:43] <fantasai> http://wiki.csswg.org/test/css2.1/format
  299. # [17:44] <fantasai> Topic: Matrix Layout
  300. # [17:44] <plinss> http://lists.w3.org/Archives/Public/www-style/2009Mar/0135.html
  301. # [17:44] <Bert> Topic: matrix layout
  302. # [17:44] <Bert> Fantasai: I agree with the comments Bert sent.
  303. # [17:44] <fantasai> http://lists.w3.org/Archives/Public/www-style/2009Mar/0183.html
  304. # [17:45] <Bert> Peter: It looks like an itneresting idea. Would it fit? and so where?
  305. # [17:45] <Bert> Steve: We have to talk about Grid and Template at the same time.
  306. # [17:46] <Bert> Steve: Maybe not urgent and better for a meeting.
  307. # [17:46] <Bert> Daniel: Is MS still working on Grid? HAven't heard from Alex in a while.
  308. # [17:46] <Bert> Sylvain: Yes, still interesting, but CSS 2.1 takes all resources right now.
  309. # [17:47] <Bert> Sylvain: Alex should be at ftf in June.
  310. # [17:47] <Bert> Steve: I haven't reviewed the new proposal yet.
  311. # [17:47] <fantasai> Melinda: I think we should put these three proposals side by side and compare their pros and cons
  312. # [17:47] <Bert> Melinda: Putting the three together at a ftf seems a good idea, indeed. Towards some combination of them.
  313. # [17:48] <Bert> Steve: And GCPM seems to have some stuff as well.
  314. # [17:48] <Bert> Bert: Yes moveto/pullfrom and similar ideas.
  315. # [17:49] <fantasai> It seems to me this matrix proposal is just like template layout, except with the added ability to overlap elements
  316. # [17:49] <Bert> Melnda: There is a need for improved layout techniques, but we need to be clear about our objectives.
  317. # [17:49] * Quits: emilyw (chatzilla@129.21.80.247) (Quit: ChatZilla 0.9.84 [Firefox 3.0.7/2009021906])
  318. # [17:49] <Bert> Steve: Peter, is that what you meant when you asked about how it fit?
  319. # [17:50] <Bert> Peter: Yes, ftf seems reasonable. But also wants to know who is interested at the moment.
  320. # [17:50] <Bert> Fantasai: We should look at the proposal and foxus on use cases, but not focus on syntax too much now.
  321. # [17:51] <Bert> Fantasai: Maybe the matrix things can be done by extending layout eleshwre.
  322. # [17:51] <Bert> Sylvain: I heard there was interest in this stuff.
  323. # [17:51] <Bert> Steve: It has alwasy been clear that people want this. Less clear if there are implementers for it.
  324. # [17:52] <sylvaing> i.e. web designers came up during and after the CSS3 panel at SXSW to express interest in Jonathan Snook's proposal
  325. # [17:52] <Bert> Steve: I mean: as a priority.
  326. # [17:52] <Bert> Peter: So to summarize: I hear interest in evaluating the proposal. Don't hear anythign about it being implemented soon.
  327. # [17:53] <Bert> Peter: I suggest we pencil it in as a topic for the ftf.
  328. # [17:54] <Bert> Steve: SOmebody should repsond to Jonathan to say we probably won't talk about it until June.
  329. # [17:54] <Bert> Peter: Who will represent the matrix proposal?
  330. # [17:54] <Bert> Steve: We can invite Jonathan...
  331. # [17:54] <Bert> Steve: Othe rquestion: are there patents involved?
  332. # [17:55] <Bert> Bert: Anybody know Jonathan Snook?
  333. # [17:55] <Bert> All: No, never met him.
  334. # [17:55] <sylvaing> http://snook.ca/
  335. # [17:56] <plinss> http://lists.w3.org/Archives/Public/www-style/2009Mar/0133.html
  336. # [17:56] <Bert> Topic: Counter-increment
  337. # [17:57] <plinss> http://lists.w3.org/Archives/Public/www-style/2009Mar/0194.html
  338. # [17:57] <Bert> Fantasai: David Baron posted proposals.
  339. # [17:57] <melinda> *jonathan is a member of the CSS 11 ;-)
  340. # [17:57] <fantasai> http://lists.w3.org/Archives/Public/www-style/2009Mar/0194.html
  341. # [17:57] <fantasai> I'm in favor of option 1
  342. # [17:58] <Bert> Steve: I like option 1
  343. # [17:58] <Bert> Fantasai: Same question for other keywords, such as 'inherit'
  344. # [17:59] <fantasai> so any objections? :)
  345. # [17:59] * dsinger is appallingly ignorant, uninformed, and unopinionated on this subject
  346. # [17:59] <Bert> Bert: Leaning to option 1 as well.
  347. # [18:00] <Bert> Melinda: So what does this mean for 'inherit'?
  348. # [18:00] <Bert> Steve: Can't use it is a coutner name.
  349. # [18:00] <Bert> s/coutner/counter/
  350. # [18:00] <Bert> Chris: Can you escape it? With a backslash?
  351. # [18:00] <Bert> Fantasai: No.
  352. # [18:01] <Bert> Sylvain: What's the use case for 'counter-increment: none'?
  353. # [18:02] <Bert> Fantasai: I can't think of a reaosn for a counter named "none", but I can certainly see a case to explicitly set 'counter-increment' to 'none' to stop the coutner from incrementing.
  354. # [18:02] <Bert> Sylvain: I don't get the 'counter-inc: none 1' rule.
  355. # [18:02] <Bert> Peter: That is just invalid.
  356. # [18:03] * dsinger has a conflicting call starting now, alas. sorry, bye
  357. # [18:03] <Bert> Peter: I think that's implied by the prose, but not explicit.
  358. # [18:03] <Bert> Melinda: We need some words to describe 'none' then.
  359. # [18:03] <Bert> Peter: Yes, agree.
  360. # [18:04] <Bert> Peter: Bert, can you write text?
  361. # [18:04] <Zakim> -[Apple]
  362. # [18:04] <Bert> Bert: OK.
  363. # [18:04] <Bert> Fantasai: I'll note it in the issues list.
  364. # [18:05] <Bert> Peter: Shoudl be enough if Bert sends it to www-style. We'll see what comments, if any, it gets.
  365. # [18:05] <Bert> s/Shoudl/Should/
  366. # [18:05] <Zakim> -??P22
  367. # [18:05] <Zakim> -[Microsoft]
  368. # [18:05] <Zakim> -Melinda_Grant
  369. # [18:05] <Zakim> -Daniel_Glazman
  370. # [18:05] <Zakim> -plinss
  371. # [18:05] <fantasai> RESOLVED: accept proposal 1, Bert to come up with wording, submit for review to www-style; no objections mean accepted
  372. # [18:05] <Zakim> -fantasai
  373. # [18:05] <szilles> Steve has probable regrets for next week due to AB meeting
  374. # [18:05] <Zakim> -Bert
  375. # [18:06] <Zakim> -SteveZ
  376. # [18:06] <Zakim> Style_CSS FP()12:00PM has ended
  377. # [18:06] <Zakim> Attendees were dsinger, +1.858.354.aaaa, plinss, Daniel_Glazman, sylvaing, ChrisL, anne, Bert, fantasai, Melinda_Grant, Shepazu, SteveZ
  378. # [18:07] * Quits: arronei (arronei@131.107.0.103) (Ping timeout)
  379. # [18:10] * Quits: sylvaing (sylvaing@131.107.0.105) (Ping timeout)
  380. # [18:11] * Quits: glazou (glazou@80.118.184.70) (Quit: glazou)
  381. # [18:14] * Joins: arronei (arronei@131.107.0.104)
  382. # [18:17] <Bert> rrsagent, make minutes
  383. # [18:17] <RRSAgent> I have made the request to generate http://www.w3.org/2009/03/18-css-minutes.html Bert
  384. # [18:18] <Bert> rrsagent, make logs public
  385. # [18:18] <RRSAgent> I have made the request, Bert
  386. # [18:18] <Bert> Meeting: CSS telcon
  387. # [18:19] <Bert> Chair: Peter
  388. # [18:27] * Quits: szilles (chatzilla@192.150.10.200) (Quit: ChatZilla 0.9.84 [Firefox 3.0.7/2009021910])
  389. # [18:31] <Bert> Regrets: Dean, Tona, Molly
  390. # [18:32] <Bert> s/Topic: today's agenda/Topic: Today's agenda/
  391. # [18:33] <Bert> s/Topic: test review process/Topic: Test review process/
  392. # [18:33] <Bert> s/RESOLUTION:/RESOLVED:/
  393. # [18:33] <Bert> s/Topic: 3D transforms//
  394. # [18:33] * Quits: shepazu (schepers@128.30.52.30) (Quit: Core Breach)
  395. # [18:34] <Bert> rrsagent, make minutes
  396. # [18:34] <RRSAgent> I have made the request to generate http://www.w3.org/2009/03/18-css-minutes.html Bert
  397. # [18:35] * Joins: shepazu (schepers@128.30.52.30)
  398. # [18:35] <Bert> s/Beryt/Bert/
  399. # [18:35] <Bert> s/CAn/Can/
  400. # [18:37] <Bert> s/anim, 3D, 2D and transtions/Animations, 3D Transforms, 2D Transforms, and Transitions/
  401. # [18:37] <Bert> s/Last weeks/At last week's/
  402. # [18:38] <Bert> s/RESOLVED:/RESOLUTION:/g
  403. # [18:39] <Bert> rrsagent, make minutes
  404. # [18:39] <RRSAgent> I have made the request to generate http://www.w3.org/2009/03/18-css-minutes.html Bert
  405. # [18:40] <Bert> s/But not middle/But not in the middle/
  406. # [18:40] <Bert> s/tets format/test format/
  407. # [18:41] * Quits: myakura (myakura@122.29.116.63) (Quit: Leaving...)
  408. # [18:42] <Bert> s/Peter\/Melinda/Peter & Melinda/
  409. # [18:42] <Bert> rrsagent, make minutes
  410. # [18:42] <RRSAgent> I have made the request to generate http://www.w3.org/2009/03/18-css-minutes.html Bert
  411. # [18:42] <Bert> s/melinda/Melinda/g
  412. # [18:43] <Bert> s/mechnaism/mechanism/
  413. # [18:43] <Bert> s/ inthe/ in the/
  414. # [18:43] <Bert> s/reahter/rather/
  415. # [18:44] <Bert> s/migfht/might/
  416. # [18:44] <Bert> rrsagent, make minutes
  417. # [18:44] <RRSAgent> I have made the request to generate http://www.w3.org/2009/03/18-css-minutes.html Bert
  418. # [18:45] <Bert> s|Peter/Melinda|Peter & Melinda|
  419. # [18:45] <Bert> s|Fantasai/Steve|Fantasai & Steve|
  420. # [18:46] <Bert> s/and so where/and if so where/
  421. # [18:47] <Bert> s/better for a meeting/better for a ftf meeting/
  422. # [18:47] <Bert> s/HAven't/Haven't/
  423. # [18:47] * Quits: ChrisL (ChrisL@128.30.52.30) (Client exited)
  424. # [18:47] <Bert> s/Sylvain: Yes, still interesting/Sylvain: Yes, still interested/
  425. # [18:48] <Bert> s/foxus/focus/
  426. # [18:49] <Bert> s/eleshwre/elsewhere/
  427. # [18:49] <Bert> s/anythign/anything/
  428. # [18:50] <Bert> s/SOmebody should repsond/Somebody should respond/
  429. # [18:50] * Joins: ChrisL (ChrisL@128.30.52.30)
  430. # [18:50] <Bert> s/Othe rquestion/Other question/
  431. # [18:51] <Bert> s/reaosn/reason/
  432. # [18:51] <Bert> s/coutner/counter/
  433. # [18:51] <Bert> s/counter-inc: none 1/counter-increment: none 1/
  434. # [18:52] <Bert> rrsagent, make minutes
  435. # [18:52] <RRSAgent> I have made the request to generate http://www.w3.org/2009/03/18-css-minutes.html Bert
  436. # [18:53] <Bert> s|s/Peter\/Melinda/Peter & Melinda/||
  437. # [18:54] <Bert> RESOLUTION: accept proposal 1, Bert to come up with wording, submit for review to www-style; no objections means accepted.
  438. # [18:54] <Bert> rrsagent, make minutes
  439. # [18:54] <RRSAgent> I have made the request to generate http://www.w3.org/2009/03/18-css-minutes.html Bert
  440. # [18:55] <Bert> s/Shoudl/Should/
  441. # [18:56] <Bert> s/alwasy/always/
  442. # [18:57] <Bert> s/coutner/counter/
  443. # [18:57] <Bert> s/anythign/anything/
  444. # [18:57] <Bert> rrsagent, make minutes
  445. # [18:57] <RRSAgent> I have made the request to generate http://www.w3.org/2009/03/18-css-minutes.html Bert
  446. # [18:57] * Quits: ChrisL (ChrisL@128.30.52.30) (Client exited)
  447. # [19:36] * Zakim excuses himself; his presence no longer seems to be needed
  448. # [19:36] * Parts: Zakim (rrs-bridgg@128.30.52.30)
  449. # [19:40] <shepazu> where should I send a coordination email about Transforms? which list?
  450. # [19:52] <fantasai> w3c-css-wg
  451. # [19:52] <fantasai> shepazu: we don't do anministrivia on www-style
  452. # [19:53] <shepazu> ok, thanks, fantasai-chan
  453. # [19:53] <fantasai> s/anministrivia/administrivia/
  454. # [19:53] <Bert> Doug, I first need PLH's approval, but we can do the coord here on IRC as well, for speed.
  455. # [19:54] <shepazu> Bert: I mean long-term, maybe a Transforms Task Force
  456. # [19:54] <Bert> I see.
  457. # [19:54] <shepazu> Dean raised the idea tht it might be better if there were one spec
  458. # [19:54] <shepazu> for SVG and CSS
  459. # [19:55] <fantasai> ok, just make sure technical discussion gets to www-style
  460. # [19:56] <shepazu> right
  461. # [20:01] <dsinger> we can split the lists and have task-force is it overwhelms css or svg. at the moment, more discussion on CSS specs would be welcome...
  462. # [20:05] <shepazu> dsinger: since cross-posting is such a pain, I'm really starting to think a TF is the best way forward at this point
  463. # [20:06] <shepazu> and that might be good to establish *before* the publications, so we can indicate in the specs that discussion should take place on the Transforms TF mailing list
  464. # [20:06] <shepazu> forming a TF is a trivial matter... I could have one running today
  465. # [20:06] <dsinger> ah, yes, hm
  466. # [20:06] <shepazu> assuming that we get approval by both WGs
  467. # [20:07] <shepazu> a TF doesn't require any more overhead than making a page (like a charter) that describes it, and making a mailing list
  468. # [20:08] <shepazu> it doesn't have to go to the AC for approval or anything
  469. # [20:08] <dsinger> right, but we lose the 'accidental oversight' of the people on SVG and CSS lists who don't join, that's all
  470. # [20:08] <shepazu> there is that
  471. # [20:09] <shepazu> but making a public statement on both those lists inviting people to join should help
  472. # [20:09] <dsinger> I'm easy; I hadn't thought of the cross-posting problem.
  473. # [20:10] <shepazu> and for those people chiefly interested in the transforms, it makes it much more manageable to track
  474. # [20:10] <shepazu> I think it increases oversight
  475. # [20:10] <dsinger> yes, a different header. should the discussion of transitions and animations happen there also?
  476. # [20:11] <shepazu> dsinger: I thought about that
  477. # [20:11] <dsinger> ...and...
  478. # [20:11] <shepazu> don't have an opinion on whether it's better to have a topic-specific TF, or one that covers all these CSS-SVG overlaps
  479. # [20:12] <dsinger> it's just that we are also trying to maintain obvious family-resemblance between these
  480. # [20:12] <shepazu> yeah, makes sense
  481. # [20:13] <dsinger> 'primarily to discuss transforms, but also when appropriate transitions and animations, or indeed other areas of css-svg mutual interest'?
  482. # [20:13] <shepazu> wfm
  483. # [20:13] <shepazu> Bert, what do you think about this?
  484. # [20:13] <Bert> About what?
  485. # [20:13] <shepazu> the price of tea in china
  486. # [20:13] <shepazu> also, forming an joint CSS-SVG TF
  487. # [20:14] * Bert reading back up...
  488. # [20:14] <shepazu> to coordinate on Transforms, Animations, et al
  489. # [20:14] <shepazu> or a couple of TFs
  490. # [20:14] <shepazu> I think probably a single one, with a dedicated mailing list, is best, now that I ponder on it
  491. # [20:15] <shepazu> dsinger, like CSS-SVG TF, keep it simple
  492. # [20:15] <dsinger> we could call it the stylin' vector group (svg), or the combin' stylin' and scalin' :-) (CSS)
  493. # [20:15] * Joins: plh (plh@128.30.52.28)
  494. # [20:16] <shepazu> lol dsinger
  495. # [20:16] <dsinger> bonjour, ca va?
  496. # [20:16] <shepazu> I just summoned plh into the room to discuss it more
  497. # [20:16] * plh notes that this channel doesn't use colors, fonts, or effects. that's disappointing
  498. # [20:16] <plh> bonjour David
  499. # [20:16] <Bert> :-)
  500. # [20:17] <Bert> Actually, when Doug talks to me, he does so in green. And when you joined, you did so in blue...
  501. # [20:17] * dsinger can't even be bothered to type cedillas, let alon ecolours
  502. # [20:17] <plh> doug, yes, speaking of summoning, who would you like me to doom for the next 50 years?
  503. # [20:17] <shepazu> plh: dsinger and propose to make a CSS-SVG Coordination TF, to discuss Transforms, Animations, Transitions, and other areas
  504. # [20:17] <shepazu> oh, plh, the list is so long...
  505. # [20:17] * dsinger wants to be yellow
  506. # [20:17] <shepazu> coward.
  507. # [20:18] <plh> as I said, if the CSS and SVG folks are ok with a TF, I'm fine with it as well
  508. # [20:18] <shepazu> I don't do anything special to my IRC client... it all looks black-and-white to me
  509. # [20:19] <shepazu> plh: it might be good to establish the TF *before* the publications, so we can indicate in the specs that discussion should take place on the TF mailing list
  510. # [20:19] <shepazu> what do y'all think?
  511. # [20:19] <Bert> Given that some people will want to work on transformations and we can't forbid them, a TF is probably the best way to avoid losing time for CSS 2.1 and other high-prio specs on the main CSS telcons.
  512. # [20:19] * shepazu changes his font color to white
  513. # [20:19] <dsinger> yes, once we ask for comments, we're stuck with where we ask them to go.
  514. # [20:20] <dsinger> it is trivially easy to make CSS and SVG the expansion of another email address, but very hard to reverse a decision to ask for cross-posting
  515. # [20:21] <shepazu> and like I said, it prevents overwhelming the more general SVG and CSS mailing lists, and allows people to track in a more issue-centered manner
  516. # [20:21] <plh> I could propose public-css-svg-2dtransforms-3dtransforms-animation-transition-task-force@w3.org for a mailing list name
  517. # [20:21] * dsinger has a patent on the u;tra-cool white text with wide white margins on a white background
  518. # [20:21] <shepazu> plh: sold!
  519. # [20:21] <shepazu> dsinger: I don't think you want to talk to me about patents right now ... :)
  520. # [20:21] <dsinger> s please on transition and animation, otherwise it's too short
  521. # [20:22] <plh> lol
  522. # [20:22] <dsinger> but the first word: public or member-only?
  523. # [20:22] <plh> I'd prefer public
  524. # [20:22] <plh> unless we have a really really good reason not to
  525. # [20:23] <shepazu> public-css-svg-tf@w3.org
  526. # [20:23] <Bert> I don't care about the name, except: why "public-"? Participants must be member of either SVG or CSS, mustn't they?
  527. # [20:23] <Bert> (Talking about patents...)
  528. # [20:23] <shepazu> Bert: naming convention
  529. # [20:23] <dsinger> I tend to think that they should be, yes. they must be under the patent policy to be on the list :-)
  530. # [20:24] <shepazu> what about public comment?
  531. # [20:24] <plh> bert, yes participants must be from css or svg, but the css wg is supposed to work in public. creating a task force doesn't change that fact
  532. # [20:24] <shepazu> as is the SVG WG
  533. # [20:24] <dsinger> public comments come from when a real WG publishes something for public comment
  534. # [20:25] <dsinger> ok, got it
  535. # [20:25] <plh> note public- doesn't mean you have to open the list to everyone. we have public mailing list where posting is restricted to group participants
  536. # [20:26] <shepazu> (for instance public-svg-wg)
  537. # [20:26] <plh> it depends on much emails you're willing to get in your inbox sometimes
  538. # [20:26] <plh> s//how/
  539. # [20:26] <plh> s/much/many/
  540. # [20:26] <dsinger> ok, there's public readability (good, both groups are), public comment (good), and public contribution (bad, IPR issues)
  541. # [20:26] <shepazu> honestly, I think having a public list, open to public comments, is best
  542. # [20:26] <shepazu> dsinger: right
  543. # [20:26] <dsinger> if the documents are publicly visible, yes
  544. # [20:27] <Bert> I wouldn't want to be on a task force whose archives are public. Better ask the potential members if they want to be.
  545. # [20:27] <shepazu> Bert: huh?
  546. # [20:27] <plh> Bert, let me be clearer then: I would strongly object if the mailing list archive was Member only. it's against the CSS charter
  547. # [20:28] <dsinger> if the archives and membership is private, but the public can send, all it takes is comeone to respond to public submissions with a 'thank you for your comments'
  548. # [20:28] <dsinger> s/is/are/
  549. # [20:28] <Bert> Making the discussions public means the *real* discussions aren't archived.
  550. # [20:28] * shepazu accuses Bert of fuddy-duddism
  551. # [20:29] <plh> are you telling me that the real discussion for the css working group aren't archived?
  552. # [20:29] <shepazu> ok, kids, let's get back on topic
  553. # [20:29] <dsinger> join a call sometime :-)
  554. # [20:30] <dsinger> this is close enough to a policy question that I feel plh et al. can work it out
  555. # [20:30] <shepazu> dsinger: I understand your concerns about IPR from non-WG members, but how do you propose to avoid that and still take public feedback?
  556. # [20:30] <plh> we all know that lots of things don't get archived. but technical discussion should be backed by public archived.
  557. # [20:30] <plh> s/ved/ves/
  558. # [20:30] <dsinger> I can't, that's why I said what I did...
  559. # [20:30] <shepazu> heh
  560. # [20:31] <dsinger> this tf also has calls, an irc channel, separate agenda/minutes, or what?
  561. # [20:31] <dsinger> wiki
  562. # [20:31] <plh> you can even create a twitter account for it :)
  563. # [20:31] <dsinger> that's when me (and my calendar) start getting twitchy
  564. # [20:31] <shepazu> would you object to a public forum for all discussions (WG and public), considering that we have our w3c posting-policy in place?
  565. # [20:32] <shepazu> dsinger: yes, calls as appropriate
  566. # [20:32] <shepazu> not necessarily regular
  567. # [20:32] * Bert got to go. Last shop closes in 30 minutes and fridge is empty.
  568. # [20:32] <shepazu> I'd assume we'd have to adjust to Oz time
  569. # [20:33] <shepazu> since that's where the editors are
  570. # [20:33] <dsinger> ok, we're dealing with a hypothetical. it can start public and be fixed if problems arise (e.g. people can be asked to join if they start contributing, or the list can be closed down to private if it gets out of control)
  571. # [20:33] <shepazu> Bert: ok, so, a TF is okay with CSS?
  572. # [20:33] <dsinger> I don't think there is a very high risk
  573. # [20:33] <dsinger> and what we lack right now is enough feedback
  574. # [20:33] <shepazu> dsinger: you hit the nail on the head
  575. # [20:33] <Bert> I expect CSS WG is OK with a TF, yes.
  576. # [20:33] <shepazu> we ned to find out what exactly people want
  577. # [20:34] * plh has to step out
  578. # [20:34] <shepazu> ok, I'll ask the SVG WG tomorrow, and put all the pieces together
  579. # [20:34] <shepazu> thanks, folks
  580. # [20:34] <dsinger> thx all
  581. # [20:34] <shepazu> dsinger: get dino to join the SVG WG :D
  582. # [20:34] * dsinger is going to lunch. hope yours is/was/will be nice
  583. # [20:34] <dsinger> he's agreed, I just have to do it
  584. # [20:35] <dsinger> he's an early riser :-(
  585. # [20:44] <shepazu> cool, dsinger
  586. # [21:27] * Parts: plh (plh@128.30.52.28) (Ex-Chat)
  587. # [21:38] * Quits: dsinger (dsinger@17.202.35.52) (Quit: dsinger)
  588. # [21:57] * Quits: melinda (melinda.gr@67.47.246.6) (Ping timeout)
  589. # [21:57] * Joins: melinda (melinda.gr@67.47.246.6)
  590. # [21:57] <fantasai> shepazu: public-css-svg-tf or whatever it was seems fine to me, please make it public read-write
  591. # [21:57] <shepazu> fantasai: that was certainly my intent
  592. # [21:58] <shepazu> I guess we need the whole CSS WG to chime in
  593. # [21:58] <shepazu> I still wonder if there might be a nicer name
  594. # [21:58] <fantasai> probably, although at this point I doubt you'd get much objection from us wrt making it public
  595. # [21:58] <shepazu> hmm... how about public-svg-css-tf... yes, that has a much nicer ring...
  596. # [21:59] <fantasai> hehe
  597. # [21:59] <shepazu> flows trippingly off the tongue...
  598. # [21:59] <fantasai> public-transforms-tf
  599. # [21:59] <fantasai> transitions are a form of transformation :)
  600. # [21:59] <shepazu> lol
  601. # [21:59] <fantasai> so are animations
  602. # [22:00] <shepazu> public-dynamic-tf
  603. # [22:00] <fantasai> but transforms arent' dynamic
  604. # [22:00] <shepazu> public-awesome-tf
  605. # [22:00] <fantasai> public-4d-tf
  606. # [22:00] <shepazu> lol
  607. # [22:01] <shepazu> public-presentation-tf?
  608. # [22:01] <shepazu> nah
  609. # [22:01] <fantasai> no, that would swallow both our groups
  610. # [22:02] * fantasai kicks off a reboot since her camera isn't cooperating
  611. # [22:06] <anne> I'd think it would be pretty hard to find a member interested in transforms/transitions who wants it to happen in Member-only space
  612. # [22:07] <anne> so far discussions have taken place on public lists...
  613. # [22:21] <shepazu> anne: I don't think that's really much of a point for debate... dsinger had some reservations about it, but I think I've convinced him that it's for the best
  614. # [22:21] <shepazu> the open question is whether the CSS WG wants to form a joint TF at all
  615. # [22:22] <shepazu> I'm pretty sure the SVG WG is cool with it
  616. # [22:53] <anne> arronei, RFC2119 words don't apply to tests
  617. # [22:53] * anne was afraid this was going to be hard
  618. # [23:14] <fantasai> huh?
  619. # [23:14] <fantasai> anne: pointer?
  620. # [23:15] <anne> public-css-testsuite
  621. # [23:15] <anne> I'm not sure I want to review Microsoft tests anymore
  622. # [23:15] <fantasai> heh
  623. # [23:16] <fantasai> They didn't train under Hixie, that's the problem. :)
  624. # [23:17] * Hixie would just explain that the guidelines already say how the tests are to be written, and that that's that
  625. # [23:20] <fantasai> a lot of them are open to interpretation
  626. # [23:20] <fantasai> anyway
  627. # [23:20] <fantasai> anne: I just finished reading Arron's post. What he says makes sense to me.
  628. # [23:22] <fantasai> anne: It's not totally consistent with what we've been doing, but we've been pretty inconsistent about these things anyway.
  629. # [23:23] <fantasai> anne: also Melinda's point about precision is valid
  630. # [23:24] <fantasai> anne: especially since we plan to hook up the CSS tests to a harness for non-QA-trained people to run
  631. # [23:25] <fantasai> anne: The guidelines do require not needing to understand CSS in order to pass/fail the test.
  632. # [23:25] <fantasai> anne: http://www.w3.org/Style/CSS/Test/guidelines.html#self-explanatory
  633. # [23:25] <anne> right
  634. # [23:34] <Hixie> i think his point about rfc2119 is just looking for trouble where there is none personally
  635. # [23:34] <Hixie> but i haven't followed the rest of the thread
  636. # [23:35] <fantasai> I don't think we need to fix anything necessarily, but if he went through the trouble of figuring out what standard text to use and had a reason to avoid RFC2119
  637. # [23:35] <fantasai> I don't think we have a good reason to ask him to go back and use it
  638. # [23:36] <Hixie> what text does he use?
  639. # [23:36] <anne> <p>Test passes if the "Filler Text" below is green.</p>
  640. # [23:36] <anne> <div>Filler Text</div>
  641. # [23:36] <anne> (there are variants on this theme)
  642. # [23:37] <Hixie> I prefer correct english grammar and no indirection, e.g. "This test passes if this text is green." but other than that it seems fine
  643. # [23:37] <Hixie> Filler text should be silver and unimportant
  644. # [23:37] <fantasai> yeah, I wouldn't use "filler text"
  645. # [23:37] <fantasai> maybe "Green Text" or something
  646. # [23:38] <fantasai> but I think the "test passes if" wording is fine in place of "should"
  647. # [23:38] <fantasai> anne: you don't have to fix all the tests yourself, you can post problems that are common to the mailing list and ask Arron to fix them
  648. # [23:39] <anne> I know, but the problem is that we seem to have disagreement over simple things
  649. # [23:39] <anne> and this is not the first time
  650. # [23:40] <anne> and I'm not too optimistic about further exchanges
  651. # [23:42] <anne> In related news I'm still interested in hearing back on http://lists.w3.org/Archives/Public/public-css-testsuite/2009Feb/0011.html
  652. # [23:44] * fantasai is so not getting any sleep tonight then :)
  653. # [23:44] * fantasai looks
  654. # [23:45] <anne> I'd go to bed :)
  655. # [23:45] <fantasai> oh, that
  656. # [23:46] <fantasai> well, looks like you just need to wait for Arron to pay attention and respond
  657. # [23:48] <anne> yup
  658. # [23:48] <fantasai> poke him on IRC in #css-test if you want
  659. # [23:48] <fantasai> or here
  660. # [23:48] <fantasai> not sure what his client settings are though
  661. # [23:48] <fantasai> anyway
  662. # [23:48] <fantasai> bedtime
  663. # [23:49] <fantasai> I'll be offline for a few days possibly a week (but hopefully not more than 24 hours, depends on the dialup situation)
  664. # [23:49] <fantasai> ping me on IRC if there's something I really should pay atention to, I might not be able to wade through all my email quickly enough
  665. # [23:50] <fantasai> but I'll check the IRC client, too
  666. # [23:50] <anne> there's no hurry with anything I think
  667. # [23:50] <fantasai> k
  668. # [23:50] <fantasai> have fun
  669. # [23:50] <fantasai> :P
  670. # [23:50] <anne> cheers, you too, whatever you're up to
  671. # [23:51] <fantasai> holidays with cousins :)
  672. # Session Close: Thu Mar 19 00:00:00 2009

The end :)