3 ms·
I'm extremely skeptical of any "just use platform/service/tool X" type of suggestion, largely because I've been doing this long enough to know that "just" needs
by ubernostrum 8y ago
I'm extremely skeptical of any "just use platform/service/tool X" type of suggestion, largely because I've been doing this long enough to know that "just" needs to be in scare quotes and that often the claimed benefits don't materialize.
Django does need a place to store the tickets, and GitHub's tracker... is not great. I'd honestly want to look at adding OAuth or other easier signup/account management to Trac before I'd look at moving to GitHub issues.
- btown 8y agoA fair and valid point, and to Django's credit, they actually do have Github OAuth as the signin procedure for Trac! Unfortunately, it's still a new interface for people to learn and be afraid of - and most importantly, it's a place where activity can be hidden from people who are just browsing the codebase, so the project looks less active than it actually is! Bots that mirror content/comments between the various platforms might be an interesting interim step that could minimize those scare quotes, and achieve many of the benefits in a minimally invasive way.
- jsmeaton 8y agoEvery year or so someone brings up the prospect of moving from Trac to something else (mostly github recently). October was the last time this was brought up[0]. I'm of the opinion that Trac is probably blocking a number of people from contributing, even if that contribution is participating in comments and voting on issues. But that's exactly the kind of thing the community as a whole can be empowered to do without the old guard of core vetoing the suggestion outright. The python community are considering doing just that now with PEP 581. [0]https://groups.google.com/forum/#!topic/django-developers/aiyE__qSHBY https://groups.google.com/forum/#!topic/django-developers/ai... [1]https://www.python.org/dev/peps/pep-0581/ https://www.python.org/dev/peps/pep-0581/