]> jfr.im git - irc/freenode/web-7.0.git/blame_incremental - content/news/2017-02-08-django-and-freenode.md
Update policies.md
[irc/freenode/web-7.0.git] / content / news / 2017-02-08-django-and-freenode.md
... / ...
CommitLineData
1---
2Title: Django and freenode
3Author: Tim Graham (timograham)
4Date: 2017-02-08T20:00+01:00
5Slug: django-and-freenode
6---
7
8For nearly twelve years, the [Django Project](https://www.djangoproject.com/)
9has endeavoured to improve "the web framework for perfectionists with
10deadlines." Django is a high-level Python Web framework that encourage
11rapid development and clean, pragmatic design. Built by experienced
12developers, it takes care of much of the hassle of Web development,
13so you can focus on writing your app without needing to reinvent the
14wheel. Of course, it's free and open source.
15
16I’m contracted full-time by the Django Software Foundation
17[as a fellow](https://www.djangoproject.com/fundraising/#fellowship-program),
18to manage some of the administrative and community management tasks of
19the Django project to support rapid development of Django itself. The
20fellowship program has a major positive impact on how Django is
21developed and maintained, and I’d encourage any large open source
22project to consider a similar program.
23
24The Django community is vibrant across the globe, with many annual
25conferences and local meetups. Sprints are often held at these events,
26but Django’s development is mainly coordinated remotely, so good
27communication tools are important to us.
28
29## How Django uses freenode
30Our community support channels include #django and the
31[django-users mailing list](https://groups.google.com/forum/#!forum/django-users).
32Discussions about the development of Django itself are held
33in #django-dev and the
34[django-developers mailing list](https://groups.google.com/forum/#!forum/django-developers). #django-sprint
35provides a chat for sprint participants, including those who want to
36join remotely. Finally, private discussions of the Django team are held
37in the #django-core channel.
38
39To keep our community safe and welcoming, Django's
40[Code of Conduct](https://www.djangoproject.com/conduct/) applies to
41all spaces managed by the Django project or Django Software Foundation
42(DSF). This includes IRC, the mailing lists, the issue tracker, DSF
43events, and any other forums created by the project team which the
44community uses for communication.
45
46## What's next for Django?
47We're currently working toward releasing Django 1.11, our next
48long-term support release, in April. This will be the last version of
49Django to support Python 2.7. Meanwhile, Django's master development
50branch is targeting Django 2.0 and will support Python 3 only. More
51details are available on [our roadmap](https://www.djangoproject.com/download/#supported-versions).
52
53If you’re interested in learning more about Django,
54[try our tutorial](https://docs.djangoproject.com/en/stable/intro/tutorial01/).
55If you’re already a Django user and want to start contributing, our
56documentation is extensive, including
57[advice for new contributors](https://docs.djangoproject.com/en/dev/internals/contributing/new-contributors/).