On Sun, 7 Feb 2016 at 02:23 Maciej Szulik <solt...@gmail.com> wrote: > On Sun, Feb 7, 2016 at 10:14 AM, Berker Peksağ <berker.pek...@gmail.com> > wrote: > > On Sun, Feb 7, 2016 at 9:21 AM, Nick Coghlan <ncogh...@gmail.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 just watched it, great talk. Thanks for sharing! > > > >> In addition to their merge bot project homu (which we've talked about > >> previously), they also have: > >> > >> highfive (a greeter bot): https://github.com/nrc/highfive
The greeter bit could be rolled into https://github.com/brettcannon/knights-who-say-ni since it has to watch for newly opened pull requests for the CLA check anyway. > > > > > This is a good idea. > > > >> starters (an issue curator): https://starters.servo.org/ > >> > >> 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. > > > > The biggest problem of these tools is that they don't provide an API > > or a framework to use as a base. They have a lot of project specific > > code and they don't work on Python 3. So you'll need to write your own > > code anyway. We are going to write a lot of bots in the next months so > > I think we will eventually create some sort of framework to share some > > code. > > Talking from the position of owning a similar bot in OpenShift, I quite > certain that it's really hard to have common base. Since these bots > address specific project and there are not two exactly the same projects > with exactly the same workflow. I think what Nick meant to show is, > what we should target, more or less at least. > Having started writing the CLA bot, I can attest that it's tough to abstract it all in a way that's easy to swap out the parts. I am trying to do my best, though, so that when it comes to swap out either the server host, contribution host, or CLA records host it won't be a complete rewrite. -Brett > > > > Coordinating with Mozilla (or any other organization) requires a big > > amount of time, and I simply don't have enough time and motivation > > right now. However, I'm planning to send an email to the > > django-developers list [1] when I finish to document my bot. I have a > > test organization at https://github.com/fayton. See also > > https://github.com/fayton/cpython/pull/1 for an example pull request > > (the name of the bot is just a placeholder, Brett will give it a name > > :)) > > > > --Berker > > > > [1] They might be interested since we (will) have almost identical > > workflow with them (they also have multiple maintenance branches for > > example) > > _______________________________________________ > > core-workflow mailing list > > core-workflow@python.org > > https://mail.python.org/mailman/listinfo/core-workflow > > This list is governed by the PSF Code of Conduct: > https://www.python.org/psf/codeofconduct > > Maciej > _______________________________________________ > core-workflow mailing list > core-workflow@python.org > https://mail.python.org/mailman/listinfo/core-workflow > This list is governed by the PSF Code of Conduct: > https://www.python.org/psf/codeofconduct
_______________________________________________ core-workflow mailing list core-workflow@python.org https://mail.python.org/mailman/listinfo/core-workflow This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
