[Django] #34576: move django issues to GitHub

11 views
Skip to first unread message

Django

unread,
May 18, 2023, 10:07:57 AM5/18/23
to django-...@googlegroups.com
#34576: move django issues to GitHub
-----------------------------------------+------------------------
Reporter: Mathieu Dupuy | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: dev
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
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.

--
Ticket URL: <https://code.djangoproject.com/ticket/34576>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
May 18, 2023, 11:19:30 AM5/18/23
to django-...@googlegroups.com
#34576: move django issues to GitHub
-------------------------------+--------------------------------------

Reporter: Mathieu Dupuy | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: dev
Severity: Normal | Resolution: invalid

Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by David Sanders):

* status: new => closed
* resolution: => invalid


Comment:

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.

--
Ticket URL: <https://code.djangoproject.com/ticket/34576#comment:1>

Django

unread,
May 18, 2023, 12:04:21 PM5/18/23
to django-...@googlegroups.com
#34576: move django issues to GitHub
-------------------------------+--------------------------------------
Reporter: Mathieu Dupuy | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: dev
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------

Comment (by Mariusz Felisiak):

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

--
Ticket URL: <https://code.djangoproject.com/ticket/34576#comment:2>

Django

unread,
May 18, 2023, 12:54:24 PM5/18/23
to django-...@googlegroups.com
#34576: move django issues to GitHub
-------------------------------+--------------------------------------
Reporter: Mathieu Dupuy | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: dev
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------

Comment (by Natalia Bidart):

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

--
Ticket URL: <https://code.djangoproject.com/ticket/34576#comment:3>

Django

unread,
May 18, 2023, 1:17:42 PM5/18/23
to django-...@googlegroups.com
#34576: move django issues to GitHub
-------------------------------+--------------------------------------
Reporter: Mathieu Dupuy | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: dev
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------

Comment (by Mariusz Felisiak):

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

--
Ticket URL: <https://code.djangoproject.com/ticket/34576#comment:4>

Reply all
Reply to author
Forward
0 new messages