Self nominating to join the Website WG

[ulgens]

Hey all,

I’d like to express my interest in joining the Website Working Group.

I'm a backend developer with over 10 years of commercial experience with Django. I was trying to contribute to the free software projects long before I was able to write code. I'm trying to be more active and contributing to the Django community for several reasons:

• It's fun :)
• I enjoy the people and the collaborative nature of the community.
• Giving back to Django feels like the natural next step after all it's given me.
• I believe I can add real value to the work being done here.

I became a DSF member in December, and I’m now looking to broaden my contributions and communication within the community. I’ve already been working on projects under the WG’s umbrella, but joining the group would give me better opportunities to contribute and help others.

I have 3 sets of goals and plans:

Short-term

Improve developer experience across WG projects, lower the barrier for contributions, and ensure these projects showcase best practices in Django development and maintenance.

Towards these goals, I created these PRs so far:

• Add tblib to test dependencies djangoproject.com#1891
• Use "run --rm" instead of exec for tests in README djangoproject.com#1894
• Clean pending migrations check djangoproject.com#1902
• Clean cache settings djangoproject.com#1904
• Tidy up Docker settings djangoproject.com#1906
• Clean duplicate settings from settings/docker.py djangoproject.com#1911
• Update Django dependency to version 5.1.5 code.djangoproject.com#234
• pre-commit setup code.djangoproject.com#238
• Rename postgres database engine to stop using an alias code.djangoproject.com#243
• Apply prettier to css files code.djangoproject.com#247
• Import js config for prettier code.djangoproject.com#248

and I'd like to continue with resolving these:

• Instructions for running tox with docker don't work djangoproject.com#1817
• Do we really need tox? djangoproject.com#1890
• pyproject.toml Migration djangoproject.com#1901
• Django Running with uv Package Manager Demo djangoproject.com#1963

and help with these:

• [dashboard] Investigate and fix N+1 query issue djangoproject.com#1806
• Use distroless for a more secure and minimal Python Docker image djangoproject.com#1948

Middle term

Improve the "issues" experience. Contribute to the discussions and planning, help to find and test solid alternatives to Trac. Towards this goal, I shared my comments and proposals under https://forum.djangoproject.com/t/discuss-migrating-off-of-trac-onto-something-else/36253. I'd like to continue contributing by creating a list and comparison of the current state and viable alternatives, and documenting what sort of technical / non-technical effort is needed.

Long term

Make data from WG projects publicly accessible and analyzable. Historical patterns and trends in contributions, issues, and community engagement can teach us a lot. My first attempt at this goal was django/code.djangoproject.com#231, but it didn't really gain any clarity because of the potential off-Trac migration.

I'd like us to have something similar to https://clickpy.clickhouse.com/, as a modern alternative to https://dashboard.djangoproject.com/, and we could learn several interesting data points from it:

• Fun stats like the longest-lived issue or the fastest closed one
• Insightful analytics—e.g., which modules tend to accumulate the most issues
• Contributor and reviewer patterns, trends over time, etc.

---

I'm adding myself under "Initial members" but please let me know if it's better to update the header.