Official conference news 2026-06-19T16:02:10Z https://2026.djangocon.us DjangoCon US Team hello@djangocon.us 2026-06-19T06:00:00Z https://2026.djangocon.us/news/code-of-conduct/ <h1 id="djangocon-us-2026%3A-creating-a-safe-and-inclusive-community" tabindex="-1">DjangoCon US 2026: Creating a Safe and Inclusive Community</h1> <p>As we gear up for another exciting DjangoCon US in Chicago this year, we want to take a moment to highlight one of the most important aspects of our conference: our <strong>Code of Conduct</strong>. At DjangoCon US, we believe that fostering a respectful, inclusive environment is essential to creating a valuable experience for everyone.</p> <h2 id="our-commitment-to-you" tabindex="-1">Our Commitment to You</h2> <p>The <strong>DjangoCon US 2026 Code of Conduct</strong> serves as the foundation for how we interact with one another, both during the conference and in related online spaces. It's designed with one goal in mind: ensuring that every participant feels welcome, respected, and safe.</p> <h2 id="what-we-expect" tabindex="-1">What We Expect</h2> <p>Our community values <strong>professional behavior, courtesy, and respect</strong> among all attendees. This applies whether you're attending talks, participating in sprints, networking at social events, or engaging in conference-related online discussions.</p> <p>Specifically, our code prohibits:</p> <ul> <li><strong>Harassment</strong> in any form</li> <li><strong>Offensive language or jokes</strong></li> <li><strong>Unwelcome attention or advances</strong></li> </ul> <p>We also ask that attendees be mindful about photography and recording - <strong>always obtain permission</strong> before capturing someone's image or voice.</p> <h2 id="reporting-concerns" tabindex="-1">Reporting Concerns</h2> <p>If you experience or witness behavior that violates our Code of Conduct, we want to know about it. You can report incidents by emailing <strong><a href="mailto:conduct@djangocon.us">conduct@djangocon.us</a></strong> with detailed information about what occurred. Our team takes these reports seriously and will respond appropriately.</p> <p>The conference organizers reserve the right to take action against anyone who violates these standards, which may include expulsion from the conference without a refund.</p> <h2 id="a-note-on-safety" tabindex="-1">A Note on Safety</h2> <p>For everyone's safety and peace of mind, <strong>weapons are not permitted</strong> at DjangoCon US events.</p> <h2 id="building-on-strong-foundations" tabindex="-1">Building on Strong Foundations</h2> <p>Our Code of Conduct was adapted from the Geek Feminism wiki and PyCon's Code of Conduct, reflecting best practices developed across the tech community.</p> <h2 id="join-us-in-creating-something-special" tabindex="-1">Join Us in Creating Something Special</h2> <p>DjangoCon US isn't just about technology—it's about people coming together to learn, share, and grow. By adhering to our Code of Conduct, you're helping us create an environment where everyone can participate fully and comfortably.</p> <p>We're looking forward to welcoming you to Chicago for DjangoCon US 2026, where we'll celebrate not just Django, but the diverse, respectful community that makes it special.</p> <p><em>For complete details, please review our full <a href="https://2026.djangocon.us/conduct/">Code of Conduct</a> before attending the conference.</em></p> 2026-06-12T16:00:00Z https://2026.djangocon.us/news/international-travel/ <p>Are you attending DjangoCon US 2026 in Chicago, Illinois, but you are not from US and need some travel information? Here are some things to consider when planning your trip.</p> <ul> <li> <p><strong>Visa Invitation Letter</strong>: If you need a visa invitation letter, please use our <a href="https://2026.djangocon.us/invitation/">visa letter form</a> to request one.</p> </li> <li> <p><strong>Visa</strong>: Check the <a href="https://travel.state.gov/content/visas/en.html">State Department's website</a> for information about US visas, and review the <a href="https://travel.state.gov/content/travel/en/us-visas/visa-information-resources/global-visa-wait-times.html">estimated visa appointment wait times</a> when planning your travel. You may be eligible for a visa waiver program (which is an online form—no embassy visit required) or you may need to apply for a visa at the <a href="https://www.usembassy.gov/">US embassy or consulate</a> in your country or a neighboring country.</p> </li> <li> <p><strong>Valid Passport</strong>: Many travelers are recommended to have a passport that remains valid for at least six months after their intended departure from the United States. Requirements vary by nationality and country specific agreements, so check with your local embassy or consulate for the most up to date information.</p> </li> <li> <p><strong>Accommodation</strong>: If you are staying in the conference hotel, <a href="https://www.ihg.com/redirect?path=asearch&amp;brandCode=vx&amp;localeCode=en&amp;regionCode=1&amp;hotelCode=CHIWP&amp;checkInDate=23&amp;checkInMonthYear=072026&amp;checkOutDate=29&amp;checkOutMonthYear=072026&amp;rateCode=6CBARC&amp;_PMID=99801505&amp;GPC=DJ6&amp;cn=no&amp;adjustMonth=false&amp;showApp=true&amp;monthIndex=00">book your room here</a>. Our conference rate expires on Aug. 3, 2026.</p> </li> <li> <p><strong>Money Conversion</strong>: Most places in the US will take major credit cards, such as Visa and Mastercard. You can withdraw local currency from your bank account using an ATM if you need cash while you are in the United States.</p> </li> <li> <p><strong>Travel Paperwork</strong>: It is a good idea to bring as much evidence as possible to show <strong>the reason</strong> of your visit to the US, <strong>where</strong> is the conference going to take place, <strong>when</strong> are you going to go back to your home country and <strong>what</strong> you do in your home country. Please bring this paperwork with you. These documents can be helpful when going through US Customs and Border Protection:</p> <ul> <li>Printout of your invitation letter.</li> <li>Printout of conference ticket.</li> <li>Lodging reservation confirmation.</li> <li>Flight reservation, especially the return date.</li> <li>Printout of conference schedule.</li> <li>If you are a speaker, bring a printout of the invitation email and the schedule section where your talk or tutorial is shown.</li> <li>Proof of address: Utility bill to show where you live, copy of lease or mortgage bill, or state and/or federal tax payment bills.</li> <li>Proof of employment or school enrollment.</li> </ul> </li> </ul> <p>If you are denied entry at the US border with a valid visa, we will refund 100% of your conference ticket. If you are also an Opportunity Grant recipient, we will also still reimburse travel expenses incurred in getting that far.<br> Please be sure to review the criteria for <a href="https://www.uscis.gov/working-united-states/temporary-visitors-business/b-1-temporary-business-visitor">B-1 Temporary Visa</a> if you are eligible.<br> Make sure to review the criteria for any other type of visa necessary for your home country nationals. There is more information in the <a href="https://travel.state.gov/content/visas/en.html">USCIS site</a>.</p> <p>We are looking forward to seeing you in Chicago in August!</p> 2026-06-10T16:00:00Z https://2026.djangocon.us/news/preparing-for-sprints-as-project-leader/ <p>This article outlines the things you should consider doing when preparing to lead a project at sprints to maximize connection and collaboration. This is for people who are attending sprints at a conference who intend to collaborate and lead others to contribute to a given project.</p> <p>If you're looking for general information on sprints, see <a href="/news/contribution-sprints/">&quot;Contribute to Django at the Contribution Sprints!&quot;</a></p> <h2 id="table-of-contents" tabindex="-1">Table of contents</h2> <ul> <li><a href="#promote-your-participation!">Promote your participation!</a></li> <li><a href="#prework-reflection">Prework reflection</a></li> <li><a href="#prepare-the-contributing-documentation">Prepare the contributing documentation</a></li> <li><a href="#identify-the-available-work">Identify the available work</a></li> <li><a href="#identify-what-you-will-need-the-day-of">Identify what you will need the day of</a></li> <li><a href="#communicate-with-the-organizers">Communicate with the organizers</a></li> <li><a href="#do-something-extra">Do something extra</a></li> <li><a href="#sprint-leader-checklist">Sprint leader checklist</a></li> </ul> <h2 id="promote-your-participation!" tabindex="-1">Promote your participation!</h2> <p>This was originally at the end, but I moved it up. This is the main thing you should do. People contribute at sprints because they want to collaborate and connect. You don’t have to wait until the conference to start that process, so get started now!</p> <p>Here are some ideas:</p> <ul> <li>Post on your social media regularly with the conference hash tag that you’ll be there</li> <li>Write a blog post that you’ll be there</li> <li>Talk about what issues you’re excited about</li> <li>Make it clear you want help from the community and where your needs are</li> </ul> <p>This step is immensely helpful to you, your project and the conference. People are more likely to attend sprints and the conference if they know what is going on. You’re more likely to find contributors if more people attend. The conference needs new and returning attendees to be sustainable.</p> <p><strong>Talking about your project and how you’ll be at the conference is a win for everyone.</strong> Please do it!</p> <h2 id="prework-reflection" tabindex="-1">Prework reflection</h2> <p>Similar to preparing for a conference, you need to ask yourself a few questions:</p> <ol> <li>What are you looking to get out of sprints?</li> <li>What does your project need?</li> <li>What are you capable of doing?</li> </ol> <p><strong>There are no right or wrong answers.</strong> Having an understanding of where you and the project stand will help you communicate what you’re looking for and build off-ramps for incompatible individuals so everyone can have their expectations met.</p> <p>An example answer set would be:</p> <ol> <li>To meet new people, grow my network and learn something new.</li> <li>More regular contributors</li> <li>Answer basic questions about running the project, know who to ping when things get hard, can teach others how to run the tests and build the docs locally.</li> </ol> <p>In the above case, there’s nothing about being an expert on the project or being the sole maintainer. Those things certainly help, and are critical when you want to collaborate on big projects at sprints, but for the purposes of growing the community and contributor base, they are unnecessary.</p> <h2 id="prepare-the-contributing-documentation" tabindex="-1">Prepare the contributing documentation</h2> <p>With your understanding of the goals for the sprint, it’s time to take a look at the project itself to determine if it’s prepared for new contributors. It’s worth doing the basics:</p> <ol> <li>Read the contribution docs and freshen them up <ol> <li>Include how to install dependencies</li> <li>Include how to run tests locally</li> <li>Include how to build the documentation locally</li> <li>Include how to run linters, formatters and/or type-checking locally</li> <li>Include where to look for issues to work on</li> </ol> </li> <li><strong>Create a fresh environment and confirm any code works</strong></li> </ol> <h2 id="identify-the-available-work" tabindex="-1">Identify the available work</h2> <p>One of the challenges to open source software is finding something to work on. Depending on the types of contribution you’re looking for and that you’re capable of supporting, consider:</p> <ul> <li>Reviewing issues and adding newcomer friendly / beginner labels</li> <li>Identifying issues that are well-contained and could be completed in a day’s worth of effort</li> <li>Identifying ideas/features that could be implemented or explored</li> </ul> <p>It can be helpful to <strong>create a single issue for the sprint that links to the various issues, features and ideas</strong> that you’re looking to work on. This has the benefit of communicating to your other contributors that these will be iterated on in the sprint, allowing them to add their own or ask questions. It also provides you with a single link to use when promoting your participation in sprints or when you’re speaking with sprinters.</p> <h2 id="identify-what-you-will-need-the-day-of" tabindex="-1">Identify what you will need the day of</h2> <p>Imagine what it will be like during the sprints. You have the ideal number of participants who want to participate exactly as you’re hoping. What will you be doing? What will you be using? Do you need to bring anything with you? You can ask the conference organizers for help with materials as well.</p> <p>Some examples of materials may be:</p> <ul> <li>Paper and pens</li> <li>Whiteboard</li> <li>TV</li> </ul> <p>While extra materials can be helpful, it’s also beneficial to prepare as if you only have your computer. Don’t be entirely reliant on the organizers because they are likely volunteers and people can make mistakes.</p> <h2 id="communicate-with-the-organizers" tabindex="-1">Communicate with the organizers</h2> <p>Depending on the conference, you may be able to get your project listed on the sprints page. At DjangoCon US, we would love to know if you plan to be at sprints and which project you’re leading.</p> <p>Let us know on your sprints ticket(s) or email us directly at <a href="mailto:sprints@djangocon.us">sprints@djangocon.us</a>.</p> <p>The organizers at DjangoCon US will be hosting a few virtual office hour sessions before the conference for attendees to get their laptops ready to contribute to a project. Knowing that you’ll be there allows us to steer people towards your project so they can clone the repo, set up a virtual environment and run the tests, all before the conference, allowing you more time to collaborate. <strong>So please, let us know if you’re coming!</strong></p> <h2 id="do-something-extra" tabindex="-1">Do something extra</h2> <p>This is entirely optional, hence the “extra”. The people who attend sprints to contribute want to feel connected to the community and help build something meaningful. The challenge is that it’s intimidating to do in public. People let judgement creep in and worry about perception. <strong>Consider what you can do to eliminate that fear and make them feel welcomed.</strong></p> <p>At DjangoCon US, when someone gets their PR merged, the entire room breaks out into applause. Apparently in the past there was a gong for a person to ring. That’d be even cooler. The point is to have a ritual that signals, “hey this person did something challenging and we should celebrate their accomplishment!” It also forms a memory for that person. They will remember that the community applauded their efforts no matter how small.</p> <p>The BeeWare project takes the above even further. <a href="https://beeware.org/contributing/challenge-coins/">They award challenge coins to anyone who participates</a>. While I haven’t done this on any of my projects, the idea is still inspirational.</p> <p><strong>What can you do to make your sprint event memorable for others?</strong></p> <h2 id="sprint-leader-checklist" tabindex="-1">Sprint leader checklist</h2> <p>In case it’s helpful here is a checklist with the above ideas.</p> <ul> <li>Announce that you’ll be at sprints and want to people to collaborate with on your project <ul> <li>Post on your social media</li> <li>Write a blog post</li> </ul> </li> <li>Reflect on what you are looking to get out of sprints</li> <li>Reflect on what your project need</li> <li>Reflect on what you are capable of doing</li> <li>Review the contribution docs <ul> <li>Does it show how to install dependencies</li> <li>Does it show how to run tests locally</li> <li>Does it show how to build the documentation locally</li> <li>Does it show how to run linters, formatters and/or type-checking locally</li> <li>Does it show where to look for issues to work on</li> <li>Create a fresh environment and confirm any code works</li> </ul> </li> <li>Review issues and add newcomer friendly / beginner labels</li> <li>Identify issues that are well-contained and could be completed in a day’s worth of effort</li> <li>Identify ideas/features that could be implemented or explored</li> <li>Create a single issue for the sprint that links to the various issues, features and ideas</li> <li>Pack the materials you’ll need (paper, pen, whiteboard, etc)</li> </ul> 2026-06-08T12:00:00Z https://2026.djangocon.us/news/announcing-lineup/ <p>We are delighted to present our tutorial and talk lineup!</p> <p>The final talk and tutorial schedule will be announced soon. If you haven't purchased your ticket yet, <a href="https://ti.to/defna/djangocon-us-2026">they're still on sale</a>.</p> <p>Congratulations to the presenters of the tutorials and talks below!</p> <h2 id="talks-(monday%2C-august-24-through-wednesday%2C-august-26)" tabindex="-1">Talks (Monday, August 24 through Wednesday, August 26)</h2> <p><em>All talks will be available live for those with online-only tickets. They will be posted to YouTube after the conference for free.</em></p> <ul> <li>Abigail Afi Gbadago (<a href="https://www.linkedin.com/in/abigail-afi-gbadago/">website</a>) - Polyglot Persistence with Django: When One Database Isn't Enough</li> <li>Andrew Selzer (<a href="https://www.linkedin.com/in/andrew-selzer/">website</a>) - Enter the Ecosystem: Contributing to Django Open Source Projects</li> <li>Angufibo Lincoln (<a href="https://www.linkedin.com/in/linc-/">website</a>) - Fail Your CI in Performance Regressions: Bringing Performance Testing to Django</li> <li>Barkha Jain - Scientists Meet Django: Building Bridges Between Research and Software</li> <li>Calvin Hendryx-Parker (<a href="https://Fosstodon.org/@CalvinHP">mastodon</a>, <a href="https://sixfeetup.com/">website</a>) and Frank Wiles - Batteries vs. Speed: The Django/FastAPI Debate</li> <li>Chrissy Wainwright (<a href="https://sixfeetup.com/">website</a>) - One URL to Rule Them All: Dynamic Landing Pages in Wagtail</li> <li>Dan Ryan (<a href="https://dryan.com/@d">mastodon</a>, <a href="https://dryan.com">website</a>) - Good Conduct: How Django Modernized Its Code of Conduct</li> <li>Drishti Jain - GeoDjango at City Scale: Spatial Data for Urban Systems</li> <li>Eduardo Felipe Castegnaro - Keeping Pace with Django: Evolving Through 15 years of Updates</li> <li>Elizabeth Christensen (<a href="https://fosstodon.org/@sqlliz">mastodon</a>, <a href="https://www.crunchydata.com/blog/author/elizabeth-christensen">website</a>) - What's New in Postgres 18 &amp; 19</li> <li>Jack Linke (<a href="https://social.jacklinke.com/@jack">mastodon</a>, <a href="https://jacklinke.com">website</a>) - Yes, we allow substitutions. No, we don't serve spaghetti.</li> <li>Jacob Walls - Auto-prefetching with model field fetch modes in Django 6.1</li> <li>James Stuckey Weber (<a href="https://front-end.social/@jamessw">mastodon</a>, <a href="https://www.oddbird.net/authors/james/">website</a>) - But did you know the browser already does that?</li> <li>Josh Thomas (<a href="https://joshthomas.dev/@josh">mastodon</a>, <a href="https://joshthomas.dev">website</a>) - Agents All the Way Down: How AI Coding Agents Changed How I Write Django</li> <li>Karen Tracey (<a href="https://fosstodon.org/@kmtracey">mastodon</a>) - Django 6: The Most Exciting Release Ever</li> <li>Kasey Kelly - Taming Your Templates: Component-Based Frontends in Django</li> <li>Kumar Shivendu (<a href="https://kshivendu.dev">website</a>) - Beyond REST: Implementing the Model Context Protocol (MCP) in Django</li> <li>Leonardo Batista (<a href="https://www.linkedin.com/in/leonardohenriquebatista/">website</a>) - Scaling Django: Mastering Database Routers with AWS Aurora</li> <li>Matías Bordese - Teach Django Tasks to speak Celery: Building a Celery backend for Django Tasks</li> <li>Meagen Voss (<a href="https://fosstodon.org/@vossisboss">mastodon</a>, <a href="https://wagtail.org">website</a>) - Pragmatic AI: How to gain trust with user-centered AI adoption</li> <li>Mohammad Ahtasham ul Hassan - Breaking the Request Chain: Rethinking Service Communication in Django Systems</li> <li>Monica Oyugi (<a href="https://mastodon.social/@monics">mastodon</a>, <a href="https://medium.com/@monicaoyugi">website</a>) - The Testing Pyramid in Practice for Django</li> <li>Natalia (<a href="https://fosstodon.org/@nessita">mastodon</a>) - Wishlist granted: HTMX without betraying your Django views</li> <li>Paolo Melchiorre (<a href="https://fosstodon.org/@paulox">mastodon</a>, <a href="https://www.paulox.net">website</a>) - The Django UUID Story</li> <li>Sarah Abderemane (<a href="https://mastodon.social/@sabderemane">mastodon</a>, <a href="https://sarahabd.com/">website</a>) - 50 shades of green - One contribution to the Django world</li> <li>Scott Cranfill (<a href="https://compiler.la">website</a>) - Using Django to deliver public transit benefits securely and privately</li> <li>Tobias McNulty - Search-as-you-type for 54 Million Names: PostgreSQL + Django for Fuzzy Name Matching at Scale</li> <li>Will Vincent (<a href="https://fosstodon.org/@wsvincent">mastodon</a>, <a href="https://wsvincent.com/">website</a>) - Modern Django Deployments in 2026</li> </ul> <p>Congratulations to all our speakers!</p> <p>If you'd like to check out these talks and more, <a href="https://ti.to/defna/djangocon-us-2026">tickets are still on sale</a>.<br> We hope to see you in Chicago!</p> 2026-06-04T16:00:00Z https://2026.djangocon.us/news/single-track/ <h1 id="djangocon-us-2026-goes-single-track" tabindex="-1">DjangoCon US 2026 Goes Single-Track</h1> <p>After years of running multiple simultaneous talk tracks, DjangoCon US 2026 will move to a single-track conference format.</p> <p>It's a significant change for the conference and one we didn't make lightly.</p> <h2 id="why-we're-making-this-change" tabindex="-1">Why we're making this change</h2> <p>The simple answer is financial sustainability.</p> <p>Running conferences has become substantially more expensive over the last several years, and sponsorship has not kept pace. Audio/visual production alone scales rapidly with each additional room: recording crews, switching equipment, livestream infrastructure, microphones, staging, and dedicated technical staff all multiply with every added track.</p> <p>At the same time, sponsorship budgets across the tech industry have tightened considerably, and ticket sales have not returned to their pre-covid levels.</p> <p>Like many community-led events, we reached a crossroads: either continue stretching resources across multiple simultaneous tracks and risk diminishing the overall conference experience, or make a focused investment to deliver a stronger, more sustainable DjangoCon US.</p> <p>We chose to focus on an opportunity to try something different.</p> <h2 id="what-a-single-track-djangocon-us-means" tabindex="-1">What a single-track DjangoCon US means</h2> <p>For attendees, the shift comes with an immediate benefit:</p> <blockquote> <p>No more choosing between two great talks happening at the same time.</p> </blockquote> <p>Every attendee, from first-time Django developers to longtime community members, will experience the same talks, keynotes, and announcements together. The hallway conversations after sessions become richer because everyone shares the same context. Discussions continue naturally between talks, over lunch, and throughout the week.</p> <p>That kind of shared experience is increasingly rare at technical conferences.</p> <p>A single-track format also allows us to invest more deeply in each selected session. With fewer presentation slots available, the program becomes more intentional, with additional attention on talk quality, pacing, and the overall flow of the event.</p> <p>Rather than trying to run multiple competing talk rooms at once, we want to make every hour of DjangoCon US feel meaningful.</p> <h2 id="expanding-the-conversations-beyond-the-stage" tabindex="-1">Expanding the conversations beyond the stage</h2> <p>Moving to a single talk track does not mean a smaller conference experience.</p> <p>Alongside the main-stage talks, DjangoCon US 2026 will include open spaces, round tables, hallway discussions, and collaborative problem-solving throughout the conference.</p> <p>Beyond those staples, we're exploring some new ideas for the space and time a second track used to fill: unique experiences and activities you simply can't get online or anywhere outside this conference. We're still shaping what those will look like, so stay tuned for announcements as plans come together.</p> <p>Some of the most valuable moments at DjangoCon US happen away from the podium entirely when a small group gathers around a table to discuss scaling challenges, accessibility, hiring, testing strategies, community organizing, or the future of Django itself.</p> <p>This year, we want to create even more intentional space for those conversations while keeping the main conference program unified.</p> <h3 id="sponsor-a-workshop" tabindex="-1">Sponsor a workshop</h3> <p>Hands-on workshops remain one of the most impactful parts of attending conferences.</p> <p>If your company wants to support practical, in-depth learning or help bring expert educators to the community, workshop sponsorship is one of the most direct ways to contribute.</p> <p>Workshops help keep tickets accessible while supporting high-quality educational content for attendees at every experience level.</p> <p><strong><a href="https://2026.djangocon.us/sponsors/information/">View sponsorship information →</a></strong></p> <h2 id="join-us-in-chicago" tabindex="-1">Join us in Chicago</h2> <p>DjangoCon US 2026 will bring the community together for five days of talks, open spaces, workshops, sprints, hallway conversations, and collaboration.</p> <p>We can't wait to see you in Chicago.</p> <p><strong>August 24–28, 2026</strong><br> <strong>voco Chicago Downtown</strong></p> <p><strong><a href="https://2026.djangocon.us/">Get your ticket →</a></strong></p> 2026-06-03T16:00:00Z https://2026.djangocon.us/news/contribution-sprints/ <p>We are excited to talk to you about contribution sprints at DjangoCon US! They are being held <strong>Thursday, August 27th and Friday, August 28th, 2026</strong>, from <strong><a href="https://time.is/0900AM_27_August_2026_in_Chicago">9am</a> to <a href="https://time.is/0500PM_27_August_2026_in_Chicago">5pm</a> CDT</strong> each day at the <strong><a href="https://www.ihg.com/voco/hotels/us/en/chicago/chiwp/hoteldetail">voco Chicago Downtown</a></strong>, the same venue as the main conference and virtually on our conference Slack. <strong>They are free to attend and open to everyone</strong>.</p> <p>📣 <strong><a href="https://ti.to/defna/djangocon-us-2026">Get your ticket</a></strong> and join us!</p> <h2 id="what-is-a-contribution-sprint%3F" tabindex="-1">What is a contribution sprint?</h2> <p>Contribution Sprints are a superset of Development Sprints. They serve the same purpose while increasing the range of contribution types and opportunities.</p> <p>Let’s start with what some people already know: <a href="https://2022.djangocon.us/news/dev-sprint-attendees/">Development Sprints</a> are an opportunity for people who maintain open source projects (or want to get involved in doing so) to sit and work together on that goal. They have mostly focused on contributing code, tests, and documentation. However, open source projects often need more than those things. This is especially true as a project grows. Development Sprints are one type of Contribution Sprint.</p> <p>Many of the new things a project needs as it grows fall under the idea of project governance. Here’s a short list of general governance issues a project may face as it grows:</p> <ul> <li>General project governance (Who leads the project? How? How are decisions made? How are new leaders developed? How are conflicts resolved?)</li> <li>Onboarding new contributors</li> <li>Funding/Finance: does your project want it? Is it needed? Who will manage it? How will they manage it?</li> <li>Project marketing</li> <li>Graphic/logo design</li> <li>Legal/licensing questions</li> <li>Clarifying code, documentation, and testing conventions (metadata that guides the rest of your contribution process)</li> </ul> <p>There is an excellent video on this topic by <a href="https://www.youtube.com/watch?v=b2WHTNE4AZk">Shauna Gordon-McKeon</a>, part of the PyCon US 2023 <a href="https://www.youtube.com/@MaintainersSummit">Maintainers Summit</a>. If you maintain a project, or are interested in helping maintain one, we recommend checking it out.</p> <h2 id="how-%26-why-to-lead-a-contribution-sprint" tabindex="-1">How &amp; Why To Lead a Contribution Sprint</h2> <p>The &quot;why&quot; is clear: if you’ve realized your project needs help, especially with things beyond code, this is a great opportunity to find that help.</p> <p>The &quot;how&quot; can be trickier, so here are some specific suggestions:</p> <ul> <li>Think about the non-code needs your project has.</li> <li>Ask for help in those areas.</li> <li>Document the need for that help in your project's <strong>CONTRIBUTING</strong> documentation.</li> <li>Make it clear in all of your communications that you’re looking for more than just code contributions. Many people still think contributing to an open source project <em>only</em> means writing code.</li> </ul> <h2 id="how-%26-why-to-join-a-contribution-sprint" tabindex="-1">How &amp; Why to Join a Contribution Sprint</h2> <p>The &quot;why&quot; can vary. Maybe you don’t feel confident enough to contribute code (you probably are, but we understand the feeling). Or maybe you have skills in non-code areas that you would love to use to help a project thrive.</p> <p>The &quot;how&quot; starts with identifying your strengths, then connecting with projects that might need them. Shauna’s video is a great starting point. Once you identify a project that interests you, reach out! Sometimes a project doesn’t realize what kind of help it needs until someone offers it.</p> <h2 id="preparing-to-lead-or-organize-a-sprint" tabindex="-1">Preparing to Lead or Organize a Sprint</h2> <p>If you’re a project maintainer or contributor, a bit of preparation can help make the most of the sprint and avoid burnout. Most open source maintainers are unpaid volunteers, we appreciate you.</p> <p>Here are some steps you can take ahead of time:</p> <ul> <li>Make sure your <strong>CONTRIBUTING</strong> guide is up to date. If your project doesn’t have one, check out <a href="https://www.django-rest-framework.org/community/contributing/">Django REST Framework</a>, <a href="https://github.com/pytest-dev/pytest/blob/main/CONTRIBUTING.rst">pytest</a>, <a href="https://docs.djangoproject.com/en/dev/internals/contributing/">Django</a>, or <a href="https://devguide.python.org/">CPython</a> for inspiration.</li> <li>Include setup instructions, test commands, code style, CI guidelines, and PR templates.</li> <li>Rather than just flagging &quot;beginner-friendly&quot; issues, try breaking down large issues into smaller, approachable tasks.</li> </ul> <h2 id="supporting-contributors-as-a-non-maintainer" tabindex="-1">Supporting Contributors as a Non-Maintainer</h2> <p>If you're an active contributor (even without commit access), you can:</p> <ul> <li>Help mentor newcomers with patience and empathy.</li> <li>Gauge each contributor’s experience level and tailor your help.</li> <li>Update documentation as needed to reflect your mentoring experience.</li> <li>Break down complex issues into bite-sized contributions.</li> <li>Let someone co-pilot an issue with you.</li> </ul> <h2 id="tips-for-hybrid-participation" tabindex="-1">Tips for Hybrid Participation</h2> <p>We are continuing the hybrid format: virtual and in-person. This brings both challenges and opportunities. While you might miss the spontaneity of in-person collaboration, working synchronously online is a powerful experience. Make sure:</p> <ul> <li>Your project uses real-time chat (Slack, Zulip, Discord, etc.)</li> <li>Your docs are easily accessible to virtual attendees.</li> <li>You’re ready to share screens, links, and tasks in real time.</li> </ul> <h2 id="final-notes" tabindex="-1">Final Notes</h2> <p>The Contribution Sprints are free and open to everyone. They will run <strong>August 27–28, 2026 from <a href="https://time.is/0900AM_27_August_2026_in_Chicago">9am</a> to <a href="https://time.is/0500PM_27_August_2026_in_Chicago">5pm</a> CDT</strong> at <strong>voco Chicago Downtown</strong> and online via Slack.</p> <ul> <li>Want to lead or organize a sprint? Great!</li> <li>Want to help? We’d love to have you.</li> <li>Have questions? Email us at <strong><a href="mailto:sprints@djangocon.us">sprints@djangocon.us</a></strong>.</li> </ul> <p>🎟️ <strong><a href="https://ti.to/defna/djangocon-us-2026">Get your ticket now</a></strong> and be part of something awesome!</p> 2026-05-27T15:00:00Z https://2026.djangocon.us/news/early-bird-tickets-end/ <p>Don't miss your chance to save. Early bird ticket sales for DjangoCon US 2026 are ending soon on May 31, 2026. Secure your spot now to join the community at a discounted rate.</p> <p><a href="https://ti.to/defna/djangocon-us-2026">Grab your early bird ticket here.</a></p> <p>DjangoCon US is where the Django community comes together, from maintainers and contributors to teams running production apps and newcomers. Expect community-selected talks, Django contribution sprints, and a welcoming space for everyone.</p> <p>Join us for five days of inspiration and learning at the Voco Chicago Downtown.</p> 2026-03-19T10:55:00Z https://2026.djangocon.us/news/proposal-selection/ <p>The DjangoCon US schedule is always highly anticipated. But how does it all come together?</p> <p>The journey from an open Call for Proposals (CFP) to the final lineup of talks and keynote sessions is a thoughtful and collaborative process designed to foster fairness and showcase the best of the Django community.</p> <h2 id="2026-program-timeline" tabindex="-1">2026 Program Timeline</h2> <p><em>*Subject to change depending on the number of submissions and other factors.</em></p> <ul> <li><strong>CFP Deadline Extension</strong>: March 23</li> <li><strong>Reviewer Deadline</strong>: April 10</li> <li><strong>Panel Finalization</strong>: April 28</li> <li><strong>Speaker Notifications</strong>: June 8</li> <li><strong>Schedule Announcement</strong>: June 22</li> <li><strong>Start of Keynote Announcements</strong>: July 1</li> </ul> <h2 id="call-for-proposals-opens" tabindex="-1">Call for Proposals Opens</h2> <p>The community proposes talks and tutorials by filling in the <a href="https://pretalx.com/djangocon-us-2026/cfp">CFP</a>. We use <a href="https://pretalx.com/p/about/">Pretalx</a>, a platform designed for conferences that support <strong>anonymous review</strong> and <strong>structured scoring</strong>. Thus, each submission is evaluated based on content, not the speaker's name or background.</p> <h2 id="anonymization-%26-code-of-conduct-compliance" tabindex="-1">Anonymization &amp; Code of Conduct Compliance</h2> <p>Once the CFP closes, the program team carefully reviews every submission to:</p> <ul> <li><strong>Anonymize</strong> any unique identifying details.</li> <li><strong>Ensure Code of Conduct compliance</strong>.</li> </ul> <p>This step is crucial for fair and unbiased reviewing. The person responsible for anonymization does not participate in the anonymous review process.</p> <h2 id="community-reviews-talks" tabindex="-1">Community Reviews Talks</h2> <p>Once proposals are anonymized, we open the review process to a team of volunteer reviewers from the community. They follow guidelines that promote consistency, fairness, and awareness of potential bias.</p> <h2 id="reviewer-guidelines-emphasize%3A" tabindex="-1">Reviewer Guidelines Emphasize:</h2> <ul> <li><strong>Focusing on content</strong>, not style, grammar, or speaker identity</li> <li><strong>Leaving a comment for all &quot;No&quot; ratings</strong> (and encouraged for &quot;Maybe&quot;)</li> <li><strong>Flagging known proposals</strong> using a BIAS: prefix and skipping scoring</li> <li><strong>Identifying any remaining personal info</strong></li> <li><strong>Disclosing conflicts of interest</strong></li> </ul> <p>Reviewers have until <strong>April 10</strong> to provide feedback on as many proposals as possible.</p> <h2 id="committee-deliberation-%26-selection" tabindex="-1">Committee Deliberation &amp; Selection</h2> <p>Once the reviews are in, the committee will lift the anonymization and meet to create the final schedule. At this stage, we look at:</p> <ul> <li><strong>Review scores and written feedback</strong></li> <li><strong>Topic coverage</strong> (e.g., avoiding repetition like six HTMX talks)</li> <li><strong>Speaker diversity</strong> (especially elevating underrepresented voices and first-time speakers)</li> <li><strong>Company representation</strong> (ensuring one organization doesn't dominate)</li> <li><strong>Prior speaking history and organizer involvement</strong></li> </ul> <p>Some talks are accepted or declined based on strong consensus. The most difficult decisions often revolve around the final handful of slots, which we may reserve in case of scheduling conflicts or withdrawals.</p> <p>The speakers will receive notifications about the decision on or before <strong>May 15</strong>. Speakers need to reply to acceptance emails to confirm their talks.</p> <p>At this point, we evaluate the suggested panelists and hosts who will participate in the last conference day and the discussion topic.</p> <h2 id="keynote-speaker-selection" tabindex="-1">Keynote Speaker Selection</h2> <p>Keynote speakers follow a separate, invitation-based process that begins well before the CFP closes. As outlined by previous DjangoCon US Chair Drew Winstel in <a href="https://winstel.dev/2024/10/20/what-makes-a-good-dcus-keynote/">his blog post</a>, we look for individuals who bring:</p> <ul> <li><strong>Emotional resonance</strong> and the ability to connect and engage with the audience</li> <li><strong>A compelling, unique perspective—reflective</strong>, funny, challenging, or inspiring</li> <li><strong>Stage presence</strong>, though extensive speaking experience isn't required</li> <li><strong>Representation of the community</strong>, especially those who've contributed significantly or brought underrepresented viewpoints to the forefront</li> </ul> <p>Keynote announcements typically occur after the talk schedule is shared.</p> <p>DjangoCon US is more than a conference. It's a reflection of the community that makes Django special. Every part of our program, from anonymous reviews to committee deliberations and keynote invitations, is rooted in care and intentionality. We aim to surface new voices, avoid bias, and curate a meaningful and engaging conference experience.</p> 2026-03-12T11:00:00Z https://2026.djangocon.us/news/cfp-deadline-extended/ <p>We've received many great proposals already but want to give folks a little extra time to submit their talks. The <a href="https://pretalx.com/djangocon-us-2026/cfp">call for proposals</a> deadline has been extended to March 23, 2026 at <a href="https://time.is/1100AM_23_March_2026_in_Chicago?DjangoCon_US_CFP_Closes">11AM CDT</a>.</p> <p>We welcome proposals no matter your background or experience level with Django. Your proposal can be from a wide range of topics; non-Django and community topics are welcome. You can look at our <a href="https://2025.djangocon.us/news/announcing-lineup/">talk lineup</a> from last year for reference. You are also welcome to submit more than one proposal. (Though we'll likely only select one per speaker.)</p> <p>Also, if you know someone you think would be a good speaker at this conference, this is the time to reach out and tell them you'd love to see them submit a talk!</p> <p>We are excited to see more awesome proposals and can't wait to see you in Chicago!</p> 2026-02-20T12:00:00Z https://2026.djangocon.us/news/call-for-proposals/ <p>We are excited that DjangoCon US 2026 is now open for talk submissions: <a href="https://pretalx.com/djangocon-us-2026/cfp">call for proposals</a>! The deadline for submissions is <s>March 16th</s> March 23, 2026 at <a href="https://time.is/1100AM_23_March_2026_in_Chicago?DjangoCon_US_CFP_Closes">11AM CDT</a>.</p> <p>We invite you to submit your proposal no matter your background or experience level with Django. Proposals can be from a wide range of topics; non-Django and community topics are welcome. You can look at our <a href="https://2025.djangocon.us/news/announcing-lineup/">talk lineup</a> from last year for reference.</p> <p>We fancy first-timers! If you haven't spoken at a conference or given a tutorial before, this is your invitation to do so. Don't let the idea that you're not famous or an expert stop you from submitting. It certainly won't stop us from selecting your talk or tutorial and it won't stop the audience from enjoying it! If you still need help deciding on a topic take a look at our own Drew Winstel's <a href="https://winstel.dev/2026/01/05/talk-ideas-for-dcus-26/">blog post</a> for some ideas.</p> <p>Plus there are perks! Presenters get free admission to DjangoCon US! <a href="https://2026.djangocon.us/opportunity-grants/">Grants</a> to assist with your travel and lodging expenses are available as well. The form for <a href="https://forms.gle/xYSsdAGR5RbvtH9q7">Opportunity Grants</a> is now live, and <strong>the application deadline is March 16th, 2026</strong>.</p> <p>For more information on talk and tutorial formats, please check out our <a href="/speaking/">speaker information page</a>.</p> <p>We want everyone attending DjangoCon US to feel safe, welcome, and included. To that end, we have a <a href="/conduct/">Code of Conduct</a> for all speakers and attendees.</p> <p>If you have questions, feel free to <a href="mailto:hello@djangocon.us">contact us</a>.</p> <p>We are excited to see your proposals and can't wait to see you in Chicago!</p> 2026-02-12T18:00:00Z https://2026.djangocon.us/news/announcing-date-change/ <h1 id="djangocon-us-is-changing-dates!" tabindex="-1">DjangoCon US is changing dates!</h1> <p>Due to a very large conference happening in Chicago the week of September 14 that is causing hotel prices to skyrocket (over $400 per night for nearby hotels), DjangoCon US is moving to the week of August 24.</p> <p>This will help keep costs more affordable for our guests, and maybe Lake Michigan will be warm enough for people who would like to take a morning swim!</p> <h2 id="schedule" tabindex="-1">Schedule</h2> <ul> <li>Monday, August 24 through Wednesday, August 26: Talks</li> <li>Thursday, August 27 and Friday, August 28: Sprints</li> </ul> <p>We apologize for the inconvenience for anyone who has already made travel plans.</p> <p>We look forward to seeing you in Chicago!</p> <p><small>Image credit: Bartek Pawlik</small></p>