Skip to content

Meeting 2013 04 01

Jump to bottom
brson edited this page Apr 1, 2013 · 1 revision

Attending

azita, brian, josh, simon, jack, patrick, dave

Agenda

  • First meeting, schedule
  • intros
  • Rust 0.6 updates
  • License
  • Dependency updates
  • Goals / milestones

Meetings

  • azita: is this a good time and day for this meeting?
  • jack: yes, could go earlier
  • josh: fine
  • azita: Since this is our first meeting, introductions?
  • azita: Research team manager. CA
  • brian: Rust/servo team member. CA
  • jack: New last week, full time on servo. NM
  • josh: Officially on servo, but often on Firefox. Working on expanding code generation for DOM. Based in Toronto
  • simon: Joining on May 20, working on gecko layout, servo and CSS specs. Based in London.

< also patrick: Rust/servo. CA. not present>

<discussion about simon's schedule on servo>

  • azita: discussing a servo work week. research team will be having one on april 8, maybe have a seperate work week for servo
  • jack: available, depending on time. unavailable week of april 15 and first week of may.
  • simon: not available in may and early june. april would have to check. mid-june available.
  • brian: maybe we can think about this as we get settled into the project

Syntax changes

  • jack: Updating for 0.6. Almost done for the deps. Trouble with mozjs
  • jack: Pretty straightforward.

License

  • jack: What's the story?
  • brian: current consensus seems to be MPL, but fair number of people want something more permissive.
  • jack: how does this decision affect samsung?
  • brian: don't know
  • jack: Who to talk to about gecko licencesning / embedding. Should find out what they did wrong, how webkit does it, etc.
  • josh: benjamin smedberg (bsmedberg), gervase markham (gerv) might know numbers/stories
  • jack: Can you forward that internal discussion to me?
  • brian: yeah
  • jack: Is brendan going to be at the work week, and can we talk to him about this?
  • azita: No
  • azita: Is this something we need to discuss with samsung?
  • brian: I think it would be a good idea
  • jack: Anybody know webkit license?
  • brian: It's a soup. most restrictive I think is LGPL

Dependency updates

  • jack: Related to mozjs.
  • jack: Asked jdm what it would take to update skia and mozjs
  • jack: I think the latest clang update on OS X has broken things
  • jack: Seeing tons of warnings about c++11 syntax. mozjs has a warning about C return types and linkage.
  • jack: What's the thinking about updating these?
  • jdm: Spidermonkey is going going to be hard. They are removing the C interface.
  • brian: Skia should be ok
  • jack: Ok, I'll get on that and also remove cairo.
  • brian: Do we have any possibliity of getting the build fixed for 0.6?
  • jack: Right now can't build mozjs. Maybe we could rest of the crates fixed.
  • brian: Seems like we won't have this working in time.
  • jack: OS X pushed new OpenGL. need updated skia
  • jack: Is there anyone to ask about this mozjs build problem?
  • patrick: Can ask in #jsapi but they will probably to tell you to upgrade?

Goals and milestones

  • jack: Brian posted some to list about this
  • jack: Build automation looks really important, would be nice to have bors. Is there any way to get some partial bors so we can get pull requests posted to IRC
  • patrick: GitHub has some hooks we could look into
  • brian: need to set them up on each repo
  • jack: i've got a script!
  • jack: since we have a goal to be embeddable, seems like we should have a milestone for it
  • jack: not sure what the milestone would be
  • patrick: how does this differ from crow?
  • jack: what platforms does crow work on?
  • patrick: it's vaporware but could work on all desktop platforms, could do android
  • brian: android embedding is android-specific though
  • patrick: so crow is an app with a web view
  • jack: ok, that overlaps.
  • patrick: let samsung worry about android embedding
  • jack: Any other milestones? We have Acid1, Crow, DOM perf.

Other

  • jack: Last March servo posts, there were some mentions about a pure JS DOM implementation
  • patrick: That was something by David Flanagan (dom.js). Andreas liked it. We decided not to go that route because of performance. You would need an implementation of the layer tree in both JavaScript and DOM, can't share memory so must use message passing (shadow DOM approach?). There was some research project (MS?) that indicated this was too slow.
  • patrick: We got a pull request for rust-http-client for rustpkg integration. That's great. Getting rid of the makefiles should be a goal because we should be dogfooding rustpkg.
  • jack: Does the rustpkg change work?
  • patrick: Have not tested it
  • jack: Also got one for rust-opengles to add some functions
  • patrick: Yeah, I'll merge it. rust-opengles should eventually be replaced by bjz's bindings, which are much more complete. The just don't fully work yet.
  • jack: When I talk to sbillig about rust-http-client I'll ask if he wants to update others for rustpkg too
Clone this wiki locally