We can do a subtree mirror from a subdirectory of a git repo into another git repo. Here's an example: https://chromium.googlesource.com/chromium/src/build
Would that suffice? Pushing it to github too would also be easy.
Rob
--
You received this message because you are subscribed to the Google Groups "infra-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to infra-dev+...@chromium.org.
To post to this group, send email to infr...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/infra-dev/CABc02_JbpMnx6JB_xbjuAjKes%3DcaFjJqK8rKDifWgFdwr%3DANiQ%40mail.gmail.com.
>> This effort is, of course, coordinated with the Developer Tools team as well as Paul Irish.
As a DevTools lead, I don't think this is quite the case. It is the first time I hear we decided to do something on this front.
What is your plan here? This is not the first time it is brought up, but there are certain challenges on the way that prevented us from investing into it earlier. Namely, the review / contribution process execution with associated policy requirements and testing infrastructure that needs to run against the debugging backend.
Lets hold it off until discussed with the eng team.
Regards
Pavel
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/CABc02_JSsDDYKW64LjrJ2K018BwV3q7fSfok_Qr0mdMd89%3DUnA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/CAEX3KhYV1EYAfkyVjv_%2BK%2BfWgEb0ghDv1uqdHUj48wHBaPjPLA%40mail.gmail.com.
No, it is clearly a bad idea. I don't see how it addresses the layout test issue, nor does it address review process challenges that we've faced with external contributors that start off github. So lets not fork the dev process like this.
We should instead steer the front-end itself towards a more open contribution model where it can be considered a standalone project with reasonable standalone testing harness and a way to test against runtime (i.e. no layout tests). So instead of forking and not testing, we should start with what we have and refactor it. That's however something we don't have free cycles for atm.
Anyhow, lets move this discussion back to the thread you pointed to.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/CABc02_KGXzOH2ZrqQ7PHp-RWa28_hE8zLv69u4xTJ%3DffzSW-PQ%40mail.gmail.com.