On Sun, Feb 7, 2016 at 10:14 AM, Berker Peksağ firstname.lastname@example.org wrote:
On Sun, Feb 7, 2016 at 9:21 AM, 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 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
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.
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  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 :))
 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 firstname.lastname@example.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