Could we do the same thing for rust-selectors? And should we? On Thu, Feb 9, 2017 at 9:27 AM James Graham <ja...@hoppipolla.co.uk> wrote:
> On 09/02/17 16:18, Michael Howell wrote: > > WPT still has its own repo; the Servo repo just does an occasional > > bidirectional sync. The equivalent for rust-selectors would be if the > > rust-selectors repo was kept and just occasionally synced with Servo > (like > > Servo is doing for M-C, anyway). > > Sure, but my point was that making the workflow for regular contributors > as painless as possible (by allowing them to work in a "monorepo" setup) > vastly increased the number of contributions we got and was a huge win > for the project. Of course the specifics of wpt demand a complex 2 way > sync architecture to support that, since there are multiple downstream > projects using the tests. > > _______________________________________________ > dev-servo mailing list > dev-servo@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-servo > _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
