Re: Django's issue tracker uses timezone CDT

2021-08-10 Thread Jacob Rief
On Monday, August 9, 2021 at 12:10:51 PM UTC+2 Adam Johnson wrote: > I'd be +1 on moving the default to UTC. > > Or we could change Trac to pick up the browser's timezone offset and > display datetimes accordingly. > The latter world be the cleanest solution. I'm not familiar with Trac's

Re: Django's issue tracker uses timezone CDT

2021-08-09 Thread 'Adam Johnson' via Django developers (Contributions to Django itself)
I'd be +1 on moving the default to UTC. Or we could change Trac to pick up the browser's timezone offset and display datetimes accordingly. On Fri, 6 Aug 2021 at 15:28, Tom Carrick wrote: > While moving the default to UTC is probably a good idea - you can change > this for yourself in

Re: Django's issue tracker uses timezone CDT

2021-08-06 Thread Tom Carrick
While moving the default to UTC is probably a good idea - you can change this for yourself in Preferences -> Localization. Tom On Fri, 6 Aug 2021 at 16:22, Jacob Rief wrote: > This presumably is a legacy from the days when Adrian Holovaty and > Jacob Kaplan-Moss started the Django project in

Django's issue tracker uses timezone CDT

2021-08-06 Thread Jacob Rief
This presumably is a legacy from the days when Adrian Holovaty and Jacob Kaplan-Moss started the Django project in Kansas City. The Django issue tracker uses the timezone CDT which is correct for central Americas, but since Django became a world wide project, in my opinion this should either be