https://django-commons.org/categories/meeting-notes/Recent content in Meeting Notes on Django CommonsHugoen-USDjango CommonsWed, 16 Sep 2026 00:00:00 +0000https://django-commons.org/blog/posts/2026-09-16-admins-meeting/Wed, 16 Sep 2026 00:00:00 +0000https://django-commons.org/blog/posts/2026-09-16-admins-meeting/<h2 id="actions">Actions</h2> <ul> <li>Brian: Add to Best Practices suggested guidelines for releasing support for updated versions of Django / Python (Brian)</li> <li>Brian: Look into ReadTheDocs domain hijacking for packages that don’t use RTD.</li> <li>Daksh: Update media page with Daksh’s lightning talk from EuroPython</li> <li><del>Daksh to create a meeting poll for an open issues discussion</del></li> <li><del>Tim: Review Storm post draft</del> <ul> <li><a href="https://github.com/django-commons/membership/pull/562">https://github.com/django-commons/membership/pull/562</a></li> </ul> </li> <li><del>Tim: Follow up with Daniel, Tilda, Brian on public notes</del></li> <li>Tim: Draft public notes LLM action and initial</li> <li>All: Review <a href="https://github.com/django-commons/controls/issues">the open issues</a>, see if anything should be closed or if there’s something of interest to you</li> <li>[TBD]: Explore limited control for DNS records with django unicorn</li> <li>[TBD]: Draft initial public notes and action</li> <li>[TBD]: Draft message for the community around policy changes</li> </ul> <h2 id="agenda">Agenda</h2> <ul> <li>Storm stepping down <ul> <li>Storm has a new full-time job that is taking up the previous OSS time</li> <li>Review <a href="https://github.com/django-commons/membership/commit/9325c7d0fc3a44c95808cacf8d5a2f5ceff09b3d">Storm Post Draft</a></li> <li>DNS <ul> <li><a href="http://desec.io">desec.io</a> - confirmed working</li> </ul> </li> <li>Is planning for the end of the month Sep 30th.</li> </ul> </li> <li>Revise contribution guidance controls PR: <ul> <li><a href="https://github.com/django-commons/controls/pull/99">https://github.com/django-commons/controls/pull/99</a></li> <li>On adding PyPI metadata for description on meaningful metrics <ul> <li>Tim: suggestion to remove basing it on the meaningful metrics</li> <li>Storm: Concern with adding it to PyPI because releases don’t get cut often <ul> <li>Tim: The changes don’t necessarily need to fit into the existing release flow</li> <li>There would be an issue going from active to dormant, there could be changes that haven’t been released. We would need to decide if those get released or not.</li> </ul> </li> <li>Badges on PyPI could have the images updated <ul> <li>How does caching work with this? <ul> <li>Would need to see what the cache level is</li> <li>What would be the impact of this</li> </ul> </li> <li>Is changing the underlying files worth the work</li> </ul> </li> </ul> </li> <li>Daksh: Would a maintainer be opposed to including a badge in the README <ul> <li>Not sure, we haven’t tried doing this before.</li> <li>We should have consistency in our projects on badges and README notice about Django Commons</li> <li>Communication plan <ul> <li>Draft a message for the maintainers on what we want to change around readme, badges, pypi</li> <li>Update the best-practices repo</li> <li>Create PRs and make it optional</li> </ul> </li> </ul> </li> </ul> </li> <li>Tim: Public notes <ul> <li>DSF Board has public and private comments, along with confidential information that they are hidden.</li> <li>Storm/Ryan: Could publish public meeting notes as blog posts on the site, then share in other places</li> <li>The four of us are in agreement, not quite sure on where it should go</li> <li>Tim: I would like it if we have notes published in the forum so that the whole community can find things in the same place</li> <li>Storm: I’d prefer a markdown file in a repo to follow-along</li> <li>Proposed Logistics <ul> <li>Do the meeting minutes in the docs website</li> <li>Use an LLM action to convert from google to markdown</li> <li>Publish to the site</li> <li>Share on the forum</li> </ul> </li> </ul> </li> <li>Tim: Review controls repo open issues: <a href="https://github.com/django-commons/controls/issues">https://github.com/django-commons/controls/issues</a> <ul> <li>Ryan: We can try to review these before next month’s meeting and do some triaging and/or discuss</li> </ul> </li> </ul>