Meeting 2014 11 10

Servo Meeting 2014-11-10

Another workweek agenda brainstorming! https://etherpad.mozilla.org/Servo-workweek-2014-12
Assign owners to action items from the workweek, at the bottom of https://etherpad.mozilla.org/Servo-workweek-2014-11
Assess CSS features implemented on every PR? (yichoi)

jack: Add them to the etherpad.
larsberg: If you want to coordinate with other teams, setting that up sooner is better. They're all organizing their schedules right now. SpiderMonkey team has asked, Platform team has asked... we're popular right now.
jack: We should take advantage of this workweek. At least for SM, we have stuff for several hours. Graphics, too. Most of our grahpics action items require us to talk with them. So, please fill in things you think of on the list. The Portland workweek is only a couple of weeks away.

larsberg: Some of the stuff doesn't have names assigned to them, and some should be obvious, but I'd like to make sure nothing that we agreed to do falls through the cracks.
jack: And... all assigned!

jack: Do you just want the CSS features documented on every PR, or something else?
yichoi: I saw Patrick's mail. As every patch is landed, it would be nice to have a list of the features like Patrick did automatically generated. Is this possible?
mbrubeck: He had a google doc / spreadsheet. We could just keep that up to date, but it seems like it would be more reliable to have something in the tree.
jack: The CSS property usage chart?
yichoi: OK, I think that is reasonable.
mbrubeck: To update the google doc?
yichoi: If we can use other pages, like chromium's. Can you make another page, like chromium's, instead of google docs?
jack: Could put it in tree...
larsberg: We could generate it at the same time we do our doc build; just process the information from the .mako file then.
jack: I will file a bug. Then, when people do PRs, we can just tweak that list.

jdm: When we implement the full CSSOM, we will really only want to support the properties on element.style that we have support for in Servo. Keeping that up to date with the ones supported in the style crate... I don't have a good mechanism for it yet.
jack: How do you disable it now?
jdm: Hand-added to the IDL. Lots of duplication.
mbrubeck: We could generate the IDL from mako and then RUst from the IDL!
jdm: Yes!
jack: MAybe tweak the IDL parser to skip things that have comments...
jdm: Still have two different files (mako and IDL) you have to keep in sync.
larsberg: Sort of like to have SimonSapin weigh in on this as well.
jack: I'll open a bug and CC SimonSapin on it.