> 2) Move webrender and webrender_traits back into the Servo repository. > > Because WebRender and Stylo are the two biggest projects that will > need to be worked on in a cross-cutting way across Firefox and Servo, > we'd like to have them out of a separate GitHub repo (with its "update > version, PR, cargo publish, pull down, repeat" workflow) and in the > one that is being tested and co-landed with Firefox. We plan to push > webrender to crates.io to ensure it is still separately usable by > other projects.
WebRender has a small and stable API. This API didn't even need to change in WebRender 2 from my understanding. This means we'll be moving a very low coupling dependency into servo whereas in the past we have pushed to move these out. Why does the plan require this be moved into Servo? The autolander setup is the same, and it would seem we could just replicate the same setup as is being proposed for servo/servo. Here are some questions around this that I think are worth answering before deciding: 1) If we go down this path, when do we propose to do it? Once WebRender 2 is landed? Landed and default? Now? 2) Do we expect WebRender 2 to have any downstream other than our (or other) browser engines? 3) How will this affect development velocity? For example, will we now have to wait for full servo builds to do testing? As I recall this is the main reason it is separated in the first place. 4) What does the alternative look like? In the meetings and documents I was in, we focused heavily on the servo/servo case, and the other dependency cases where not discussed as much. I assume those will be handled by something better than what we are doing now; do we know what that looks like yet? jack. _______________________________________________ dev-servo mailing list [email protected] https://lists.mozilla.org/listinfo/dev-servo
