Django

We’re happy to report that our second iteration of the Django/PyСharm fundraising campaign - which we ran this summer - was a huge success. This year we helped raise a total of $66,094 USD for the Django Software Foundation! Last year (2016) we ran a ... [More] similar campaign which resulted in a collective contribution of $50,000 USD to the cause. We’re happy we could raise even more money this year for the Django community! If you missed the campaign here’s the essence of the past promotion: For 3 weeks this summer, Django developers could effectively donate to Django Software Foundation by purchasing a new individual PyCharm Professional annual subscription at 30% off, with all proceeds from the sales going to the Django Software Foundation. Read more details here. All the money raised goes toward Django outreach and diversity programs: supporting DSF, the Django Fellowship program, Django Girls workshops, sponsoring official Django conferences, and other equally incredible projects. We want to say huge thanks to the DSF for their active collaboration and making this fundraiser happen. We hope that in 2018 we’ll be able to make this yearly event even more successful! The DSF general fundraising campaign is still on-going, and we encourage everyone to contribute to the success of Django by donating to DSF directly. If you have any questions, get in touch with us at [email protected] or JetBrains at [email protected]. [Less]

The Django team is happy to announce the release of Django 2.0. This release starts Django’s use of a loose form of semantic versioning, but there aren’t any major backwards incompatible changes (except that support for Python 2.7 is removed) that ... [More] might be expected of a 2.0 release. Upgrading should be a similar amount of effort as past feature releases. The release notes cover the assortment of new features in detail, but a few highlights are: A simplified URL routing syntax that allows writing routes without regular expressions. A responsive, mobile-friendly contrib.admin. Window expressions to allow adding an OVER clause to querysets. You can get Django 2.0 from our downloads page or from the Python Package Index. The PGP key ID used for this release is Tim Graham: 1E8ABDC773EDE252. With the release of Django 2.0, Django 1.11 has reached the end of mainstream support. The final minor bug fix release, 1.11.8, was issued today. As a long-term support release, Django 1.11 will receive security and data loss fixes until April 2020. Django 1.10 has reached the end of extended support. All Django 1.10 users are encouraged to upgrade to Django 1.11 or later to continue receiving fixes for security issues. See the downloads page for a table of supported versions and the future release schedule. [Less]

After three years of full-time work as the Django Fellow, I'd like to scale back my involvement to part-time. That means it's time to hire another Fellow who would like to work on Django 20-40 hours per week. The position is ongoing - the successful ... [More] applicant will have the position until they choose to step down. The position of Fellow is primarily focused on housekeeping and community support - you'll be expected to do the work that would benefit from constant, guaranteed attention rather than volunteer-only efforts. In particular, your duties will include: monitoring the [email protected] email alias and ensuring security issues are acknowledged and responded to promptly fixing release blockers and helping to ensure timely releases fixing severe bugs and helping to backport fixes to these and security issues reviewing and merging pull requests triaging tickets on Trac answering user questions on IRC and the django-developers mailing list helping new Django contributors land patches and learn our philosophy Being a committer isn't a prerequisite for this position; we'll consider applications from anyone with a proven history of working with either the Django community or another similar open-source community. Your geographical location isn't important either - we have several methods of remote communication and coordination that we can use depending on the timezone difference to the supervising members of Django. You'll be expected to post a weekly report of your work to the django-developers mailing list. If you don't perform the duties to a satisfactory level, we may end your contract. We may also terminate the contract if we're unable to raise sufficient funds to support the Fellowship on an ongoing basis (unlikely, given the current fundraising levels). Compensation isn't competitive with full-time salaries in big cities like San Francisco or London. The Fellow will be selected to make best use of available funds. If you're interested in applying for the position, please email us with details of your experience with Django and open-source contribution and community support in general, the amount of time each week you'd like to dedicate to the position (a minimum of 20 hours a week), your hourly rate, and when you'd like to start working. The start date is flexible and will be on or after January 1, 2018. Applications will be open until 1200 UTC, December 18, 2017, with the expectation that the successful candidate will be announced around December 22. Successful applicants will not be an employee of the Django Project or the Django Software Foundation. Fellows will be contractors and expected to ensure that they meet all of their resident country's criteria for self-employment or having a shell consulting company, invoicing the DSF on a monthly basis and ensuring they pay all relevant taxes. If you or your company is interested in helping fund this program and future DSF activities, please consider becoming a corporate member to learn about corporate membership, or you can make a donation to the Django Software Foundation. [Less]

Django 2.0 release candidate 1 is the final opportunity for you to try out the assortment of new features before Django 2.0 is released. The release candidate stage marks the string freeze and the call for translators to submit translations. Provided ... [More] no major bugs are discovered that can't be solved in the next two weeks, Django 2.0 will be released on or around December 1. Any delays will be communicated on the django-developers mailing list thread. Please use this opportunity to help find and fix bugs (which should be reported to the issue tracker). You can grab a copy of the package from our downloads page or on PyPI. The PGP key ID used for this release is Tim Graham: 1E8ABDC773EDE252. [Less]

Malcolm Tredinnick was an early member of Django's core team. He contributed a great deal of code to the Django Project, and a vast amount of his time helping and encouraging others. Malcolm died young, in March 2013. In his memory, the Malcolm ... [More] Tredinnick Memorial Prize is awarded annually. It is intended to recognise someone who participates in the Django community in the same spirit as Malcolm: welcoming, nurturing and suppporting newcomers and helping other people. You can read more about Malcolm and his contribution to Django, and about the prize. We invite your nominations for this year's prize. Please drop us a line at [email protected], telling us whom you'd like to nominate and why you think their contribution is a worthy continuation of Malcolm's work for the Django community. Anyone is welcome to nominate a candidate. Nominations will remain open for two weeks (until Friday 24th November 2017). [Less]

It is that time of year again to think about next year’s Django Software Foundation’s Board of Directors! As you know, the Board guides the direction of the marketing, governance and outreach activities of the Django community. We provide funding ... [More] , resources, and guidance to Django events on a global level. Further we provide support to the Django community with an established Code of Conduct and make decisions and enforcement recommendations for violations. We work closely with our corporate and individual members to raise funds to help support our great community. In order to for our community to continue to grow and advance the Django Web framework, we need your help. The Board of Directors consists of volunteers who are elected to one year terms. This is an excellent opportunity to help advance Django. We can’t do it without volunteers, such as yourself. For the most part, the time commitment is a few of hours per month. There has been some confusion on this in the past, but anyone including current Board members, DSF Members, or the public at large can apply to the Board. It is open to all. If you are interested in helping to support the development of Django we’d enjoy receiving your application for the Board of Directors. Please fill out the application form by 9 December 2017 to be considered. If it is still 9 December somewhere in the world, applications will remain open. If you have any questions about applying, the work, or the process in general please don’t hesitate to reach out via email to [email protected] and one of us will get back with you shortly. Thank you for your time and we look forward to working with you in 2018. The 2017 DSF Board of Directors [Less]

Today we've issued the 1.11.7 bugfix release. The release package and checksums are available from our downloads page, as well as from the Python Package Index. The PGP key ID used for this release is Tim Graham: 1E8ABDC773EDE252.

Django 2.0 beta 1 is an opportunity for you to try out the assortment of new features in Django 2.0. Only bugs in new features and regressions from earlier versions of Django will be fixed between now and 2.0 final (also, translations will be updated ... [More] following the "string freeze" when the release candidate is issued). The current release schedule calls for a release candidate in a month from now with the final release to follow about two weeks after that around December 1. Early and often testing from the community will help minimize the number of bugs in the release. Updates on the release schedule schedule are available on the django-developers mailing list. As with all alpha and beta packages, this is not for production use. But if you'd like to take some of the new features for a spin, or to help find and fix bugs (which should be reported to the issue tracker), you can grab a copy of the beta package from our downloads page or on PyPI. The PGP key ID used for this release is Tim Graham: 1E8ABDC773EDE252. [Less]

Today we've issued the 1.11.6 bugfix release. The release package and checksums are available from our downloads page, as well as from the Python Package Index. The PGP key ID used for this release is Tim Graham: 1E8ABDC773EDE252.

Django 2.0 alpha 1 is now available. It represents the first stage in the 2.0 release cycle and is an opportunity for you to try out the changes coming in Django 2.0. Django 2.0 has an assortment of new features which you can read about in the ... [More] in-development 2.0 release notes. This alpha milestone marks a complete feature freeze. The current release schedule calls for a beta release in about a month and a release candidate about a month from then. We'll only be able to keep this schedule if we get early and often testing from the community. Updates on the release schedule schedule are available on the django-developers mailing list. As with all alpha and beta packages, this is not for production use. But if you'd like to take some of the new features for a spin, or to help find and fix bugs (which should be reported to the issue tracker), you can grab a copy of the alpha package from our downloads page or on PyPI. The PGP key ID used for this release is Tim Graham: 1E8ABDC773EDE252. [Less]