00:08
<zewt>
well, as predicted the option to stop chrome from wasting a ton of tab space to tell me my name no longer works
00:09
<zewt>
why does everything gradually turn to crap?
03:36
<roc>
2nd law of thermodynamics
05:51
<annevk>
Domenic: thank you, but I think I should just slowly learn how it actually works rather than doing things one layer of abstraction away
07:38
<MikeSmith>
annevk: so after getting my environment set up to build the spec, I now wonder why we don't just move the html-build tools directly into the html repo
07:39
<MikeSmith>
having them in a separate repo results in needing to do some klunky stuff to be able to make it work
07:40
<MikeSmith>
e.g., in my case I just made symlinks to ../html/source and ../html/images etc
07:40
<MikeSmith>
because I don't want to do what the readme says and actually copy the files over
08:18
<annevk>
MikeSmith: I suspect Domenic has it setup like that because it made sense to do it that to run the whole thing on the server
08:24
<MikeSmith>
annevk: OK
08:24
<MikeSmith>
it doesn't cause me any real heartburn
08:25
<MikeSmith>
but that said, if more people start using it I reckon they might run into problems/confusion and post questions asking how to fix/troubleshoot it
08:25
<MikeSmith>
would be nice to try to preempt that if possible
08:25
<annevk>
MikeSmith: yeah, I recommend sorting it through with Domenic
08:25
<MikeSmith>
hai
08:25
<annevk>
MikeSmith: I haven't really taken the time to look into it yet
08:27
<MikeSmith>
k
08:32
<annevk>
Heh, https://wiki.whatwg.org/wiki/GitHub seems due for an update
08:33
<annevk>
I was wondering where to document the commit message and merge guidelines
08:37
<MikeSmith>
annevk: for now, could flip on the wiki for https://github.com/whatwg/html
08:38
<MikeSmith>
if there's some reason to put that stuff anywhere other than in .md file in the repo root
08:39
<annevk>
MikeSmith: I don't really want to start using GitHub wikis
08:51
<MikeSmith>
annevk: good
08:53
<MikeSmith>
so maybe just a separate file called HOWTO.md or USING_GIT.md
08:53
<MikeSmith>
(if not in the main readme)
10:20
<annevk>
MikeSmith: seems like it should be in a CONTRIBUTING.md file as you mentioned elsewhere and per https://github.com/blog/1184-contributing-guidelines
10:21
<annevk>
MikeSmith: though it's kind of a pain to keep that up-to-date across various repositories
11:04
<MikeSmith>
ah yeah, I didn't understand that you wanted to have it for all the repos
11:04
<MikeSmith>
had only been thinking about HTML
11:48
<MikeSmith>
annevk: I posted http://stackoverflow.com/questions/32296220/sharing-a-contributing-md-file-across-multiple-github-repos to see if SO produces any good ideas
13:01
<annevk>
MikeSmith: ah, nice
15:27
<frewsxcv>
I wonder if git allows soft links to point to a file within a git submodule
16:26
<Domenic>
MikeSmith: see the bottom todo line in HTML-build repo
16:27
<Domenic>
Also, I think we don't want to be just moving issues to GitHub without resolving them, as that creates a lot of unnecessary email for everyone,
16:54
<deltab>
frewsxcv: symlinks? I don't think git cares where they point
22:52
<MikeSmith>
Domenic: OK (about moving issues)
22:53
<MikeSmith>
Domenic: the two or so I moved I did so because I think we can get more visibility at Github for them can we can just keeping them in W3C bugzilla
22:54
<MikeSmith>
and those two are sorta explicitly soliciting help from any contributors willing to spend some time writing a script to generate the indexes
22:57
<MikeSmith>
so my thinking was that we're more likely to get somebody volunteering if there's an issue at GitHub for it
22:57
<MikeSmith>
or maybe you were
22:58
<MikeSmith>
*you were just saying that we should also keep the W3C bug open until something actually lands for it
23:00
<MikeSmith>
anyway, as I said, there are no other W3C bugs that I was thinking should just be moved other than the ones I moved already
23:06
<MikeSmith>
Domenic: about the "Don't require throwing everything into one directory before doing the build..." thing, thanksマI'll write up a patch to review and raise a PR for it