/irc-logs / w3c / #css / 2012-02-27 / end

Options:

  1. # Session Start: Mon Feb 27 00:00:01 2012
  2. # Session Ident: #css
  3. # [01:03] * Joins: arno (arno@208.87.61.217)
  4. # [01:10] * Quits: arno (arno@208.87.61.217) (Quit: Leaving.)
  5. # [01:11] * Joins: jdaggett_ (jdaggett@202.221.217.73)
  6. # [01:15] * Joins: bradley (qw3birc@128.30.52.28)
  7. # [01:15] <bradley> hello
  8. # [01:26] * Quits: drublic (drublic@84.174.27.22) (Client exited)
  9. # [01:30] * Quits: bradley (qw3birc@128.30.52.28) (Quit: Page closed)
  10. # [02:21] * Joins: tantek (tantek@70.36.139.112)
  11. # [02:53] * Joins: miketaylr (miketaylr@68.203.0.108)
  12. # [03:44] * Quits: tantek (tantek@70.36.139.112) (Quit: tantek)
  13. # [03:59] * Quits: ed (ed@88.131.66.80) (Ping timeout)
  14. # [04:00] * Joins: ed (ed@88.131.66.80)
  15. # [05:30] * Joins: tantek (tantek@70.36.139.112)
  16. # [05:56] * Quits: miketaylr (miketaylr@68.203.0.108) (Quit: Leaving...)
  17. # [07:46] * Quits: nimbu (Adium@24.18.47.160) (Quit: Leaving.)
  18. # [09:07] * Quits: jdaggett_ (jdaggett@202.221.217.73) (Quit: jdaggett_)
  19. # [09:50] * Joins: drublic (drublic@80.152.180.137)
  20. # [10:10] * Quits: drublic (drublic@80.152.180.137) (Client exited)
  21. # [12:07] * Joins: drublic (drublic@80.152.180.137)
  22. # [12:45] * Quits: drublic (drublic@80.152.180.137) (Client exited)
  23. # [13:07] * Quits: jdaggett (jdaggett@180.235.8.216) (Quit: jdaggett)
  24. # [13:49] * Joins: drublic (drublic@80.152.180.137)
  25. # [14:21] * Joins: karl (karlcow@128.30.54.58)
  26. # [14:37] * Joins: florian (yaaic@84.215.51.223)
  27. # [14:37] * Quits: florian (yaaic@84.215.51.223) (Quit: Yaaic - Yet another Android IRC client - http://www.yaaic.org)
  28. # [14:37] * Joins: florian (yaaic@84.215.51.223)
  29. # [14:37] * Quits: florian (yaaic@84.215.51.223) (Quit: Yaaic - Yet another Android IRC client - http://www.yaaic.org)
  30. # [15:50] * Joins: nimbu (Adium@24.18.47.160)
  31. # [15:54] * Joins: miketaylr (miketaylr@68.203.0.108)
  32. # [16:04] * Quits: miketaylr (miketaylr@68.203.0.108) (Quit: Leaving...)
  33. # [16:09] * Joins: miketaylr (miketaylr@68.203.0.108)
  34. # [16:19] * Joins: danielfilho (danielfilh@187.31.77.7)
  35. # [16:40] * Joins: ksweeney (ksweeney@63.119.10.10)
  36. # [17:12] * Quits: drublic (drublic@80.152.180.137) (Connection reset by peer)
  37. # [17:49] * Joins: arno (arno@192.150.10.200)
  38. # [18:23] * Joins: Ms2ger (Ms2ger@91.181.60.137)
  39. # [18:39] * Quits: arno (arno@192.150.10.200) (Quit: Leaving.)
  40. # [19:19] * Quits: nimbu (Adium@24.18.47.160) (Quit: Leaving.)
  41. # [19:23] * Quits: SimonSapin (simon@82.232.219.95) (Ping timeout)
  42. # [19:37] * Quits: miketaylr (miketaylr@68.203.0.108) (Quit: dflk;adfslkj;alsiekfj;laiskdf)
  43. # [19:37] * Joins: jet (jet@159.63.23.38)
  44. # [19:38] * Joins: miketaylr (miketaylr@68.203.0.108)
  45. # [19:44] * Joins: nimbu (Adium@67.138.164.194)
  46. # [19:49] * Quits: tantek (tantek@70.36.139.112) (Quit: tantek)
  47. # [20:07] * Quits: jet (jet@159.63.23.38) (Quit: jet)
  48. # [20:37] * Joins: drublic (drublic@93.132.225.15)
  49. # [20:49] * miketaylr is now known as miketaylr|
  50. # [20:49] * miketaylr| is now known as miketaylr||
  51. # [20:49] * miketaylr|| is now known as miketaylr|||
  52. # [21:04] * Joins: jet (jet@159.63.23.38)
  53. # [21:13] * Quits: nimbu (Adium@67.138.164.194) (Quit: Leaving.)
  54. # [21:25] * Quits: Ms2ger (Ms2ger@91.181.60.137) (Quit: nn)
  55. # [21:44] * Quits: TabAtkins (tabatkins@216.239.45.4) (Quit: Lost terminal)
  56. # [21:52] * Quits: karl (karlcow@128.30.54.58) (Quit: This computer has gone to sleep)
  57. # [21:57] * Joins: TabAtkins_ (tabatkins@216.239.45.4)
  58. # [23:17] <fantasai> plinss: Is there a way to push changes to /sites/csswg.org/test without authenticating against every single subrepository?
  59. # [23:18] <plinss> every single? there should only be the one...
  60. # [23:19] <plinss> but, yes, store your login credentials in a keyring
  61. # [23:19] <fantasai> I cloned
  62. # [23:19] <fantasai> https://hg.csswg.org/site/base
  63. # [23:19] <fantasai> and that required entering my password about 10 times
  64. # [23:19] <plinss> that's not the test repo
  65. # [23:19] <fantasai> no, that's the site repo
  66. # [23:20] <plinss> ah, missed your original path...
  67. # [23:20] <fantasai> which is what I need to modify
  68. # [23:20] <fantasai> so I tried to push a changeset from csswg.org/test
  69. # [23:20] <fantasai> but it seems to be asking me to authenticate against all 10 (or whatever) subrepos
  70. # [23:21] <fantasai> Is that necessary? Is there a way to just push to the one I'm modifying?
  71. # [23:21] <plinss> right, it'll do that.
  72. # [23:21] <plinss> the site repo is the root that contains all the subrepos for the installed apps
  73. # [23:21] <plinss> when you push to it, it'll auth against all the sub repos
  74. # [23:21] <fantasai> I see.
  75. # [23:22] <plinss> http://mercurial.selenic.com/wiki/KeyringExtension
  76. # [23:22] * Joins: arronei_ (arronei@131.107.0.94)
  77. # [23:22] <plinss> install the keyring and set your login name in your ~/.hgrc file
  78. # [23:22] <plinss> it'll never ask for a password again...
  79. # [23:23] * Joins: nimbu (Adium@24.18.47.160)
  80. # [23:24] * Quits: arronei (arronei@131.107.0.126) (Ping timeout)
  81. # [23:26] <plinss> fwiw, if you're making changes in one of the subrepos, you can just push there...
  82. # [23:26] * fantasai needs to modify htdocs
  83. # [23:27] <plinss> the index.html page I presume?
  84. # [23:27] * fantasai gets a parse error and gives up, puts this task in the "try again once the OS has been upgraded" bucket
  85. # [23:27] <fantasai> plinss: no, adding resources/testharnes.js
  86. # [23:27] <fantasai> plinss: http://lists.w3.org/Archives/Public/public-css-testsuite/2012Feb/0070.html
  87. # [23:28] <plinss> ah, right, on my todo list
  88. # [23:29] <plinss> that should probably be in a subrepo so it can rev independently of the entire site (and we can give other people access to it without giving them the whole web server)
  89. # [23:29] <plinss> I can set that up after lunch today if you want
  90. # [23:30] <fantasai> yay, it works!
  91. # [23:30] <fantasai> plinss: Up to you. Doesn't affect me, since I have access to the whole repo anyway :)
  92. # [23:31] <fantasai> plinss: we should spend some time sorting out the spec Mercurial migration, though
  93. # [23:31] <plinss> ok, I'll move it later
  94. # [23:31] <fantasai> plinss: not today, I told myself I'd work on testing today
  95. # [23:31] * fantasai has been putting this off
  96. # [23:31] <plinss> yes, that was what I was going to work on after lunch
  97. # [23:32] <plinss> I have a clone of the CVS repo and a conversion to hg on my machine
  98. # [23:32] <fantasai> plinss: did you check with sysreq about the checkout / hooks?
  99. # [23:32] <plinss> I also have the repo setup on csswg.org
  100. # [23:32] <plinss> yes, Mike can set up a hook to push to our mirror
  101. # [23:32] <fantasai> nice
  102. # [23:32] <fantasai> hmm
  103. # [23:32] <plinss> drafts.csswg.org is up too
  104. # [23:33] <fantasai> I wonder if we can check out into a checkout of the CVS repo
  105. # [23:33] <fantasai> and then push to dev.w3.org
  106. # [23:33] <plinss> I'm just looking at getting the CVS $date$ substitution working with hg
  107. # [23:33] <fantasai> Hm. I don't think that's too important.
  108. # [23:34] <fantasai> plinss: Given we auto-generate the dates now, we can just strip that from any specs that use it
  109. # [23:34] <fantasai> plinss: Bert's preprocessor will insert it into the generated spec
  110. # [23:34] <plinss> ok. it seemed to be all over the place
  111. # [23:34] <plinss> I just wanted functional paroty...
  112. # [23:34] <fantasai> plinss: heh. I don't think it's worth the trouble here :)
  113. # [23:34] <plinss> ok
  114. # [23:35] <plinss> I can always add it later
  115. # [23:35] <fantasai> plinss: Anything else you're concerned about?
  116. # [23:35] <plinss> (if someone screams)
  117. # [23:35] <plinss> not really, I was going to give my copy another once over, push it to our mirror, then ask you to double check it
  118. # [23:36] * Quits: drublic (drublic@93.132.225.15) (Connection reset by peer)
  119. # [23:36] <plinss> once you give the nod I'll push to dvcs.w3.org and we can shut down the CVS repo
  120. # [23:36] * Joins: drublic (drublic@93.132.225.15)
  121. # [23:36] <plinss> if you have time later I'll ping you after I push to the mirror
  122. # [23:37] <plinss> I just need to get some lunch first, learned the hard way not to make important system changes on low blood sugar :-)
  123. # [23:37] <fantasai> plinss: Ok. We also need to be ready to set up redirects and delete the files from CVS. So we should do the actual migration during a pre-announced period.
  124. # [23:37] <plinss> yes
  125. # [23:37] * Parts: ksweeney (ksweeney@63.119.10.10)
  126. # [23:37] <fantasai> plinss: maybe Thursday
  127. # [23:37] <fantasai> plinss: Oh, but we also need to make sure the Mercurial docs are all set up!
  128. # [23:37] <plinss> that long?
  129. # [23:38] <fantasai> plinss: And that Tantek's QAed the process of setting up hg and checking in a change
  130. # [23:38] <fantasai> plinss: Including one where we trigger a conflict.
  131. # [23:38] <plinss> I think he has hg set up and the docs (for OSX at least) for that
  132. # [23:39] <fantasai> plinss: I'm less concerned about installing mercurial than using it in a real environment
  133. # [23:39] <plinss> sure
  134. # [23:39] <fantasai> plinss: where other people are checking into the repo
  135. # [23:39] <fantasai> plinss: between your pushes
  136. # [23:40] <plinss> you think we need more than is at: http://wiki.csswg.org/tools/hg ?
  137. # [23:40] <fantasai> plinss: yes
  138. # [23:40] <fantasai> plinss: There's a mention of all the relevant commands, but there isn't a good explanation of workflow
  139. # [23:40] <fantasai> plinss: And rebase isn't covered
  140. # [23:41] <fantasai> plinss: The docs need to be workflow-oriented, or they won't make very much sense.
  141. # [23:41] <plinss> ok
  142. # [23:41] <plinss> I'll work on that later today
  143. # [23:41] <fantasai> plinss: Like, it should say
  144. # [23:41] <fantasai> "Getting Started" - everything about setting up, i.e. link to install docs, config files, and cloning
  145. # [23:41] <fantasai> "Making a Change"
  146. # [23:42] <fantasai> updating your tree, making the change, checking the diff, pushing it to the repo, resolving conflicts
  147. # [23:43] <fantasai> that's just a rough idea..
  148. # [23:43] <fantasai> but there should basically be two sets of commends to run: stuff before I make edits, and stuff after I make edits
  149. # [23:43] <fantasai> if the stuff happens to be 5 commands, bunch them into one series. Handle exceptions (stuff going wrong) after that.
  150. # [23:44] * Joins: karl (karlcow@128.30.54.58)
  151. # [23:44] <fantasai> Splitting out the commands and learning more about what they do is Advanced Topics
  152. # [23:44] <fantasai> The basic thing is
  153. # [23:45] <fantasai> "How do I update my tree" and "How do I push my changes"
  154. # [23:45] <fantasai> Those two need to be dead simple.
  155. # [23:45] <plinss> I don't want to get into advanced topics in our docs of hg, there's plenty of that around
  156. # [23:45] <plinss> we should just focus on basics of using our repo
  157. # [23:46] <fantasai> I consider 'hg incoming' to be an Advanced Topic
  158. # [23:46] <fantasai> and that's on the wiki right now
  159. # [23:46] <fantasai> I also consider 'hg revert' to be an Advanced Topic
  160. # [23:46] <plinss> ok
  161. # [23:47] <fantasai> basic topics are "How do I update my tree", "How do I review my changes", and "How do I check in my changes"
  162. # [23:47] <fantasai> Anything *you* consider and advanced topic probably doesn't belong on the wiki at all :)
  163. # [23:47] <plinss> :-P
  164. # [23:48] <plinss> how many spec editors do we really have that don't get the basics of VCS?
  165. # [23:48] <fantasai> Things like offline commits, hg revert, and other handy tools should be in a separate section.
  166. # [23:48] <fantasai> from Basic Topics
  167. # [23:48] <fantasai> plinss: People understand the concept of a VCS. That's different from learning how to use it.
  168. # [23:49] <fantasai> s/it/a specific one/
  169. # [23:49] <fantasai> plinss: Also, a significant number of our spec editors don't use the command line
  170. # [23:49] <plinss> really?
  171. # [23:49] <fantasai> yes really
  172. # [23:49] <plinss> scary
  173. # [23:49] <fantasai> like, all the ones at Microsoft IIRC
  174. # [23:49] <plinss> they have TortoiseHG...
  175. # [23:50] <fantasai> That's not the command line, now, is it :)
  176. # [23:50] <plinss> same operations, just point and click
  177. # [23:50] <fantasai> My point stands.
  178. # [23:50] <plinss> ok
  179. # [23:52] <plinss> while I'm not opposed to good documentation, part of me wonders if we're over thinking this, I'd think spec editors would be more DVCS savvy than test authors, and what we had for the test repo was OK then...
  180. # [23:55] <plinss> IMO there's enough documentation explaining Mercurial already on the web, our docs should only focus on the specific issues of working with our repo and should point to other existing docs
  181. # [23:56] * fantasai looks on the test wiki for instructions on using HG and fails to find them... :/
  182. # [23:56] <fantasai> plinss: We had a guide to migrating from Subversion.
  183. # [23:56] <plinss> http://wiki.csswg.org/tools/hg#more-information
  184. # [23:57] <fantasai> plinss: Too much detail
  185. # [23:58] <fantasai> plinss: We need a 2-screenful "this is how you make an edit". Otherwise it's frustrating.
  186. # [23:58] * Joins: jdaggett (jdaggett@180.235.8.216)
  187. # [23:59] <plinss> I hear you, and I'll work on it this afternoon. I just don't want to go crazy with hg docs.
  188. # Session Close: Tue Feb 28 00:00:00 2012

The end :)