> We strongly feel that the code and issue tracker need to live in the same location to make it easier to manage and give people one location to visit for all o

> We strongly feel that the code and issue tracker need to live in the same location to make it easier to manage and give people one location to visit for all of their ESLint-related needs... For sake of interest I feel compelled to mention that fossil[0] does have a fully-integrated ticket system[1] (and more[2][3]) that allows code to reference tickets, and tickets reference code. These tickets and full history are first-class artifacts that are part of the repository, so are carried from copy to copy, and updates are transmitted as part of synchronizing repos. Of course there is more to project management than just tickets, but as a happy fossil user for many years, I do really appreciate the integrated ticket management. [0] http://www.fossil-scm.org http://www.fossil-scm.org [1] http://fossil-scm.org/index.html/doc/trunk/www/bugtheory.wiki http://fossil-scm.org/index.html/doc/trunk/www/bugtheory.wik... [2] http://fossil-scm.org/index.html/doc/trunk/www/wikitheory.wiki http://fossil-scm.org/index.html/doc/trunk/www/wikitheory.wi... [3] http://fossil-scm.org/index.html/doc/trunk/www/event.wiki http://fossil-scm.org/index.html/doc/trunk/www/event.wiki