id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
34576	move django issues to GitHub	Mathieu Dupuy	nobody	"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 [https://peps.python.org/pep-0581/ 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.

"	Uncategorized	closed	Uncategorized	dev	Normal	invalid			Unreviewed	0	0	0	0	0	0