On 09/02/17 09:51, Anthony Ramine wrote:
I haven't split it out yet, because I'm still hoping that the
outcome of this discussion is that I won't have to. The unified
code changes are in part 3 of
https://bugzilla.mozilla.org/show_bug.cgi?id=1336646
How does the discussion mean you don't have to split? All I see is
three patches, none of them making it obvious how the selectors API
changed. This also means that the commit messages will never ever be
written from the POV of selectors, and always from the POV of servo,
thus quite limiting any lingering hope to have external contributors
now, given it will not be as discoverable as before what is happening
in the crate at the commit level.
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.
We can't quantify the missed opportunities when merging things
together in a single repository.
I don't really have any skin in this game, but I will note that the
web-platform-tests have been much more successful since we allowed
people to use them in the same repository as their browser code, even
though it does mean we get a lot of commits with useless commit messages
like "tests". So it's not always the case that the unquantifiable
benefits of multiple repositories always outweigh the unquantifiable
benefits of a single (from the point of view of a specific group of
developers working on a larger project) repository.
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
