Skip to content

Meeting 2015 10 12

Lars Bergstrom edited this page Oct 13, 2015 · 1 revision

Agenda items

  • Welcome new team member, ajeffrey! (jack)
  • Seriously, please update the weekly status update tool, folks (larsberg)
  • Any cross-team Mozlando meetings other than SM and Rust/Servo-in-Gecko? Speak NOW! (larsberg)
  • Trying to clarify Servo governance (https://github.com/servo/servo/wiki/Governance ). We also need to think about a light intent-to-implement/RFC-like process... (larsberg)
  • Review queue is growing: https://github.com/servo/servo/labels/S-awaiting-review (mbrubeck)
  • Quick update on some contracting (larsberg)

Attending

  • larsberg, manish, frewsxcv, jack, glennw, mbrubeck, edunham, pcwalton, ajeffrey

Last week

New team member

  • jack: Say hello to Alan (ajeffrey)! New member of the team starting today! Joins us from Bell Labs, and will be working on Layout & DOM stuff.

Weekly status tool

  • jack: larsberg would like to remind us to update the status! E-mails things out, doesn't make us do a stand-up meeting. Usually, before the servo meeting is best.
  • larsberg: Also good to keep azita, dherman, others in sync.

Mozlando meetings

  • jack: Do we need any others? One to add - get ms2ger and the devtools people in the same room. Not super-formal (2 of them and him?). Need to do some hacking. The DevTools protocols changed and are undocumented. We don't imitate FF closely enough for them to work.
  • larsberg: Two meetings right now: SM on bindings, etc. and on rust/servo-in-gecko.
  • pcwalton: GFX & webrender? Going to talk with jet next week, though maybe figure out then if we need a follow-up.
  • jack: The biweekly rendering/layout meetings with Gecko seem to be continuing apace. We'll probably chat at Mozlando, but don't need to right now. If you need any cross-team collaboration otherwise, let us know! Mainly for hour-long blocks of dedicated and coordinated time.

Governance

  • jack: We have a page on the wiki that attempts to describe our governance. larsberg, I, pcwalton, and dherman have been trying to update this. Currently, lightweight intent-to-implement / RFC process. We're pretty good already at coordinating our decisions, due to the fact that our face-to-face meetings miss people. We'd like to make it a bit more public to make sure folks' input is considered. Also, will be an important signal to other browser implementers on what we're doing.
  • larsberg: We're not in a huge rush to roll it out.

review queue

  • mbrubeck: 43 PRs are waiting for review! Huge number of requests that are stalled. Time to check if you have any assigned to you. If you don't, if they're assigned to others, steal and help. Looking at the huge number opened since Friday, not surprised we're having trouble keeping up. May need more reviewers, particularly in some areas. Should see if there's anybody who isn't one and should be.
  • jack: 14 reviews are not assigned. Please check the ones assigned to you and clear them. I'll do a pass and assign them.
  • mbrubeck: Leaderboard for number of reviews?
  • jack: Only if jdm isn't on it...
  • edunham: Easy to set up a board of how many open tickets you have...
  • larsberg: You can just look on homu, since we assign the PRs...
  • jack: OOOH! And you can sort them!
  • mbrubeck: The volume of DOM patches is incredible...
  • jack: We did just add two new DOM reviewers - frewsxcv & nox. Hopefully we'll start inflicting these on ajeffrey...

reftests

  • jack: ms2ger is upstreaming our custom reftests
  • larsberg: mrobinson is going to host the HTML viewer & suchlike in the outputs
Clone this wiki locally