12:45:20 RRSAgent has joined #pub 12:45:20 logging to http://www.w3.org/2015/06/04-pub-irc 12:46:01 sam has joined #pub 12:46:52 r12a has joined #pub 12:51:18 jeff has joined #pub 12:54:28 kaz has joined #pub 12:54:40 phila has joined #pub 12:54:51 ddavis has joined #pub 12:55:01 tripu, my regrets for your prez; I wasn't able to reschedule my meeting in 5 minutes :/ 12:55:10 Zakim has joined #pub 12:55:13 Bert has joined #pub 12:55:54 scribe: denis 12:56:53 zakim, move tech to here 12:56:53 sorry, Ralph, I do not see a conference named 'tech' in progress or scheduled at this time 12:57:02 zakim, move review to here 12:57:03 ok, Ralph; that matches Team_Global(review)8:00AM 12:57:21 zakim, who's on the phone? 12:57:21 On the phone I see Bert, Jeanne, ??P6, Veronica, phila, TimBL, Ted, Richard, Ralph, Sam, Jeff, Xueyuan, Naomi, ??P4 12:57:26 zakim, code? 12:57:26 the conference code is 4562 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), denis 12:57:34 +??P5 12:57:39 zakim, ??P5 is me 12:57:39 +denis; got it 12:57:42 -??P4 12:57:43 zakim, dial ivan-voip 12:57:43 ok, ivan; the call is being made 12:57:45 zakim, call kazuyuki-617 12:57:45 +Ivan 12:57:45 ok, kaz; the call is being made 12:57:47 +Kazuyuki 12:57:59 +??P4 12:58:25 I have made the request to generate http://www.w3.org/2015/06/04-pub-minutes.html tripu 12:58:55 regrets: Coralie 12:59:19 Title: The new publication system: how is that going to help me? 12:59:23 Chair: Antonio 12:59:30 Present+ Antonio 12:59:35 Kenny has joined #pub 12:59:48 +??P7 12:59:57 zakim, 007 is me 12:59:57 sorry, ddavis, I do not recognize a party named '007' 13:00:00 -> https://tripu.github.io/remark/remarkise?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fechidna%2Fmaster%2Fdoc%2Fpresentation.md Today's presentation 13:00:01 zakim, ??P7 is me 13:00:01 +ddavis; got it 13:00:05 +[IPcaller] 13:00:06 zakim, mute me 13:00:07 ddavis should now be muted 13:00:21 Yves has joined #pub 13:00:25 Jean-Gui has joined #pub 13:00:56 +??P11 13:01:18 +Plh 13:01:18 +??P14 13:01:23 xiaoqian has joined #pub 13:01:34 +Shawn 13:01:39 tripu: I want to focus on how the system's going to help team contacts and editors 13:01:42 -Jean-Gui 13:01:47 sam_ has joined #pub 13:02:01 yosuke has joined #pub 13:02:14 MikeSmith has joined #pub 13:02:15 +??P14 13:02:16 -??P14 13:02:17 -> https://tripu.github.io/remark/remarkise?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fechidna%2Fmaster%2Fdoc%2Fpresentation.md#1 Slide 1 13:02:23 jeanne has joined #pub 13:02:42 Zakim, call Mike if you know what's good for you 13:02:42 I don't understand you, MikeSmith 13:02:51 Zakim, call Mike 13:02:51 ok, MikeSmith; the call is being made 13:02:53 +Mike 13:02:56 -> https://tripu.github.io/remark/remarkise?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fechidna%2Fmaster%2Fdoc%2Fpresentation.md#2 Slide 2 13:03:09 tripu: on page 2, we have an overview of the general process 13:03:24 ... your groups might be doing things a different way but it's more or less how it's happening 13:03:26 shawn has joined #pub 13:03:43 ... the important thing to note here is the back and forth between the different roles 13:04:06 zakim, who is muted? 13:04:06 I see Shawn muted 13:04:07 ... the process of fixing issues can happen several times and there are humans behind that so it might be slow sometimes 13:04:12 +Xiaoqian 13:04:14 -> https://tripu.github.io/remark/remarkise?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fechidna%2Fmaster%2Fdoc%2Fpresentation.md#3 Slide 3 13:04:31 tripu: some of the groups and staff contacts are uploading documents to temporary locations 13:04:46 ... the whole purpose is to check with pubrules 13:05:00 ... it would be good to get rid of these temporary locations 13:05:06 jeremie has joined #pub 13:05:14 guillaume has joined #pub 13:05:17 -> https://tripu.github.io/remark/remarkise?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fechidna%2Fmaster%2Fdoc%2Fpresentation.md#4 Slide 4 13:05:27 Zakim, call jeremie-mobile 13:05:27 ok, jeremie; the call is being made 13:05:29 +Jeremie 13:05:32 tripu: on slide 4, we have listed a few problems 13:05:44 liam has joined #pub 13:05:53 ... some people are kept busy for tasks that can be automated 13:06:02 ... it's also difficult to publish very often 13:06:21 +Liam 13:06:34 ... validation of the specs can be cumbersome as well. Might need other people involved to help understanding where are the issues 13:06:38 -Liam 13:06:47 q? 13:06:49 ... and the publication requires people to be awake 13:06:57 -> https://tripu.github.io/remark/remarkise?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fechidna%2Fmaster%2Fdoc%2Fpresentation.md#5 Slide 5 13:07:05 tripu: so let the robots steal our job 13:07:16 zakim, mute me 13:07:16 Kazuyuki should now be muted 13:07:17 -> https://tripu.github.io/remark/remarkise?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fechidna%2Fmaster%2Fdoc%2Fpresentation.md#6 Slide 6 13:07:20 zakim, who is making noise? 13:07:30 ted, listening for 10 seconds I heard sound from the following: Ralph (13%), Sam (18%), Bert (47%), tripu (9%), TimBL (13%), Richard (18%) 13:07:31 -> https://tripu.github.io/remark/remarkise?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fechidna%2Fmaster%2Fdoc%2Fpresentation.md#7 Slide 7 13:07:32 tripu, quit saying everything twice please 13:07:37 zakim, mute bert 13:07:37 Bert should now be muted 13:07:50 +Liam 13:07:57 -Bert 13:08:19 tripu: the slides 6 and 7 describe the ideal situation 13:08:45 +Bert 13:09:07 ... people could publish after each commit or trigger the publication by clicking on a button 13:09:21 ... slide 6 shows how it could be integrated with other system like Github 13:09:33 q? 13:09:57 ... the system should then infer some data, run validators, etc 13:10:03 ... and send feedback to the user 13:10:15 -Shawn 13:10:35 tripu, which slide are we on? 13:11:13 -> https://tripu.github.io/remark/remarkise?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fechidna%2Fmaster%2Fdoc%2Fpresentation.md#8 Slide 8 13:11:19 occasional choppiness, tripu, but not often 13:11:30 tripu: that slide lists some advantages of the system 13:11:54 ... it will be easier to publish more frequently, publish on your own 13:12:05 ... it will save a lot of messages between the different people 13:12:18 -> https://tripu.github.io/remark/remarkise?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fechidna%2Fmaster%2Fdoc%2Fpresentation.md#9 Slide 9 13:12:32 tripu: Slide 9 lists features we have already 13:12:43 ... email notifications being sent to a public mailing list 13:13:06 ... when there's an error, the message contains the error 13:13:20 ... so you know why your publication failed 13:13:26 q+ 13:13:27 q? 13:13:32 ack liam 13:13:32 liam, you wanted to ask if this means dated copies go away (having missed the start, sorry!) 13:13:33 [we plan on targeting those messages to specific groups instead of catch-all alias as it is at present] 13:13:54 liam: are you saying the dated spec goes away? 13:14:17 tripu: I found that we have some specs under /TR but not linked to anywhere 13:14:57 liam: some specs do get uploaded under /TR but not being published later 13:14:58 ack ivan 13:15:09 I admit to being responsible for a couple of TR orphans :-( 13:15:09 q+ to ask, at the appropriate point (maybe later), why docs not going to Rec are not covered and can we not bring them into the system 13:15:20 ivan: does it mean all the notifications go the same mailing list? 13:15:34 q+ 13:15:41 Notifications will be better targeted, as Ted hinted. 13:15:44 ... it means I have to subscribe to the mailing list and will get a huge amount of unnecessary emails 13:15:46 q+ to answer ivan 13:16:04 q? 13:16:07 ack r007a 13:16:07 r007a, you wanted to ask, at the appropriate point (maybe later), why docs not going to Rec are not covered and can we not bring them into the system 13:16:12 tripu: it should be much smarter. So far we don't have a lot of traffic but it makes sense to have it split between different mailing lists 13:16:19 jeanne2 has joined #pub 13:16:47 richard: my WG is eager to use that system but we produce a lot of NOTEs 13:17:00 ... when will we be able to use it? 13:17:08 tripu: at the moment, we only process WDs 13:17:26 ... people have been asking for that on spec-prod@w3.org 13:18:06 ... as much as we would like to expand the type of specs we can handle, we still have a few things to fix for WDs 13:18:12 Notes often start out as Notes 13:18:14 ... it's difficult to give a timeframe 13:18:16 jeanne2 has joined #pub 13:18:19 Notes often start out as WDs I mean 13:18:36 q? 13:18:40 ack jeremie 13:18:40 jeremie, you wanted to answer ivan 13:18:50 ... specberus can already check more types of documents 13:19:05 -Jeanne 13:19:06 jeremie: the reason why we publish to a mailing list because it was the easiest way to do it 13:19:21 ... instead of targeting the requester 13:19:55 ... I recommend you don't subscribe to the mailing list but just look at the archive 13:19:56 jeanne2 has joined #pub 13:19:59 -> https://lists.w3.org/Archives/Public/public-tr-notifications/ Notifications archive 13:20:01 +Jeanne 13:20:05 ... so you don't get too many emails 13:21:00 -> https://tripu.github.io/remark/remarkise?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fechidna%2Fmaster%2Fdoc%2Fpresentation.md#10 Slide 10 13:21:09 tripu: slide 10 lists features we don't have yet 13:21:26 ... for now, we don't have a web UI 13:21:53 ... we handle only WDs 13:22:01 q+ 13:22:25 -> https://tripu.github.io/remark/remarkise?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fechidna%2Fmaster%2Fdoc%2Fpresentation.md#11 Slide 11 13:22:41 q? 13:22:43 ack r007a 13:22:45 q+ 13:22:47 tripu: @1 13:22:49 +[IPcaller.a] 13:23:17 richard: if we have a document that is going to be a NOTE but is current a WD, can we use the system? 13:23:21 q+ 13:23:23 tripu: yes 13:23:26 -TimBL 13:23:29 q? 13:23:31 richard: fantastic 13:23:37 ack phila 13:23:38 ack me 13:23:39 q? 13:23:49 q+ 13:24:00 phila: it doesn't handle FPWD, right? 13:24:08 tripu: no FPWD for now, only ordinary WD 13:24:16 [I note "Transitions" is mentioned on slide 11] 13:25:11 phila: no other standards bodies allow editors to publish like that 13:25:44 q+ 13:26:05 ... it's great but the downside is nobody is going to read a version that can be obsoleted so quickly 13:26:26 ack jeremie 13:26:37 tripu: @2 13:27:18 https://github.com/w3c/specberus/issues/143 13:27:18 jeremie: I'm sorry to Richard but we are not able to publish WD that are going to be NOTEs 13:27:43 ... the details discussed on github #143 13:28:20 ... we are planning to do so, but not possible fow now 13:28:20 s/fow/for/ 13:28:36 ack ivan 13:28:58 ivan: NOTEs are important for IG 13:29:44 ... regarding the exceptions you listed on slide 11, it often happen that a team contact has a friendly discussion with the webmaster 13:29:49 "friendly" 13:30:06 ... when there's an error reported by pubrules 13:30:28 ... sometimes, you get the approval from the webmaster 13:30:29 jeanne has joined #pub 13:30:31 [webmaster and this system is tasked with enforcing w3c's process] 13:30:39 ... is there a way for the system to remember that exception? 13:30:47 q+ 13:30:53 q? 13:30:57 tripu: the exceptions are a headache to handle 13:31:27 ack r007a 13:31:28 +1 -- I regularly link to outside a11y documentation with invalid, but working links 13:31:29 -Plh 13:31:31 ivan: if there's a draft that is not 100% perfect and still pass the system, it would be great 13:31:40 +Plh 13:31:46 guillaume has joined #pub 13:32:17 rrsagent, make minutes 13:32:17 I have made the request to generate http://www.w3.org/2015/06/04-pub-minutes.html jeanne 13:32:29 tripu: we are thinking about adding a list of steps to skip on a specification basis 13:32:46 q? 13:33:17 ivan: we have team contacts for each WG but we need to have a human filter that can approve these errors 13:33:31 ... team contacts can be that filter 13:33:51 +1 to richard 13:34:41 richard: it's great to be able to publish often on /TR because we would prefer to have people review the dated spec instead of the editor's draft 13:34:42 ack ted 13:34:51 +TimBL 13:35:23 +1 to the workflow r12a describes; publish often with some identifier that makes it practical to tie comments to identified versions 13:35:45 ted: handling exceptions is pretty complex. We are thinking about having a general exceptions system 13:36:16 q+ 13:36:27 i would note that we, as a horizontal activity, are constantly reviewing specs and want to be able to review dated versions too 13:36:41 ... when you go to CR, you want your document to be clean and not have the exceptions 13:37:03 ack ivan 13:37:04 +koalie 13:37:13 tripu: the rules exist for a reason 13:37:28 ivan: I agree we have to be strict when we go to CR, PR or REC 13:37:39 present+ Coralie(second_half) 13:37:42 ... and I wonder if we want to keep the current system for these 3 13:37:45 [Coralie arrives] 13:37:52 -Xueyuan 13:38:02 ... for WDs, it should be fine 13:38:04 [phrased another way - if you want to use it, conform. if you want exceptions, go through manual appeal process] 13:38:15 q? 13:38:23 ... I'm a bit worried with an automatic system 13:38:24 timbl has joined #pub 13:38:31 +Xueyuan 13:38:40 ... it has a tendency that only the automatic way will be used 13:39:17 i wonder whether there are identifiable things that must be correct, eg. patent policy or copyright statemnt, but other things that require less rigourous conformance 13:39:30 -> https://tripu.github.io/remark/remarkise?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fechidna%2Fmaster%2Fdoc%2Fpresentation.md#12 Slide 12 13:39:44 tripu: I hope the advantages of such system are clear 13:39:51 -> https://tripu.github.io/remark/remarkise?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fechidna%2Fmaster%2Fdoc%2Fpresentation.md#13 Slide 13 13:40:08 tripu: now I want to show how the system works for you 13:40:55 ... only the first time a specification is going to be published, you will need someone in the the team to request a token 13:41:20 ... to request a token, you need the shortlink and the source of the spec (where it comes from) 13:41:42 timbl: do you really need those url? can't you get one from the other? 13:41:50 tripu: I think we could 13:42:02 q+ to answer that from Tim 13:42:07 timbl, we are not extracting data from the document at this point 13:42:18 timbl: it should be possible if you follow the spec (on GH for instance) 13:42:27 ivan: if you use respec, the information is already there 13:43:21 darobin: if you change the shortname in the source, you could publish everywhere on /TR 13:43:32 ack me 13:43:32 darobin, you wanted to answer that from Tim 13:44:08 tripu: in this GH example, you could publish everything under the source url 13:44:22 -> https://tripu.github.io/remark/remarkise?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fechidna%2Fmaster%2Fdoc%2Fpresentation.md#13 Slide 13 13:44:30 -> https://tripu.github.io/remark/remarkise?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fechidna%2Fmaster%2Fdoc%2Fpresentation.md#14 Slide 14 13:44:50 tripu: then you make sure your document pass pubrules 13:44:57 -> https://tripu.github.io/remark/remarkise?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fechidna%2Fmaster%2Fdoc%2Fpresentation.md#16 Slide 16 13:45:24 tripu: slide 16 shows how you can request a publication 13:45:58 ... you can use your browser directly or CLI 13:46:14 [and of course, in addition to browser and CLI you can build tools that call out to that HTTP API] 13:46:20 ... you'll get the id of the request 13:46:24 -> https://tripu.github.io/remark/remarkise?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fechidna%2Fmaster%2Fdoc%2Fpresentation.md#17 Slide 17 13:46:35 q+ 13:46:44 tripu: and that's it, you just have to wait a bit and get the status of the request 13:47:06 ... right now, we are dumping the result 13:47:22 [where is the documentation for the request parameters (both required and any optional params)?] 13:47:27 q? 13:47:29 [example of code that autopublishes from a build tool https://github.com/w3c/spork/blob/master/cherry-picker.js#L75] 13:47:33 ... the result is not user-friendly and shows the different steps 13:47:34 ack ivan 13:47:57 [The decision is the decision to go with the automated process, right? That is, the group does not need to agree to publish each new version, or does it?] 13:47:59 ivan: I try to combine what you are showing and the way we are using respec in my WGs 13:48:41 q+ to reply to ivan 13:48:50 rkawada has joined #pub 13:48:52 ... we generate snapshots (dated spec) that are sent to the webmaster 13:49:12 ... how can we combine it with that system? 13:49:26 ... does it do all the respec management automagically? 13:49:35 https://github.com/w3c/spec-generator 13:49:44 darobin: the good news is you don't need to do anything 13:50:12 ... respec is supported by the system. It'll call another system called spec-generator 13:50:21 Let's go to page 18, where the manifest is explained. 13:50:26 ... you will actually only need one line in your manifest 13:50:30 https://github.com/w3c/echidna/wiki/How-to-use-Echidna-with-ReSpec-and-GitHub 13:50:34 https://github.com/w3c/echidna/wiki/Setting-up-Echidna-as-a-GitHub-hook 13:50:52 [I suppose the documentation to which darobin refers in his answer to my question is https://github.com/w3c/echidna/wiki/How-to-use-Echidna ] 13:50:58 ivan: great, it does what we do manually 13:51:28 tripu: the next slides 18/19 show what robin was detailling 13:51:37 -> https://tripu.github.io/remark/remarkise?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fechidna%2Fmaster%2Fdoc%2Fpresentation.md#20 Slide 20 13:52:03 tripu: on slide 20, here's how you can use respec with the automatic publishing system 13:52:03 q+ 13:52:12 +??P16 13:52:17 [but it support ReSpec "more" in that you don't need to pre-generate] 13:52:21 ... echidna doesn't care whether you are using respec, bikeshed etc 13:52:26 zakim, ??P16 is me 13:52:26 +rkawada; got it 13:52:30 q? 13:52:33 ... so far we have limited support for spec generators 13:52:34 ack me 13:52:34 ack darobin 13:52:34 darobin, you wanted to reply to ivan 13:52:42 ack r007a 13:53:06 richard: we have to create that manifest and make sure it references every images we have in the spec 13:53:11 -Jeanne 13:53:24 ... the system is not able to find these? 13:53:56 darobin: you could in theory write a tool that could generate the manifest from a spec 13:54:13 ... I suspect echidna requires a manifest instead of parsing the html 13:54:43 ivan: I did something similar when I was converting TR spec to epub 13:54:53 ... and I was relying on that kind of manifest 13:55:03 http://www.w3.org/TR/2012/NOTE-jlreq-20120403/ 13:55:10 ... and it does simplify things 13:55:42 richard: when you have documents like jlreq, maintaining the list of images, it becomes quickly a pain in the neck 13:55:51 q+ 13:56:17 darobin: I understand what you are saying. Please file an issue to modern tooling and I'll look into it 13:56:31 ... it's going to be difficult to have it in echidna 13:56:40 ack jeremie 13:56:44 ... but I'm happy to look at a tool producing these manifest 13:57:08 jeremie: it will be extremely complex for have that kind of tools 13:57:33 [echidna is platform agnostic, not eg github specific. some platform repos sense of relative path might be different that others for us to retrieve over the web] 13:57:42 http://www.w3.org/TR/2012/NOTE-jlreq-20120403/Images-en/img1_3.png 13:57:45 http://www.w3.org/TR/2012/NOTE-jlreq-20120403/Images-en/img1_7.png 13:58:04 http://www.w3.org/TR/2012/NOTE-jlreq-20120403/Images-en/img1_[1-7].png 13:58:12 I have made the request to generate http://www.w3.org/2015/06/04-pub-minutes.html tripu 13:58:22 -Yves 13:58:23 (I'm using an install script for /TR that seems to find images automatically rather well.) 13:58:33 Yves has left #pub 13:58:34 -phila 13:58:40 ... maybe we could use special format to have a list of file with sequential numbers 13:58:50 [basically, you load the document into PhantomJS, and intercept loaded resources as in https://github.com/w3c/spork/blob/master/spork.js#L103] 13:59:11 richard: with many images, the manifest is likely to have errors 13:59:13 [then you need some ad hoc code to differentiate the resources you care about from those you don't as in https://github.com/w3c/spork/blob/master/profiles/html.js#L26] 13:59:25 s/sequential numbers/sequences (numbers, letters, ...) 13:59:34 [it's not technically hard, but it's work :)] 13:59:43 tripu: robin agreed to have that tool ready by the end of the tech talk 14:00:03 -> https://tripu.github.io/remark/remarkise?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fechidna%2Fmaster%2Fdoc%2Fpresentation.md#19 Slide 19 14:00:35 tripu: Slide 19 shows how you can integrate your spec with echidna using a continuous integration tool like travis 14:00:36 -Bert 14:00:51 -> https://travis-ci.org/ Travis CI 14:00:56 https://en.wikipedia.org/wiki/Travis_CI 14:00:59 ... CI tools make it easy to run tasks after each commit 14:01:09 ivan, we often have more images in the directory that are used in the doc, and sometimes different directories (eg. for zh version and en version), so care still needs to be taken there 14:01:28 ... that file .travis.yml is basically all you need to integrate your spec with echidna 14:01:51 -Plh 14:01:51 ... it's getting closer to the long term goal of having everything automatic 14:01:58 q+ 14:02:02 +Plh 14:02:08 -> https://tripu.github.io/remark/remarkise?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fechidna%2Fmaster%2Fdoc%2Fpresentation.md#21 Slide 21 14:02:34 ack ivan 14:02:38 tripu: we are planning to improve the errors messages, UI, etc 14:02:55 -Richard 14:02:59 ivan: when WDs are published, they are announced on the homepage 14:03:11 ... but it was not mentioned during that talk 14:03:23 ... should I get in touch with comm team? 14:03:56 q? 14:03:58 tripu: at the very least, people in charge of that should get the notification and it shouldn't be too hard to plug it to another system 14:04:15 q+ 14:04:19 ack jeff 14:04:29 [you need comments if you want me to finish the manifest tool before the end of the call] 14:04:40 tripu++ 14:04:41 +1 14:04:41 denis++ 14:04:43 jeff: great job. This is something I've heard from a lot of editors. They are very excited about it 14:04:43 +1 14:04:43 jeremie++ 14:04:44 +1 14:04:44 +1 14:04:44 team++ 14:04:48 team++ 14:04:49 +1 14:04:55 jeremie++ 14:04:57 team++ 14:05:01 q? 14:05:06 tripu++ 14:05:09 denis++ 14:06:01 ivan: changing the operations for an existing WG is not that easy I guess. Might not suit a WG that is about to close 14:06:43 Zakim, who's on the call? 14:06:43 On the phone I see rkawada, ??P6, Veronica, Ted, Ralph, Sam, Jeff, Xueyuan, Naomi, denis, Ivan, Kazuyuki, tripu, ddavis, [IPcaller], Plh, Mike, Xiaoqian, Jeremie, Liam, 14:06:46 ... [IPcaller.a], TimBL, koalie 14:06:47 tripu: if some of you have questions about how your WG can migrate to that system, ask us. It shouldn't be too hard, at least in a manual way 14:07:34 q? 14:08:06 -TimBL 14:08:08 -Ivan 14:08:09 thanks tripu 14:08:09 -Kazuyuki 14:08:11 -??P6 14:08:12 -Ted 14:08:12