Discuss migrating off of Trac onto 'something' else

Django Internals
11

Well, there’s this thread from 2018 about widening participation, coming out of DjangoCon that year.

https://groups.google.com/g/django-developers/c/aiyE__qSHBY/m/0DErKI0gCQAJ

And it comes up every couple of turns, I’d say.

The issues I see are:

  1. The history. It’s absolutely impossible to work on Django without it. A hard criterion on any option is that we can’t loose that. And it can’t become impossible to filter/search. (This last is a problem with GitHub issues. DRF, for example, a large project that I’ve worked on at length, is much harder to find related issues on, despite probably having only a tenth or less of the history.)
  2. The freedom. It’s likely we already passed peak GitHub. I’m very sceptical of tying ourselves to a corporate solution. I know many others in our community are too.
  3. What alternative is actually better? They’re all horrific to use (or not powerful enough) as far as I can see.

Likely there are more, but those are the ones that stand out to me quickly.

@bmispelon is busy pushing the Django Trac forward. I think his opinion is likely the most valuable in terms of the risk we face.

3 Likes