Arnaud Porterie

Sorry for the delay, I'm insanely busy with Docker 1.5.0 release. TBH I'm afraid we end up with something that becomes less about stats, and more like a control center...

Thanks for the feedback and ideas :-) I really had metrics in mind, which is why I'm not sure about making it a "control center" like I replied in #5,...

That was inside a container using the project's `Dockerfile`. There's nothing fancy in my command line: ``` docker run -d --restart=always \ -e CONSUMER_KEY=$API_KEY \ -e CONSUMER_SECRET=$API_KEY_SECRET \ -e ACCESS_TOKEN=$ACCESS_TOKEN...

Also, this would prevent the following torrent of logs: ``` time="2016-11-08T16:33:03-05:00" level=debug msg="received GitHub event" action=labeled event="pull_request" number=27745 repository="docker/docker" time="2016-11-08T16:33:03-05:00" level=info msg="running operation" operation=rebuild repository="docker/docker" time="2016-11-08T16:33:04-05:00" level=debug msg="rejecting pull request...

Until Go 1.8 is mainstream, I'd love to have a Makefile rule that builds with a `plugin` build tag to support that feature.

Just one small note: as it is configured today in Docker, `poule` will only add labels when an issue is initially opened, reopened, or edited. Unless one of those events...

This has been discussed in #8177, we're closing this for a lack of real world use cases.

Thanks for the ping! [Vossibility](https://github.com/icecrime/vossibility-stack) is a tool I created to help me manage the [:whale: Docker](https://github.com/docker) open source project. I do wish it was easier to consume or use...

Totally agree we should work on automating the release process. Also I would add: - I kind of dream of an API / web UI to manage this (click checkbox...

Agree with @thajeztah, it should remain in control of the release captain.