I think one important aspect here is to separate out the concerns of vendoring code in-tree vs where that code is developed. It sounds like Gecko has lots of technical requirements about why and how code lives in-tree, but the more important bit here is how it changes over time.
What Yehuda was saying about how forking or syncing having downsides I think is quite important for Rust code in Gecko, as this may run the risk of splitting the ecosystem on various boundaries (e.g. the "gecko rust-url" and the "upstream rust-url" or something like that). Along those lines I think it's very important to drill down into exactly what concerns there are about having these components developed in the Servo-style as they are today. It sounds like there's some hesitation about this today, but Yehuda I think is making a good case that tooling can make the process quite easy. There's quite a lot to benefit from with having only "one source of truth" for all this code! _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
