02:07
<zoey>
Should I just start finding bugs in the HTML script?
02:12
<annevk>
hey zoey
02:12
<zoey>
hi
02:13
<annevk>
zoey: http://krijnhoetmer.nl/irc-logs/whatwg/20151023#l-80 has a conversation with someone else where I tried to explain the basics
02:13
<annevk>
zoey: the basic goal is fixing issues in whatwg/html's "source" resource
02:13
<annevk>
zoey: which is a giant HTML file
02:14
<annevk>
zoey: that happens to be the HTML standard
02:14
<zoey>
Oh okay
02:15
<zoey>
thank you
02:16
<annevk>
zoey: I'll try to get to your email in a bit
02:17
<zoey>
sure
02:17
<annevk>
zoey: which file did you find the colspan="2" in?
02:17
<annevk>
zoey: doesn't seem to be source, at least not on that line
02:17
<zoey>
the one whose link you sent me
02:17
<zoey>
let me check
02:20
<zoey>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28076
02:20
<zoey>
line 662
02:20
<annevk>
oh, I think you might have misunderstood
02:20
<annevk>
that is a bug report and describes an issue with whatwg/html's source document
02:21
<annevk>
Bugzilla might have issues of itself, but they are not important to this project
02:21
<zoey>
Ohh
02:22
<zoey>
can you please send me the link again?
02:22
<annevk>
zoey: you mean https://wiki.mozilla.org/Outreachy/2016/December_to_March#Contribute_to_the_HTML_Standard.21?
02:23
<zoey>
No, the link you sent for me to find an error, so that I could get started
02:25
<annevk>
So the link I gave you was https://www.w3.org/Bugs/Public/show_bug.cgi?id=28076 which describes a problem you could attempt to fix
02:29
<annevk>
zoey: you can also find another problem to fix by following the links to issues and bugs given in the "Contribute to the HTML Standard" section I linked to before
02:39
<zoey>
ok thanks i 'll straight get down to this now
02:42
<annevk>
zoey: enjoy!
06:51
<MikeSmith>
big congrats heycam|away https://twitter.com/heycam/status/659243858509697024
06:51
<MikeSmith>
you look very distinguished there
06:52
<MikeSmith>
now take a vacation and come visit me in Tokyo
07:10
<hober>
MikeSmith: i should have extended this trip so i could visit
07:11
<MikeSmith>
hober: come in the spring and we can all have hanami party under the cherry trees
07:12
<hober>
YES
07:13
<hober>
actually that's what i did when i was last in tokyo
07:13
<hober>
though sadly not with you. iirc you were out of town
07:13
<MikeSmith>
ah yeah
07:15
<MikeSmith>
hober: well you didn't do it in my neighborhood though; where I live now I have two big cherry trees just 20 yards away from my place, just waiting for you
07:15
<MikeSmith>
btw whoever made http://w3cmemes.tumblr.com/post/132069383207/brad-chooses-his-new-fido-challenge-method I love them
07:17
<MikeSmith>
it even looks *exactly* like Brad, but with 75 extra pounds, and a tiny bit less hair, and scarier
07:54
<jgraham>
53 minutes into meeting on future of HTML; first mention of WHATWG
07:54
<gsnedders>
Woah.
07:54
<gsnedders>
so, is XHTML2 the future?
07:57
<jgraham>
Goodness only knows. I feel like people in this conversation are working from the position that WHATWG doesn't exist.
07:59
<gsnedders>
But the W3C is a standards org. WHATWG is just a bunch of people conspiring!
08:00
<jgraham>
Now Charles is advocating delta specifications
08:12
<zcorpan>
nox: problem in the spec or some impl? (re bufferedAmount)
11:57
<JeanCarloMachado>
/msg NickServ identify wisdom20
11:57
<JeanCarloMachado>
oh crap
13:13
<smaug____>
SW spec if oddly written. It doesn't first tell what some method does. It just has the algorithm
13:13
<smaug____>
I have no idea from the name of matchAll what it does
23:29
<zcorpan>
https://medium.com/@stevefaulkner/thoughts-on-notes-from-the-future-of-html-session-at-tpac-1c2f6f204cea#.19klrh3n7 hmmmm... what if w3c would publish a webdev version of the spec, without the impl requirements?