BlueSoybean.com - Free RSS-Based News Reader

close

The Django weblog

Latest news about Django, the Python web framework.


Source: https://www.djangoproject.com/rss/weblog/

Articles

Hitting the Home Stretch: Help Us Reach the Django Software Foundation's Year-End Goal! | Weblog | Django

Posted by Jeff Triplett on Dec. 18, 2025

via The Django weblog
Share  
Tags  

Introducing the 2026 DSF Board

Thank You to Our Outgoing Directors

We extend our gratitude to Thibaud Colas and Sarah Abderemane, who are completing their terms on the board. Their contributions shaped the foundation in meaningful ways, and the following highlights only scratch the surface of their work. Thibaud served as President in 2025 and Secretary in 2024. He was instrumental in governance improvements, the Django CNA initiative, election administration, and creating our . He also led our birthday campaign and helped with the creation of several new working groups this year. His thoughtful leadership helped the board navigate complex decisions. Sarah served as Vice President in 2025 and contributed significantly to our outreach efforts, working group coordination, and membership management. She also served as a point of contact for the Django CNA initiative alongside Thibaud. Both Thibaud and Sarah did too many things to list here. They were amazing ambassadors for the DSF, representing the board at many conferences and events. They will be deeply missed, and we are happy to have their continued membership and guidance in our many working groups. On behalf of the board, thank you both for your commitment to Django and the DSF. The community is better for your service.

Thank You to Our 2025 Officers

Thank you to Tom Carrick and Jacob Kaplan-Moss for their service as officers in 2025. Tom served as Secretary, keeping our meetings organized and our records in order. Jacob served as Treasurer, providing careful stewardship of the foundation's finances. Their dedication helped guide the DSF through another successful year.

Welcome to Our Newly Elected Directors

We welcome Priya Pahwa and Ryan Cheley to the board, and congratulate Jacob Kaplan-Moss on his re-election.

The board unanimously elected our officers for 2026:
  • President: Jeff Triplett
  • Vice President: Abigail Gbadago
  • Treasurer: Ryan Cheley
  • Secretary: Priya Pahwa
  • Jacob Kaplan-Moss
  • Paolo Melchiorre
  • Tom Carrick
I'm honored to serve as President for 2026. The DSF has important work ahead, and I'm looking forward to building on the foundation that previous boards have established. Our monthly board meeting minutes may be found at , and . If you have a great idea for the upcoming year or feel something needs our attention, please reach out to us via our page. We're always open to hearing from you.

via The Django weblog
Share  
Tags  

Django Code of Conduct Transparency Report 2025

The received 4 reports and met 12 times in 2025. This transparency report is a brief account of how those reports were handled. This year’s number is lower than previous years in part because of the formation of the which handles moderation on our official spaces and has been able to act directly on smaller scale infractions. In some cases we received additional reporting while investigating initial reports, but have not counted those as separate instances. This working group conducts business in several ways. It has online meetings, typically once per month. It also discusses issues in a Slack channel, but most cases are handled in the meetings. The group welcomed three new members this year: Ariane Djeupang, Natalia Bidart, and Priya Pahwa. Natalia was selected by the new Online Communities Working Group as their liaison to the Code of Conduct Working group; Ariane and Priya were elected by the working group. The group also saw Jay Miller step down this year. We all want to thank Jay for his continued role in our community and for all the work he did with the Code of Conduct group. It was the group’s intention to work with a consultant to update our Code of Conduct and processes. We reached out to two consultants to help with that work, but unfortunately we weren’t able to engage either to get that work completed. We hope to progress with that in 2026. In the meantime, we made a few internal process tweaks - creating up a new “ask CoC” channel with key stakeholders to discuss moderation and CoC enforcement, and having our team set up as moderators in GitHub until we find a better model. Two reports from late 2024 carried into this year. Two reports resulted in suspensions from the relevant platforms. Another was shared with local event organizers.
Finally, this section provides a brief summary of the kinds of cases that were handled:
  • One case involved repeated violations of the Discourse rules about self promotion. The working group recommended a suspension from the forum.
  • One case involved repeated behavior across several platforms that discouraged participation and created problems for others. The working group recommended a suspension from all relevant platforms and working groups.
  • One case involved an incident at a PSF-sponsored event. The information was passed on to the local organizers.

via The Django weblog
Share  
Tags  

Online Community Working Group GitHub repo and project

The Online Community Working Group has introduced a new GitHub repository designed to manage and track ideas, suggestions, and improvements across Django's various online community platforms.

Introducing the Online Community Working Group Repository

Primarily inspired by the rollout of the repository, the Online Community Working Group has launched that works in conjunction with the to provide a mechanism to gather feedback, suggestions, and ideas from across the online community and track their progression. The primary aim is to help better align Django's presence across multiple online platforms by providing:
  1. Centralisation: A community-platform-agnostic place to collect feedback, suggestions, and ideas from members of any of Django's online communities.
  2. Visibility: With a variety of platforms in use across the community, some of which require an account before their content can even be read, discussions can happen in what effectively amount to private silos. This centralised repository allows all suggestions and ideas to be viewed by everybody, regardless of their community platform of choice.
  3. Consistency: A suggestion for one platform can often be a good idea for another. Issues and ideas raised centrally can be assessed against all platforms to better align Django's online community experience.

How to use the Online Community Working Group Repo

If you have an idea or a suggestion for any of Django's online community platforms (such as the , , or elsewhere), the process starts by in the new repository. You'll be asked to summarise the idea, and answer a couple of short questions regarding which platform it applies to and the rationale behind your idea. The suggestion will be visible on the public board, and people will be able to react to the idea with emoji responses as a quick measure of support, or provide longer-form answers as comments on the issue. The Online Community Working Group will review, triage, and respond to all suggestions, before deciding whether or how they can be implemented across the community.

Existing Online Communities

Note that we're not asking that you stop using any mechanisms in place within the particular community you're a part of currently—the Discord channel is not going away, for example. However, we may ask that a suggestion or idea flagged within a particular platform be raised via this new GitHub repo instead, in order increase its visibility, apply it to multiple communities, or simply better track its resolution.

Conclusion

The Online Community Working Group was relatively recently set up, with the aim of improving the experience for members of all Django's communities online. This new repository takes a first step in that direction. Check out the repository at on GitHub to learn more and start helping shape Django's truly excellent community presence online.

via The Django weblog
Share  
Tags  

Django 6.0 released

The Django team is happy to announce the release of Django 6.0. assembles a mosaic of modern tools and thoughtful design. A few highlights are:
  • Template Partials: modularize templates using small, named fragments for cleaner, more maintainable code. (GSoC project by , mentored by )
  • Background Tasks: run code outside the HTTP request-response cycle with a built-in, flexible task framework. ()
  • Content Security Policy (CSP): easily configure and enforce browser-level security policies to protect against content injection. ()
  • Modernized Email API: compose and send emails with Python's EmailMessage class for a cleaner, Unicode-friendly interface. ()
You can get Django 6.0 from or from . The PGP key ID used for this release is Natalia Bidart: With the release of Django 6.0, Django 5.2 has reached the end of mainstream support. The final minor bug fix release, , was issued yesterday. Django 5.2 will receive security and data loss fixes until April 2028. All users are encouraged to upgrade before then to continue receiving fixes for security issues. Django 5.1 has reached the end of extended support. The final security release, , was issued on Dec. 2, 2025. All Django 5.1 users are encouraged to to a supported Django version. See the for a table of supported versions and the future release schedule.

via The Django weblog
Share  
Tags