Week ending 2023-11-05 (Week 44)
Triaged
- https://code.djangoproject.com/ticket/34694 - trailing slash is not appending (worksforme)
- https://code.djangoproject.com/ticket/34940 - Filter queryset on “tuples” of values for multiple columns (duplicate)
- https://code.djangoproject.com/ticket/34941 - db_default with decimal.Decimal() doesn’t return Decimal instances on Oracle. (accepted)
Reviewed
- https://github.com/django/django/pull/17388 - Fixed #34909 – Added aria-describedby to Admin Add/Change buttons
- https://github.com/django/django/pull/11783 - Resolved #30032 – Added support for query expressions as default values
- I ended up in this PR after reading on ticket 32577
- I pushed a rebase, plus conflict and style fixes, and pinged the author
- https://github.com/django/django/pull/17227 - Fixed #34813 – Doc’d how calculation of the integrity HTML attr needs to occur after collectstatic.
- https://github.com/django/django/pull/17220 - Fixed #34806 – Made the cached_db backend resilient to cache backend errors.
- https://github.com/django/django/pull/17417 - Fixed #34925 – Fixed Model.refresh_from_db() skipping items in fields param.
- https://github.com/django/django/pull/17416 - Fixed #16429 – Provided refresh option for FilePathField path choices.
- After a round of reviews, I realized that the understanding of what “automatically refresh choices” mean may differ from what others understand, so if you are interested in this work, I’d suggest reading my latest comments in the PR and sharing your view.
Authored
- https://github.com/django/django/pull/17429 - Refs #30601 – Fixed typos in docs/topics/db/transactions.txt.
- https://github.com/django/django/pull/17428 - Refs #15578 – Made cosmetic edits to fixtures docs.
Other/Misc
- Continuing on the consensus topic, I read Jacob’s suggestion Consensus Decision Making - Seeds for Change:
- I think our consensus model definitely needs improvement as I posted last week in the forum but, from the article, we may not be “that far” from having a functional model. For example, we already have an agreement schema that maps nicely to the one in the article:
- “Agree” would be our +1
- “Agree with reservations” → +0
- “Stand aside” → -0
- “Block” → -1
- The article also describes how the Block should be used wisely and strategically, proposing a few tools to allow “unfolding” that Block into processes that lead to an eventual consensus. I think adapting something along these lines could be key for us.
- Lastly, I think we could use all/some of the suggested conditions for consensus, to build and document our own consensus process. Specifically, I think we already have trust and are open with each other, but I would appreciate a more clear/documented “common goal” and a more explicit “Commitment to consensus”.
- I think our consensus model definitely needs improvement as I posted last week in the forum but, from the article, we may not be “that far” from having a functional model. For example, we already have an agreement schema that maps nicely to the one in the article:
- Following conversation in the forum about the User model, I watched this DjangoCon AU talk and did some readings on the links shared by Lily. I learnt a lot, thanks!
- Investigated former tickets and PRs related to ticket 34457
- Read Why is the Django Admin “Ugly”? - CodeRed