Proposal to make m-c the canonical home of WebRender

[Kartikaya Gupta]

As a heads up to anybody who wasn't at the WR meeting today, there is a proposal to make mozilla-central the canonical home of webrender. The Github repo would still exist, we would just sync it from m-c instead of the other way around. The proposal and possible implementation are in google docs [1], [2]. Please take a look in the next day or two if this is relevant to your interests and leave comments on the docs.

Thanks!

[1] https://docs.google.com/document/d/1dUAJ4bfwHyD2jAnTvOrPd1WWlUHzmH3UZ2km1GFS0cE/edit?usp=drivesdk

[2] https://docs.google.com/document/d/1s4ixKWBS-tMjnd8YQ8mA5ijsf0Gy-9ukJ_QbFTEi5wE/edit?usp=drivesdk

[Lars Bergstrom]

Thanks for sharing!

Did you reach out to any member of the Servo core team (https://github.com/servo/servo/wiki/Governance#core-team)? Anything that impacts workflow on or requires changes to Servo repositories or projects should be designed in conjunction with that team.

Sorry if I missed stuff around this discussion! I've been stuck in the planning exercises and probably won't come up for air for another couple of weeks. As any change from the status quo will definitely impact the mixed reality programs, which rely heavily on Servo, I'd ask that you hold off until we've been able to asses that impact. In particular, staffing decisions from the in-flight planning process will impact internal and external resourcing decisions relative to this project.

Thanks,

- Lars

_______________________________________________
dev-tech-gfx mailing list
dev-te...@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-gfx

[Kartikaya Gupta]

We haven't officially contacted the Servo core team yet (although I
guess maybe this email thread counts now) since the plan was (and
still is) being figured out. FWIW we would like to minimize the
disruption to existing workflows as much as is feasible, but if you
have specific things you'd like to call out please do so. Also for
context the main motivation here is from the Firefox org to make sure
critical components are in-tree and follow a unified process for
easier tracking by Firefox stakeholders (sheriffs, release, project
mgmt, etc.).

[Lars Bergstrom]

Thanks - sounds good! Josh said that he's in the loop now, and I'm confident that we can find something that works wonderfully for all the projects dependent on WR. Look forward to chatting more soon!

- Lars