Meeting 2015 09 28

Agenda items

• meeting time change redux (jack)
• Should TWiS & contributor stats also track our dependencies? If so, which are in vs. out? (larsberg)
• Script crate (and others?) rebuilding when they don't need to (gw)
• Webrender update - https://github.com/glennw/webrender/wiki (gw)
• app units + servo types crate (gw)

Attending

• brson, larsberg, jack, edunham, gw, mrobinson, manishearth, frewsxcv

Last week

• Team updates: http://benjamin.smedbergs.us/weekly-updates.fcgi/project/servo

New meeting time?

• jack: gw is the only one in this timezone, so maybe do this whenever works for him. Move to Tuesday?
• gw: It's currently Tuesday for me. (10AM). Can move an hour earlier, but more than that is tricky.
• larsberg: Why were we moving it? Other than off of Korea time :-)
• jack: jdm has a conflict. And somebody else 1/2 the time. But, another time on this day is also bad. Maybe Tuesday US / Wednesday gw? That satisifes conflicts. Objections?
• larsberg: Maybe both to Tuesday US or I'll be confused :-)
• jack: I'll send mail to the list.
• larsberg: Daylight savings, gw?
• gw: We don't have it. Can have it on Pacific instead, if that's better for you.
• jack: Would be useful for the US people. I will take advantage of that offer!

Reporting on other projects

• Larsberg: I'd like to track more things. Which ones?
• frewsxcv: Just the stuff in our org.
• jack: Sounds good!
• brson: Interested in this for Rust, too. Often failing to acknowledge others.
• jack: Should also have the RFCs repo?
• brson: Share any scripts you write!
• jack: Luckily, if you add too many, there's no traffic, so no problem. Send an e-mail that you're going to make that change!

Script crate rebuilding

• gw: SCript rebuilds very often when no apparent reason.
• jack: In the past, been that the configure script or something is touching a file it shouldnt' be. Also if you checkout code because of how git does timestamps.
• gw: I don't have repro steps, but I can see it after two builds.
• jack: Can get the repo steps. Also can do the rebuild manually without cargo to see. There might be something in our makefile.
• larsberg: RUST_LOG=cargo::ops::cargo_rustc::fingerprint It's ugly, but possible. --verbose why would be awesome. In pcwalton's recent case, it was related to an editor autosave-type file.
• gw: I'll check the fingerprint log. It's not related to the git checkout in my case, I think.
• jack: Do file bugs if you notice spurious builds. They're huge problems and we should fix them, particularly with script.

Webrender

• gw: There's a link ( https://github.com/glennw/webrender/wiki ) with an overview, benchmarks, and graphs! Please take a look. Seems promising, but with the caveat that it doesn't support 100% of functionality.
• jack: This is probably the most well-documented feature we've implemented in Servo!

app units + servo types crate

• gw: Other related thing is that I've been developing this as a standalone crate and my own test project I can build against it so I don't have to suffer Servo build times. It's been really handy! But, a few types in Servo are relied on. Main is appunits type. If we want to build it separately, the easiest way is to put app units in its own crate and maybe a servo types crate. Pulls out a few things from the util crate. Only painful things is that it pulls out ToCss, which relies on cssparser, so I reversed the order on that.
• jack: I think we've debated it before and if it should go in rust-geom. Not a lot of opposition, just laziness prevented it. Seems like a fine place.
• gw: euclid?
• jack: Yes :-) Seems like one way to resolve that issue. What else would we want in a servo types crate?
• gw: Simple types. Can do without them, but like the image format enum, a few other bits (pipeline id). Simple C-style enums & wrappers over u32s. Without, a little conversion step is required. Not a big deal.
• jack: Does util depend on something?
• gw: Everything - azure, mozjs, layers, cssparser, ipc-channel, rust-selectors.
• jack: Yeah, just pull them out. Can still build it from cargo with a simple repo. For app units, either types or euclid is fine.
• gw: Only bad thing is that I need to push a dependency onto cssparser. I don't have a problem with that, but should check with SimonSapin.
• jack: Since mbrubeck did a bunch of the euclid work around typed struct, might just confirm with him, too.
• gw: If they're happy with it, I'll add those separate crates.
• jack: I think that's a good thing.