[{"author": "Mike Ounsworth", "text": "<p>USB tether your phone!</p>", "time": "2025-07-23T11:19:44Z"}, {"author": "Tim Chown", "text": "<p>rpc?</p>", "time": "2025-07-23T11:21:35Z"}, {"author": "Alice Russo", "text": "<p>RFC Production Center</p>", "time": "2025-07-23T11:21:52Z"}, {"author": "Karen O'Donoghue", "text": "<p>RFC Production Center</p>", "time": "2025-07-23T11:21:57Z"}, {"author": "Tim Chown", "text": "<p>ta</p>", "time": "2025-07-23T11:21:58Z"}, {"author": "Mike Ounsworth", "text": "<p>Can that be defined? What does the RFC Production Center do?</p>", "time": "2025-07-23T11:22:10Z"}, {"author": "Jim Fenton", "text": "<p>Does the concern about WiFi hotspots include iPhones etc. with tethering enabled? That would potentially be a lot of devices.</p>", "time": "2025-07-23T11:22:24Z"}, {"author": "Robert Sparks", "text": "<p>Yes</p>", "time": "2025-07-23T11:22:46Z"}, {"author": "Alice Russo", "text": "<p>@Mike, it's what used to be called the RFC Editor; it's the function of publishing the approved I-Ds as RFCs.</p>", "time": "2025-07-23T11:22:48Z"}, {"author": "Mike Ounsworth", "text": "<p>Thanks Alice!</p>", "time": "2025-07-23T11:23:03Z"}, {"author": "Tim Chown", "text": "<p>ah, that now makes sense</p>", "time": "2025-07-23T11:23:04Z"}, {"author": "Mike Ounsworth", "text": "<p>Wait, USB tethering your phone to your laptop is bad?</p>", "time": "2025-07-23T11:23:42Z"}, {"author": "Jim Fenton", "text": "<p>USB tethering should be OK. It's WiFi tethering that is the concern</p>", "time": "2025-07-23T11:24:48Z"}, {"author": "Mike Ounsworth", "text": "<p>Henk makes a really good point!<br>\nI have in the past done horrible things with makefiles to transform my markdown before handing it to the kramdown build tool. Yeah, that would be impossible to review / edit. Good point.</p>", "time": "2025-07-23T11:29:13Z"}, {"author": "Jim Fenton", "text": "<p>2 approvals in 48 hours, right! :)</p>", "time": "2025-07-23T11:29:57Z"}, {"author": "Rich Salz", "text": "<p>So you're just stuck with editing rfcxml for now anyway</p>", "time": "2025-07-23T11:29:59Z"}, {"author": "Daniel Gillmor", "text": "<p>using {::include }</p>", "time": "2025-07-23T11:30:07Z"}, {"author": "Mike Ounsworth", "text": "<p>That said, for all the reasons mentioned, back-porting RPC team changes made on the XML back to the (pre-transformed) markdown can be a pain.</p>", "time": "2025-07-23T11:32:20Z"}, {"author": "Daniel Gillmor", "text": "<p>i find the easiest way to do that is a simple wrapper \"./compare\" script, which produces .txt output from both the original toolchain and from the RPC's xml, and compares the .txt outputs with each other</p>", "time": "2025-07-23T11:33:08Z"}, {"author": "Daniel Gillmor", "text": "<p>then i tweak the markdown until the comparison shows no significant diffs.</p>", "time": "2025-07-23T11:33:45Z"}, {"author": "Daniel Gillmor", "text": "<p>it's a bit of a pain, but not particularly awful.</p>", "time": "2025-07-23T11:34:12Z"}, {"author": "Martin Thomson", "text": "<p>I do the same thing dkg does.</p>", "time": "2025-07-23T11:39:20Z"}, {"author": "Martin Thomson", "text": "<p>I then do that with the XML.  Which requires a LOT of ignoring stuff.</p>", "time": "2025-07-23T11:39:32Z"}, {"author": "Martin Thomson", "text": "<p>There's a tool I wrote that reduces whitespace changes between documents to help with that.</p>", "time": "2025-07-23T11:39:54Z"}, {"author": "Rich Salz", "text": "<p>you could use <code>tidy</code> with the XML flag</p>", "time": "2025-07-23T11:40:22Z"}, {"author": "Martin Thomson", "text": "<p><a href=\"https://github.com/martinthomson/rfc-tidy\">https://github.com/martinthomson/rfc-tidy</a></p>", "time": "2025-07-23T11:40:44Z"}, {"author": "Martin Thomson", "text": "<p>tidy does work pretty well, but it isn't aware of the inline/block distinctions for RFC XML</p>", "time": "2025-07-23T11:41:10Z"}, {"author": "Martin Thomson", "text": "<p>so it can be a bit off</p>", "time": "2025-07-23T11:41:24Z"}, {"author": "Rich Salz", "text": "<p>Quick skim: clever code! Nice.</p>", "time": "2025-07-23T11:42:37Z"}, {"author": "Martin Thomson", "text": "<p>clever is not usually something to be proud of</p>", "time": "2025-07-23T11:43:02Z"}, {"author": "Martin Thomson", "text": "<p>I would instead say \"hacky\"</p>", "time": "2025-07-23T11:43:12Z"}, {"author": "Martin Thomson", "text": "<p>There is an option in the i-d-template to have that tool run.  The catch is that the comment Carsten adds with markdown source is removed (because it removes comments)</p>", "time": "2025-07-23T11:44:07Z"}, {"author": "Rich Salz", "text": "<p>which is okay if you're doing it for diffs, tho, right?</p>", "time": "2025-07-23T11:44:40Z"}, {"author": "Martin Thomson", "text": "<p>RIght</p>", "time": "2025-07-23T11:49:11Z"}, {"author": "Carsten Bormann", "text": "<p>Please don't use dark mode with a projector</p>", "time": "2025-07-23T11:59:42Z"}, {"author": "\u00c9ric Vyncke", "text": "<p>and not showing on the \"lite\" version</p>", "time": "2025-07-23T12:00:13Z"}, {"author": "Daniel Gillmor", "text": "<p>draft-unicorns-die-die-die</p>", "time": "2025-07-23T12:00:22Z"}, {"author": "Orie Steele", "text": "<p>can I get a link to the repo?</p>", "time": "2025-07-23T12:00:27Z"}, {"author": "Jean Mahoney", "text": "<p><a href=\"https://github.com/martinthomson/sparkle-unicorn\">https://github.com/martinthomson/sparkle-unicorn</a></p>", "time": "2025-07-23T12:00:53Z"}, {"author": "Martin Thomson", "text": "<p><a href=\"https://github.com/martinthomson/internet-draft-template\">https://github.com/martinthomson/internet-draft-template</a></p>", "time": "2025-07-23T12:01:27Z"}, {"author": "Carsten Bormann", "text": "<p>v</p>", "time": "2025-07-23T12:01:47Z"}, {"author": "Carsten Bormann", "text": "<p><a href=\"https://github.com/new?template_name=internet-draft-template&amp;template_owner=martinthomson\">https://github.com/new?template_name=internet-draft-template&amp;template_owner=martinthomson</a></p>", "time": "2025-07-23T12:01:50Z"}, {"author": "Carsten Bormann", "text": "<p>(This is where the above page points to)</p>", "time": "2025-07-23T12:01:59Z"}, {"author": "Daniel Gillmor", "text": "<p>Many thanks to MT for doing this basekine work, but also maybe it could be hosted on <a href=\"https://github.com/ietf/\">https://github.com/ietf/</a> someplace</p>", "time": "2025-07-23T12:02:10Z"}, {"author": "Karen O'Donoghue", "text": "<p>or <a href=\"http://authors.ietf.org\">authors.ietf.org</a></p>", "time": "2025-07-23T12:02:44Z"}, {"author": "Mike Ounsworth", "text": "<p>@MT can you explain the different between</p>\n<p><a href=\"https://github.com/martinthomson/i-d-template\">https://github.com/martinthomson/i-d-template</a></p>\n<p>and</p>\n<p><a href=\"https://github.com/martinthomson/internet-draft-template\">https://github.com/martinthomson/internet-draft-template</a></p>\n<p>I know they both matter for the internals, but I think I only need to know about one of them?</p>", "time": "2025-07-23T12:02:48Z"}, {"author": "Henk Birkholz", "text": "<p>It is of course, actually, <a href=\"https://raw.githubusercontent.com/martinthomson/internet-draft-template/refs/heads/main/draft-todo-yourname-protocol.md\">https://raw.githubusercontent.com/martinthomson/internet-draft-template/refs/heads/main/draft-todo-yourname-protocol.md</a></p>", "time": "2025-07-23T12:02:51Z"}, {"author": "Murray Kucherawy", "text": "<p>@secretariat: Someone is doing some disruptive hammering behind the stage in Castilla.</p>", "time": "2025-07-23T12:05:05Z"}, {"author": "Jay Daley", "text": "<p>Someone is on it</p>", "time": "2025-07-23T12:05:13Z"}, {"author": "Murray Kucherawy", "text": "<p>Thanks</p>", "time": "2025-07-23T12:05:19Z"}, {"author": "Dhruv Dhody", "text": "<p>Is there a place where we have info on what to do when we move I-Ds from personal to WG github org?</p>", "time": "2025-07-23T12:07:24Z"}, {"author": "Dhruv Dhody", "text": "<p>Thanks MCR, that was my question!~</p>", "time": "2025-07-23T12:08:42Z"}, {"author": "Daniel Gillmor", "text": "<p>this is my favorite part of a shoulder-surfing session</p>", "time": "2025-07-23T12:11:17Z"}, {"author": "Lucas Pardue", "text": "<p>The role management is the really annoying part, let's document it</p>", "time": "2025-07-23T12:11:21Z"}, {"author": "Renzo Navas", "text": "<p>In any case, I think we will need a written (or video) tutorial</p>", "time": "2025-07-23T12:12:49Z"}, {"author": "Daniel Gillmor", "text": "<p>someone should send this video to the github UX team</p>", "time": "2025-07-23T12:12:51Z"}, {"author": "Karen O'Donoghue", "text": "<p>right... we need some simple guides and tutorials.</p>", "time": "2025-07-23T12:13:09Z"}, {"author": "Tim Chown", "text": "<p>where's the 'import repo' button? :)</p>", "time": "2025-07-23T12:13:17Z"}, {"author": "Mike Ounsworth", "text": "<p>+1 DKG.<br>\n\"How many IETF experts does it take to import a repo?\"</p>", "time": "2025-07-23T12:13:43Z"}, {"author": "Daniel Gillmor", "text": "<p>+1 MT -- history is really valuable</p>", "time": "2025-07-23T12:14:11Z"}, {"author": "Mike Ounsworth", "text": "<p>Importing the repo also brings over all the Github Issues (both open and closed)</p>", "time": "2025-07-23T12:14:20Z"}, {"author": "Jonathan Lennox", "text": "<p>I believe if you fork the repo you'll get the history but not the issues, if that's what you want</p>", "time": "2025-07-23T12:14:44Z"}, {"author": "Henk Birkholz", "text": "<p>@Jim: gitbot also helps</p>", "time": "2025-07-23T12:15:15Z"}, {"author": "Orie Steele", "text": "<p>The URL for assigning users to roles (such as admin or maintainer) is of the form:</p>\n<p><a href=\"https://github.com/ORG/REPO/settings/access\">https://github.com/ORG/REPO/settings/access</a></p>", "time": "2025-07-23T12:15:25Z"}, {"author": "Carsten Bormann", "text": "<p>Mike: I think Henk was pointing out that the value of these <em>MAY</em> be negative, so do think before you act.  But generally the vaue is pisitive.</p>", "time": "2025-07-23T12:16:13Z"}, {"author": "Carsten Bormann", "text": "<p>Don't make blanket rules here -- WGs are different.</p>", "time": "2025-07-23T12:17:23Z"}, {"author": "Mike Ounsworth", "text": "<p>Personally, I have had multi-year old Github Issues save my bacon when someone asks \"Why was this designed this way?\" and we can go dig up the discussion thread.</p>", "time": "2025-07-23T12:17:32Z"}, {"author": "Carsten Bormann", "text": "<p>In some WGs, documents stay candidate for adoption for a long time.</p>", "time": "2025-07-23T12:17:41Z"}, {"author": "Mike Ounsworth", "text": "<p>(but year, I'm not trying to recommend any blanket thing)</p>", "time": "2025-07-23T12:17:53Z"}, {"author": "Mike Ounsworth", "text": "<p>*fair</p>", "time": "2025-07-23T12:17:57Z"}, {"author": "Carsten Bormann", "text": "<p>Mike: Of course, don't delete the old repo, archive it.</p>", "time": "2025-07-23T12:17:58Z"}, {"author": "Orie Steele", "text": "<p>You can transfer repos and issues, with the correct permissions :)</p>", "time": "2025-07-23T12:17:59Z"}, {"author": "Jonathan Lennox", "text": "<p>Can someone post the repo for the notifications e-mail?  I know it exists but can't find it quickly</p>", "time": "2025-07-23T12:18:05Z"}]