Moving to GitHub Issues

Written By Arian Stolwijk, on Monday, August 1st 2011, 7:14pm

We at the MooTools headquarters love GitHub for all its features which makes contributing and managing our code much easier than say, five years ago. GitHub is the place to be for all cool JavaScript projects which makes following your projects of interest a lot easier. When we moved to GitHub a long time ago, the ticket system was too basic to be a real solution. Fortunately this has since improved.

Especially the additions for milestones and assignees were important for us. With this in place GitHub issues can finally replace Lighthouse.

The main advantages are:

  • Everything at one place, one login
  • Easier to follow MooTools
  • Similar to pull requests

A disadvantage is that most of the current issues are in Lighthouse. Darren did an awesome job going through a lot of them but there are still some open or not fixed. A proposed option was to move all tickets to GithHub, but we decided to try to address as many as we can and just move on to GitHub.

Now every MooTools project has its issues on GitHub:

So if you know anything about any of the issues at GitHub or some old Tickets at Lighthouse, comments and fixes are highly appreciated!

2 Responses to “Moving to GitHub Issues”

  1. xandros says:

    sorry for off topic, but on several pages in the documentation there are links labeled as “tutorial/demo” that link to articles on clientcide that seem to be dead links now

    example :

    http://www.clientcide.com/wiki/cnet-libraries/01.1-class.extras/03-occlude

  2. Fábio Miranda Costa says:

    That’s great! :)