Skip to content

Meeting 2016 01 25

Jump to bottom Edit New page
Lars Bergstrom edited this page Jan 25, 2016 · 1 revision

Agenda items

Attending

  • Manishearth, ajeffrey, bholley, jdm, larsberg, mbrubeck, brson, SimonSapin, till, jack, pcwalton

Last week

Build time trend

  • jdm: We now have integration with travis that reports how long Travis builds take to a dashboard provided as a service. Unclear how much value this has, but it's data we can track over time! Only reporting since Thursday at this point.
  • mbrubeck: We've passed the 200 crate mark in our Cargo.lock file! Includes dev dependencies, but woo-hoo!
  • jdm: Average travis build is about 27 minutes.
  • jack/till: Not getting any data out of that site...
  • jdm: I can see it in both Firefox and Chrome. Something wrong with keen.io, perhaps?
  • larsberg: We should be getting MUCH bigger GCE instances soon, btw.
  • jdm: Of course, we could possibly integrate this with our buildbot stuff, too...
  • jack: Please file an issue about that! Need to turn off uBlock for that site to work!

Student projects

  • jdm: People talked about some ideas, but we need to start aggregating more ideas. There are both the brainstorming ones as well as a new one about project proposals: https://github.com/servo/servo/wiki/Project-proposal-deadlines and https://github.com/servo/servo/wiki/Project-proposal-deadlines .
  • jdm: Between students and classes and other mentoring programs, we have a lot of opportunities. I've started putting down potential ideas that are worth triaging on the wiki page https://github.com/servo/servo/wiki/Student-project-brainstorm. Please drop ideas in there, even not fleshed out stuff!
  • ajeffrey: I'd be interested in mentoring a project related to WASM. Not sure what, yet, though... ideas that vague welcome? Or stuff that's more concrete?
  • jdm: Don't mind really vague ones, as long as it's understood that if it's too vague, I may come back in a month or two.
  • ajeffrey: What's the timetable?
  • jdm: There are ongoing requests. I just want things here that we can flesh out and assign to people.
  • ajeffrey: I'll add something, then!

Homu maintenance

  • jack: Last meeting, we decided to fork. Then, barosl appeared. Manish is going to be a committer to upstream. Our current status is that we will maintain our fork and merge in experimental PRs as they mature.
  • manish: Not sure; he said that if he needs one, he'd make Manish one, but he didn't do so yet. I'm perfectly fine with maintaining a fork and syncing up regularly.
  • jack: Should push to get you as a committer, otherwise upstreaming will be difficult...
  • manish: I don't think getting stuff upstream is a huge concern. We can keep pulling their PRs to us. Not a big deal to keep in sync.
  • jack: We discussed with edunham, too, and if Rust needs to do anything, we will share our homu fork with them.
  • manish: Homu hasn't been updated for Rust for ~6 months.

Windows

  • larsberg: It happened! Thanks to everyone who pitched in on the reviews and vlad for doing the original work! I'm working on getting a CI builder online.
  • jack: Is it like linux/mac where it Just Works, or is it like android where it's slow and needs polish?
  • larsberg: Slow, needs polish. Release build is usable. Got it running under the VS profiler. Currently compile with msys rust instead of msvc rust, so no debug info. Profiler/debugger isn't that useful right now. Fontconfig performance is much slower than linux where font code is better tuned. Not as miserably bad as android. Definitely something to tackle on non-linux platforms sooner rather than later.
  • jack: Good bug here for someone with Windows API experience wouldbe to replace font stuff with actual native. Would like to get off of freetype.
  • jdm: More complicated than ./mach build?
  • larsberg: Yes. Using msys environment, and no less than three versions of python that get installed. mingw, system, and msys Complications about mach vs. spidermonkey vs. msys. I'll put stuff in the README. I'm hoping to reduce the number of pythons by one.
  • jack: Ideal state might be system python and that's it?
  • larsberg: System + mingw would be ok. Having to use msys one makes things wonky.

Meeting times

  • jack: Everybody but pcwalton filled it out. If we want the meetings on the same day, it would be Wednesday. The times that seemed best then are for the "late" meeting, 5 or 6PM Pacific, and "early" was 10AM Pacific.
  • jdm: I'm not a huge fan of 8pm & 9pm meetings for that "late" one.
  • ajeffrey: Same here. Nothing actually blocking it, but... it's not lovely.
  • jack: Current meeting time is fine on the early meeting. There's also 2PM Pacific on Mondays worked for most people. lars&jack can move their meeting. So rough for Manish & Glenn, but maybe that's way too early for them? But it relies on Glenn waking up way too early.
  • till: It's nice b/c people in the EU could potentially join... whereas 4AM not so much.
  • jack: I'll hold out for feedback from ms2ger, then, and try to close the loop here.
Add a custom footer
Add a custom sidebar
Clone this wiki locally