Monday, May 20, 2013

Spring Cleaning for GitHub

Spring is almost over, but it's not too late for us to do a bit of cleaning in our GitHub home.

We've been working hard on clearing our pull request queue.  We believe we're a few weeks away from being at a sustaining pace where all PRs get resolved in a week or so.  Hurrah!

Issues, however, are a different story.  There are 650+ issues with 5 to 10 arriving each day.  We've failed in all attempts in our imagination to think of a way to get on top of them.  Additionally, we believe that the majority of these issues are already addressed by PRs or are no longer valid for other reasons.

For this reason, we'll be declaring bankruptcy on the majority of these issues.  Next week, we'll be running a script to automatically:
  • Close issues older than 15 days that have no linked pull request.
  • Send an email to the issue reporter with an option to reopen if it is still an issue.
We've staffed up our attention on the issues queue and plan a similar turnaround time on all issues to move each of them to their next stage within a week or less.

Thanks for your continued help in making Angular great and we hope you enjoy the new clean house!

14 comments:

  1. I hope this project is paid somehow by Google and you can afford to hire few good programmers.

    ReplyDelete
  2. Hopefully this will be the reset you need, because as far as I can see the momentum is just going to increase. There's a lot of traction out there (a good problem to have, of course, but still a problem if you've gotten to this point once already.)

    ReplyDelete
  3. Great news! This is one of the perceived issues with Angular compared to other frameworks—the amount of unresolved issues.

    ReplyDelete
  4. Awesome. Thanks for the heads-up!

    ReplyDelete
  5. In the future could we require all bugs to come with example code (e.g. jsFiddle) before being allowed as an official issue?

    ReplyDelete
    Replies
    1. Or Plunk! ;-)

      Sounds like a great approach to getting all those issues back under control.

      I notice that may PR's have identifiers in brackets. Perhaps this could be documented in the CONTRIBUTING.md file.

      Delete
    2. Great idea! So much easier to track down an issue with a jsFiddle or Plunk available. Plus, by doing that people are forced to think through the issue more thoroughly and create a simple repo.

      Delete
  6. I agree with purge. Hopefully you can get an intern or two for issue triage going forward?

    ReplyDelete
  7. Have you all considered a bot to act as a first line of defense on issues? https://github.com/cldwalker/gh-active-issues is how I deal with my issues. Mine is tailored to my needs but you could do something similar that automates away vague issues

    ReplyDelete
  8. All you're doing is preventing people from telling you what's wrong.

    This won't fix anything; it will instead make the existing problem worse. You'll still have more bugs than you can get on top of; you just also won't know what they are.

    This is a terrible idea.

    ReplyDelete
  9. This sounds like it could work. Mostly if those old issues have already been resolved. I would be surprised if you are not already trying to add more people to your team. Good luck!!!

    Arturo Hernandez

    ReplyDelete
  10. John is perfectly right. The fact that a reporter is not skilled enough to write a precise report does not at all mean that he is not pointing at an important issue.

    ReplyDelete
  11. We really need big guys like Google, Amazon, IBM, Oracle to adopt this kind of projects and help them on funding front. Open source community really need backing from some one like Google, which has boundless resources.


    Thanks
    Rohit

    ReplyDelete

Note: Only a member of this blog may post a comment.