> In general, I posit that Mozilla completely, utterly, lost against V8 in the > embedded department in a huge part because of this mono-repository thing > where everything is muddled together.
I don't think anyone is disagreeing with you on this point. The plan is as it always has been - to split out anything sensible to its own repo and publish to crates.io. The key traits of rust-selectors leading to this exception are that it was split out for 2 years with little community involvement in development (but a reasonable amount of usage) and (we hope temporary) high synchronization burden for the active developers. We should continue to split out things as the default, since we have no way to know which things will spawn healthy communities a priori. This is being proposed as an exception to our policy given some unique circumstances. > As Simon says in his own reply, no we never block people because they did a > breaking change that requires action on Servo's side. That's the main reason > why things are split IMO. Servo shouldn't be a special burden for unrelated > contributors. You are correct to point out that this will change for rust-selectors when it is in-tree. The practical consequence based on current data is basically zero, since all active developers are working with the must-be-in-sync-with-servo-and-gecko rule already. jack. _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
