Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automate Github Issues #33

Open
eborden opened this issue Jun 1, 2017 · 2 comments
Open

Automate Github Issues #33

eborden opened this issue Jun 1, 2017 · 2 comments

Comments

@eborden
Copy link

eborden commented Jun 1, 2017

It seems there is a fair amount of time spent by hackage trustees flagging and filing failures in the hackage matrix. Many projects are hosted on github and this presents an opportunity for automation. Instead of expending time and political capital of individual hackage trustees in filing these issues the process could be automated.

Good:

  • Less time spent monitoring and reacting to failures.
  • More time to spend on improving and refining infra.
  • Directs less focus on individual trustees and more focus on the tool.

Bad:

  • Bots can be annoying and produce false positives.
  • Bots must either provide enough information for introspection or be complex in order to do introspection themselves.
@hvr
Copy link
Member

hvr commented Jun 2, 2017

What would you suggest an automatically submitted notification/issue could look like?

@hvr hvr added the enhancement label Jun 2, 2017
@eborden
Copy link
Author

eborden commented Jun 2, 2017

I'll put some thought in to this. I think the matrix has solid value for the ecosystem. It currently sits in this awkward phase between monitoring and CI. I think more automation would push it to be viewed more as CI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants