Servo Meeting 2015-04-13

Agenda items

jack: Has anyone tried it?
larsberg: Yes. I haven't tried the rebase support, but it apparently creates local refs and can then diff between the old and new. https://github.com/servo/servo/pull/5662 is a review I did with it.
jdm: I like that it posts things to github; that's a better default than Critic.
jack: Last time we talked about this nobody expressed huge love for Critic, so it might be worth giving it a try. Doesn't seem to be a downside to experimenting. Not open source and Critic is, but not really any difference in the way we use them.

jack: Most big PRs are through so now is a good time for the upgrade.
jdm: I don't believe it's filed, but I believe ms2ger was going to try it with a newer version.
jack: If it's not fixed, we should get that filed and tracked in number...
larsberg: 2853!
jack: Yeah, can do that and then bring it up in the rust meeting tomorrow if it's still a bug. Sounds like if it's in cssparser the rustup is not even in the Servo crate yet. So we might have more problems past that. WHich etherpad?
larsberg: We usually use this one: https://etherpad.mozilla.org/rustup
jack: Makes sense! Could also have a bug in the tracker, like one for the current upgrade. Otherwise, all the submodule PRs aren't linked together and visible.

jack: Anybody have issues with homu? Seems to be working well...
larsberg: It's working great!
jack: Only bad thing is that when you do "r-" it doesn't say anything, though the queue does instantly update.
jdm: So glad I don't have to go to actual commits and leave comments.
jack: Does the rust one make you do @bors? Or @homu?
larsberg: It has to be the account name that homu runs with.
jack: Could we just do "r+" instead of having a username?
larsberg: I haven't asked him to.
jack: It also just retries the one builder and saves us a lot of rebuild time on retries!

jack: Down to the last few candidates in the current pool. Will be bringing people in for on-site interviews in MV or SF over the next couple of weeks. Things are looking pretty nice! We should have some full-time help soon for the ops and research engineer positions, hopefully...

jdm: Firefox timeline integration has landed! You have DOM events and stuff showing up in Firefox Aurora!
jack: Have you talked with people on devtools about what needs to change?
jdm: Not yet. I suspect it won't be a big change; probably just have to tell them what we support.
jack: Maybe we should schedule some time with them in Whistler. For the same reason we meet with the JS team... to avoid being broken (at least without being told).
jack: Is it also an interesting project to have a standalone thingie that speaks the other end of devtools and spits out the image/data report?
jdm: To be really useful, it would reimplement what the timeline UI already does.
jack: I should look at it.
pcwalton: If we want more instrumentation, we should figure out what we want and do the shortest path there - the timeline view is already really good.
jack: I'm thinking if we changed the async stuff, it would be nice if you could show images of the differences in PRs, etc. Would be nice if it wasn't as manual as it is today.
pcwalton: The chrome people used to export the HTML of the timeline for running against twitter and then print it. That lets you both plot it and upload it somewhere.
jack: I'll play with the firefox devtools on Aurora and see how it looks!