| 00:02 | <GPHemsley> | lists.whatwg.org is down |
| 00:49 | <MikeSmith> | GPHemsley: yeah it as been even since switching to TLS |
| 00:49 | <GPHemsley> | oh |
| 00:49 | <MikeSmith> | some Dreamhost borkenness prevents it from working |
| 07:20 | <annevk> | Domenic: say hi to mkwst |
| 07:20 | <botie> | will do |
| 07:20 | <annevk> | not you botie... |
| 07:24 | <zcorpan> | where's the source for botie? |
| 07:24 | <zcorpan> | seems like it's more annoying than helpful |
| 07:33 | <MikeSmith> | zcorpan: https://github.com/w3c/infobot |
| 07:45 | <zcorpan> | MikeSmith: either there's a bug with $addressed or it's set up wrong for this channel |
| 08:30 | <annevk> | foolip: you around? |
| 08:31 | <foolip> | annevk: yep |
| 08:31 | <annevk> | foolip: I was wondering if for https://github.com/whatwg/whatwg.org/pull/62 we could instead rebase and merge or some such |
| 08:31 | <annevk> | foolip: so all commits just follow the existing ones |
| 08:32 | <foolip> | annevk: I could filter-branch the whole old repo to make it look like it happened inside a subdirectory, sure |
| 08:32 | <annevk> | foolip: failing that a merge commit is probably cleaner than wiping history altogether |
| 08:32 | <annevk> | foolip: yeah, I guess that's what I mean, so we keep a linear history |
| 08:33 | <annevk> | foolip: but also don't lose the commits and blame et al keep working |
| 08:33 | <foolip> | I think that this is actually a good case to have a merge commit, makes it very easy to tell with confidence exactly what was merged |
| 08:33 | <foolip> | A squashed commit also isn't terrible if it points to the commit it came from, if the purpose is history digging |
| 08:34 | <foolip> | well, I'll let you decide, and I will do |
| 08:34 | <annevk> | foolip: meh, merge commit is fine I guess |
| 08:35 | <annevk> | foolip: hmm so if we remove deployment via the cgi script it seems you can remove the cgi script from .htaccess |
| 08:36 | <annevk> | foolip: and it seems we could use --delete for this as well, no? |
| 08:36 | <annevk> | foolip: anything other than the cgi script that would be gone? |
| 08:37 | <foolip> | annevk: some old browser logos, that kind of thing, only files that were once in git history |
| 08:38 | <annevk> | foolip: then --delete seems like the way to go, since leaving them up was more of a side effect of not having proper syncing |
| 08:38 | <foolip> | annevk: just a moment, will push new commits |
| 08:40 | <MikeSmith> | zcorpan: will take a look at the botie config |
| 08:40 | <annevk> | foolip: disabled the webhook |
| 08:40 | <foolip> | annevk: thanks |
| 08:41 | <annevk> | Hmm, changes to resources.whatwg.org ended up sending an email to a w3.org email address? |
| 08:42 | <MikeSmith> | annevk: my address? |
| 08:42 | <annevk> | MikeSmith: see pm, looks like it's meant to be a secret address |
| 08:44 | <MikeSmith> | annevk: http://simpsons.wikia.com/wiki/Kearney_Zzyzwicz |
| 08:47 | <foolip> | annevk: PR updated, see latest commit content and message |
| 08:48 | <annevk> | foolip: .htaccess still has the IndexIgnore line, but we can clean that up later too if you want |
| 08:48 | <annevk> | foolip: I approved the thing |
| 08:50 | <foolip> | annevk: I forgot to git commit --amend, just pushed the changes to .htaccess as well, can you take a look? |
| 08:51 | <annevk> | foolip: r+ |
| 08:52 | <foolip> | annevk: hmm, so https://github.com/whatwg/resources.whatwg.org/pull/63#pullrequestreview-58884348 |
| 08:52 | <annevk> | foolip: yeah? 😃 |
| 08:52 | <foolip> | It's not even a sentence, and I think you don't mean the first line of the commit message? |
| 08:53 | <annevk> | foolip: the first line is the title, no dot |
| 08:53 | <annevk> | foolip: the remainder is the body, uses dots |
| 08:53 | <annevk> | foolip: but I guess we can make an exception for body that contains only a URL |
| 08:53 | <annevk> | foolip: I usually make a sentence of sorts out of it |
| 08:53 | <annevk> | foolip: anyway r+ either way, it's not important |
| 08:54 | <foolip> | ok :) |
| 08:58 | <zcorpan> | foolip: what happened here? https://github.com/whatwg/whatwg.org/issues/26 |
| 08:59 | <foolip> | zcorpan: interesting, automatically closed because I merged in the history of resources.whatwg.org |
| 08:59 | <zcorpan> | aha |
| 08:59 | <foolip> | zcorpan: search my inbox, that was the only case |
| 09:08 | <annevk> | foolip: https://github.com/whatwg/whatwg.org/issues/18 too |
| 09:09 | <foolip> | annevk: oh, right, I can't just search for the same commit |
| 09:09 | <foolip> | trying inbox search again |
| 09:10 | <foolip> | OK, well, that is the only other one I find |
| 09:13 | <annevk> | same |
| 09:21 | <annevk> | Ugh, Travis is having trouble reaching resources.whatwg.org again, the sooner we move that the better |
| 09:21 | <annevk> | Must be DreamHost somehow intervening |
| 09:26 | <foolip> | annevk: has that been happening before? |
| 09:27 | <annevk> | foolip: yeah loads |
| 09:27 | <foolip> | annevk: ok, will prioritize getting that moved then |
| 09:27 | <annevk> | foolip: though only in the last couple weeks, some time before the trouble with the HTML Standard started |
| 09:28 | <annevk> | foolip: basically get The command "curl --remote-name --fail https://resources.whatwg.org/build/deploy.sh && bash ./deploy.sh" exited with 1. |
| 09:29 | <foolip> | annevk: we could get that from git I suppose instead |
| 09:29 | <foolip> | but, just fixing the hosting works too |
| 09:29 | <annevk> | foolip: fetching the whole repo seems worse though |
| 09:30 | <annevk> | foolip: perhaps if we had a Docker wrapper and cached it |
| 09:31 | <foolip> | annevk: I assumed one could just get a single file |
| 10:25 | <annevk> | foolip: ooh interesting |
| 10:27 | <foolip> | annevk: https://raw.githubusercontent.com/whatwg/whatwg.org/master/resources.whatwg.org/build/deploy.sh |
| 10:28 | <annevk> | From GitHub's servers, I see |
| 10:28 | <annevk> | Might be a good temporary fix |
| 10:28 | <foolip> | annevk: if one did that, there'd be no real reason to deploy it to resources.whatwg.org at all |
| 11:25 | <MikeSmith> | zcorpan: OK I just now changed botie config to have `addressing REQUIRED` |
| 11:25 | <MikeSmith> | which I think that should prevent it from saying anything unless directly addressed |
| 11:26 | <zcorpan> | MikeSmith: say hi to annevk |
| 11:26 | <zcorpan> | i guess it worked |
| 11:26 | <zcorpan> | thanks |
| 11:26 | <MikeSmith> | seems so |
| 11:27 | <zcorpan> | botie: say hi to MikeSmith |
| 11:27 | <botie> | will do |
| 12:03 | <annevk> | foolip: I'm back in a bit, but fully back Wednesday to help with things |
| 14:39 | <wanderview> | I was going to ask JakeA a question, but from reading this I guess he's supposed to be playing cricket or something... https://publicholidays.co.uk/summer-bank-holiday/ |
| 14:43 | <Ms2ger> | Or watching the cricket, that's possible too |
| 14:43 | <Ms2ger> | Something unrelated to cricket should be unlikely, though |
| 15:31 | <gsnedders> | Ms2ger: You don't even have a bank holiday yet you're watching the cricket! |
| 15:32 | Ms2ger | denies watching anything |
| 15:32 | <Ms2ger> | Radio's on, though :) |
| 16:44 | <TabAtkins> | Protip: don't accidentally cron a git-updating script from the root account, then switch it to properly run on your user account, without remembering to update all git objects to be owned by your account again. |
| 17:48 | <Alming> | Hello |