https://code.djangoproject.com/ticket/35829 - Update/Fix Font Awesome icons (Needs license expertise, I have reached out to the board for advice, accepted based on follow ups.)
https://code.djangoproject.com/ticket/35828 - Switch to statically declaring version number in pyproject.toml (Waiting for more forum feedback, I engaged in conversations, closed as wontfix for now given the lack of clear consensus.)
https://code.djangoproject.com/ticket/35757 - memcached.PyMemcacheCache reentrancy problem with ASGI-based runserver (A few rounds of coming and going, I followed up with Carlton and he closed it as needsinfo.)
Initial chat with @andrewgodwin regarding The Fellowship (of the ) and ongoing pain points. The meeting goal was to establish a shared and clear understanding of the current issues, then iterate on them to find improvements and solutions. Looking forward to more of these discussions!
Catch up on security issues:
Sync with Sarah specifically on this topic.
Replies to pending reports.
Started conversation with the DSF Board about potentially becoming a CNA (CVE Numbering Authority, for example Python is a CNA already).
https://code.djangoproject.com/ticket/35851 - django.test.client.ClientMixin._login doest not set enviorn like REMOTE_ADDR can cause test failures in certain situations (wontfix)
https://code.djangoproject.com/ticket/35862 - invalid token in plural form: EXPRESSION on django/contrib/auth/locale/ru_RU and some other ru_RU file when running manage.py compilemessages -l ru_RU command (invalid)
https://code.djangoproject.com/ticket/35866 - Django documentaion style guide on models is unclear what to do with any other Python dunder methods that the model class might have (accpted)
It’s been a busy week getting back up to speed after the holidays, with a lot of meetings and a considerable amount of information to process. I also found the recent news (recent to me at least) about the Steering Council drama a bit unsettling, but I’m glad to see that the DSF Board and other community members have been actively working on mitigation actions. Thank you!
Triaged
https://code.djangoproject.com/ticket/35901 - settings.DEBUG could reject non-empty string values (or in particular “off”, “no”, “0”, “disabled”, “false”, “False”) (wontfix)
https://code.djangoproject.com/ticket/35927 - utils/encoding.py force_string, smart_string, force_bytes, and smart_bytes should verify encoding parameter is not None (invalid)
Short week for me since I wasn’t feeling great when it started, and my ability to stay up was lost by Thursday . I’m at 60% today, which is like 12 times better than last week!
Deep dive on this new feature, with the goal of finalizing it and have it ready to be merged before Django Feature Freeze (Jan 15th).
I found some issues that IMHO needs further community discussion so I resurfaced Salvo’s thread in this comment. If you are a Django shell user and care about the default auto import experience, PLEASE comment!
I have a local working branch that splits the work in the original PR in two, one without the “models modules alias auto import” and a follow up commit that adds it. Will push to Salvo’s PR soon for better review and understanding.
Authored
https://github.com/nessita/django/pull/18 - Fixed #35667 – Improved deprecation warning handling by replacing stacklevel with skip_file_prefixes. (study of a potential better approach)
Other/Misc
Reviewed security reports.
Prepared and sent hours invoice and monthly report.
I’m still recovering from last week’s illness (frustratingly still undiagnosed), though progress has been slow. My brain feels foggy, and my body still aches. Hopefully, I’ll feel better by next (this) week!
Finally I started feeling better health-wise, so we travelled to Argentina to visit family. Therefore, I’ll be taking Mon-Wed off the week of the 23th and also Mon-Wed the week of the 30th. I will try to at least catch up with security reports and ticket triaging, unsure if I’ll be able to do any PR reviews… Will try though!