On Sat, 6 Feb 2016 at 23:21 Nick Coghlan email@example.com wrote:
I was at linux.conf.au 2016 last week, and one of the presentations was from Mozilla's Emily Dunham on some of the infrastructure automation they use with Rust and other GitHub based projects: https://www.youtube.com/watch?v=dIageYT0Vgg
I finally had the time to watch the video. It's very interesting and basically mirrors what I'm hoping is going to be possible for us once we migrate to GitHub (i.e., automate as much as we can). While it doesn't change any of the plans for reaching parity support to the hg workflow, it is something to revisit when it comes time to look at adding new features to our workflow (and maybe even share the bots if it happens to make sense).
In addition to their merge bot project homu (which we've talked about previously), they also have:
The first project looks for folks submitting their first PR or issue, and responds with some standard info to save humans from having to do it later (like pointers to the Code of Conduct and the Contributor Licensing Agreement, as well as explanations of how the contribution process works)
The second one is designed to provide a better answer to the "How do I get started?" question by making it easy for developers to tag simpler issues. This could presumably also be used to provide separate views based on what folks want to work on (e.g. documentation, Python code, C code)
While these wouldn't necessarily be something we wanted to set up immediately, it likely makes a lot of sense to try to share the tool maintenance load with Mozilla rather than going for a completely custom setup.
-- Nick Coghlan | firstname.lastname@example.org | Brisbane, Australia _______________________________________________ core-workflow mailing list email@example.com https://mail.python.org/mailman/listinfo/core-workflow This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct