| 11:45 | <Noam Rosenthal> | Thanks @jstenback:matrix.org! Some feedback: I think the topics for the aria discussion don't need that much time, as well as the responsive image topics which might be ok with one hour. We might want to give custom attributes more time if @keithamus:matrix.org would need that. Also the mutation observer topic is together with @keithamus:matrix.org. - The module stylesheet discussion should be together with csswg so we should coordinate if possible. - perhaps my first topic can swap with one of the Friday topics? Thrusday seems really packed with issues I present and people might need a breather from hearing me :) |
| 12:56 | <Alan Stearns> | We are coordinating around the module stylesheet session (it’s on the CSS agenda as a breakout) |
| 14:47 | <Noam Rosenthal> | We are coordinating around the module stylesheet session (it’s on the CSS agenda as a breakout) |
| 16:03 | <mgaudet> | (I am trying to swing back to this with tests -- just snowdrifted under other things, so probably next week unfortunately) |
| 18:37 | <TabAtkins> | What was the details here, Anne? |
| 19:03 | <annevk> | If you click "More" in OP there's the output, no? And our CI didn't have such output. |
| 19:49 | <TabAtkins> | Ah whoops, didn't realize where I was supposed to look. |
| 19:59 | <TabAtkins> | Ah, found the issue. Well, the issue is exactly what the error message says - Bikeshed looks for repository info locally (so it finds it when you run locally, from the spec's repo) but then it can't find that info when it's run externally. Looks like WHATWG shoudl be able to easily add a computed Repository metadata to handle everything, tho. |
| 19:59 | <TabAtkins> | (And, amusingly, if you do make remote, it doesn't give errors but it does link to the wrong repository; all the issue links point to the spec-generator repository instead, lol) |
| 20:08 | <TabAtkins> | all right, pushed an update to y'all's boilerplate that should solve this for everyone |