Hi David. First off, well done for getting your first PR merged today! ๐
Then, thanks for raising this; it's worth talking about at least. I too would like to bring the ticket count down, but I would like to do it by fixing them. ๐ I think there are two approaches here. Certainly on DRF, Tom Christie implemented an approach of closing tickets that weren't really active. He's got an old post on that: https://www.dabapps.com/blog/sustainable-open-source-management/ I've followed similar on Django-Filter, say. Historically, that's not what we've gone for on Django. Rather, we've seen no harm in keeping valid tickets open. (The filters you link to already let you cut down the number of tickets you see, if that's the goal.) For **many** of the tickets, they're not necessarily super hard, they just need time and love. So new contributions like yours are the secret. It may be a harder job to get the number down this way, but I'm optimistic we can do it. Plus Mariusz and I very much enjoy merging fixes to really old tickets. It's somewhat satisfying. (I don't guess anyone else notices, but... ๐) I hope that makes sense. And thanks for your super contributions this week. Welcome aboard! ๐ Kind Regards, Carlton On Thursday, 26 September 2019 16:45:52 UTC-7, David Vaz wrote: > > Hi, > > I am playing around at the DjangoCon US 2019 Sprints and while trying to > do my share one thing stands out in the open tickets is: Some are very old > and others have not been touched in a while. > > I did a simple analysis of accepted and open tickets based on last > modified time (kind of a live status). > > The numbers might change over time, but I also linked them: > > Modified at any time All > <https://code.djangoproject.com/query?status=assigned&status=new&changetime=09%2F26%2F2015..09%2F26%2F2019&stage=Accepted>: > > 1264 > > Modified in last 5 years > <https://code.djangoproject.com/query?status=assigned&status=new&changetime=09%2F26%2F2014..09%2F26%2F2019&stage=Accepted>: > > 1039 > > Modified in last 4 years: > <https://code.djangoproject.com/query?status=assigned&status=new&changetime=09%2F26%2F2015..09%2F26%2F2019&stage=Accepted> > > 887 > > Modified in last 3 years > <https://code.djangoproject.com/query?status=assigned&status=new&changetime=09%2F26%2F2016..09%2F26%2F2019&stage=Accepted>: > > 728 > > Modified in last 2 years > <https://code.djangoproject.com/query?status=assigned&status=new&changetime=09%2F26%2F2017..09%2F26%2F2019&stage=Accepted>: > > 494 > > Modified in last year > <https://code.djangoproject.com/query?status=assigned&status=new&changetime=09%2F26%2F2018..09%2F26%2F2019&stage=Accepted>: > > 329 > > > So if we would decide to close stalled tickets after some inactivity > period we could massively reduce the opened tickets list. Imagine if we > close any ticket no modified in the last 5 years we would reduce by 20% the > active ticket list. If we decide to be more aggressive, say 3 years we can > cut by half the active tickets list. > > > I also believe that apparently stalled tickets might be important. This > auto-close approach would also trigger *a live prof, *any automatically > closed ticket could be reopened if relevant. > > > Let us focus the efforts on the really active ones. > > > Anyway, these are just my thoughts. > > > For those of you who do not know me, I am organizing DjangoCon Europe 2020 > in Porto Portugal and you are all invited, official details are about to be > released. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/e3b9ab45-2ab8-49f0-a531-919cbf7334f9%40googlegroups.com.
