move django issues to GitHub

[Mathieu Dupuy]

It must have been already been discussed but I could not find it with a trac research on the summary with "github".

Trac is a software that is really showing its age. It is now almost 20 years old now and you can tell from the UI because it did not really change in the meanwhile. It was a good solution in the ~2000 but now I can't think of any significant open-source project that is still using it. It is showing its age and the user experience significantly drifted from what is the norm today. Trac' usability is really poor, it does not use markdown, and Django's Trac is super slow (an average of 5 actions for any action as of today).

Ruby on Rails and CPython already moved to GitHub, and we should do the same. The reasoning of moving to GitHub for CPython is detailed in the ​PEP 0581. Despite a significant resistance in the CPython project, that is rather conservative, they did the move anyway, and they seem pretty satisfied. Contribution skyrocketted after the move.

If CPython deemed it superior and managed to do it, we can and should do it.

[David Sanders]

I was thinking the same thing just the other day, but this is a discussion that needs to be had with the community. There are pros & cons for moving to GitHub.

(also trac is for issues with Django itself and issues with the ticketing falls under djangoproject.com)

Start a thread! I'll be keen to see what folks say.

[Mariusz Felisiak]

This was discussed multiple times. I'm strongly against it.

[Natalia Bidart]

Yes please, let's start a thread in the forum since I also think the pros outweigh the cons.

[Mariusz Felisiak]

There is plenty of disadvantages and only one advantage i.e. folks will not have to switch to Trac from GitHub.