# Where is the DEP discussion?

**URL:** <https://forum.djangoproject.com/t/where-is-the-dep-discussion/46183>\
**Category:** Django Internals\
**Created:** [October 13, 2026, 2:20am UTC](https://forum.djangoproject.com/t/where-is-the-dep-discussion/46183 "2026-10-13T02:20:56Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![villager](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/villager/32/24305_2.png) [@villager](https://forum.djangoproject.com/u/villager)\
**Post date:** [October 13, 2026, 2:20am UTC](https://forum.djangoproject.com/t/where-is-the-dep-discussion/46183/1 "2026-10-13T02:20:57Z")

</div>

Draft DEPs do not always have a related Forum discussion, and when they do, the posts are not named or linked consistently making them difficult to find.

[DEP 0001](https://github.com/django/deps/blob/main/final/0001-dep-process.rst#submitting-the-draft) makes it very clear:

> a draft DEP should be presented to the Django Forum.

Is this something that should be enforced more strongly?

I find the discussions on the Forum helpful and accessible. The Forum also has more community engagement than GitHub or Trac; a Forum post is crucial to giving the community a fair chance to weigh in. I think it would be good if all DEP Pull Requests had a related Forum post beginning with the DEP number. For example: **DEP 1: DEP Purpose and Guidelines**

The Python Enhancement Proposal (PEP) process, for inspiration, is quite structured. Recent PEP 823 received a forum post, [PEP 823: None-aware access operators](https://discuss.python.org/t/pep-823-none-aware-access-operators/109159) and it is linked in the front matter of the [PEP draft](https://peps.python.org/pep-0823/).

---

<div class="post-metadata">

**Author:** ![CodenameTim](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/codenametim/32/31507_2.png) [@CodenameTim](https://forum.djangoproject.com/u/CodenameTim)\
**Post date:** [October 14, 2026, 1:33pm UTC](https://forum.djangoproject.com/t/where-is-the-dep-discussion/46183/2 "2026-10-14T13:33:30Z")

</div>

This seems easy enough to do and is generally a good thing to do for visibility.

Would you be willing to do the leg work for getting the existing DEPs up to date?

---

<div class="post-metadata">

**Author:** ![nanorepublica](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/nanorepublica/32/14211_2.png) [@nanorepublica](https://forum.djangoproject.com/u/nanorepublica)\
**Post date:** [October 14, 2026, 1:46pm UTC](https://forum.djangoproject.com/t/where-is-the-dep-discussion/46183/3 "2026-10-14T13:46:30Z")

</div>

Related OCWG Idea Issue: [Increase visibility of DEP/WG/etc repo activity · Issue #24 · django/online-community-working-group · GitHub](https://github.com/django/online-community-working-group/issues/24)

I would love to see this happen in an automated fashion. Also perhaps a DEP sub category inside Django Internals?

---

<div class="post-metadata">

**Author:** ![CodenameTim](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/codenametim/32/31507_2.png) [@CodenameTim](https://forum.djangoproject.com/u/CodenameTim)\
**Post date:** [October 14, 2026, 2:52pm UTC](https://forum.djangoproject.com/t/where-is-the-dep-discussion/46183/4 "2026-10-14T14:52:51Z")

</div>

> [@nanorepublica](#):
>
> I would love to see this happen in an automated fashion.

Get out of my mind. 😁

---

<div class="post-metadata">

**Author:** ![villager](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/villager/32/24305_2.png) [@villager](https://forum.djangoproject.com/u/villager)\
**Post date:** [October 15, 2026, 5:45am UTC](https://forum.djangoproject.com/t/where-is-the-dep-discussion/46183/5 "2026-10-15T05:45:41Z")

</div>

> [@CodenameTim](#):
>
> Would you be willing to do the leg work for getting the existing DEPs up to date?

Certainly! Brainstorming what that would involve:

- Open Pull Requests to accepted, finalized and rejected DEPs with any existing discussion on the Forum I can find.
- Open Issues to draft DEPs that are missing discussion, asking the author to create and link a discussion.
- Comment on DEPs still in Pull Request that are missing discussion, asking the author to create and link a discussion.

Anything I missed?

---

<div class="post-metadata">

**Author:** ![villager](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/villager/32/24305_2.png) [@villager](https://forum.djangoproject.com/u/villager)\
**Post date:** [October 15, 2026, 5:49am UTC](https://forum.djangoproject.com/t/where-is-the-dep-discussion/46183/6 "2026-10-15T05:49:39Z")

</div>

First step is probably opening a Pull Request to add `Discussion-To` to the [DEP Metadata required fields](https://github.com/django/deps/blob/main/final/0001-dep-process.rst#dep-metadata).

---

<div class="post-metadata">

**Author:** ![nanorepublica](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/nanorepublica/32/14211_2.png) [@nanorepublica](https://forum.djangoproject.com/u/nanorepublica)\
**Post date:** [October 15, 2026, 11:23am UTC](https://forum.djangoproject.com/t/where-is-the-dep-discussion/46183/7 "2026-10-15T11:23:17Z")

</div>

This looks good.

I wonder if we could get some Github Actions setup to automate the creation of forum topics?

We could also perhaps auto create a Discord channel as well (this might become too noisy though)

---

<div class="post-metadata">

**Author:** ![CodenameTim](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/codenametim/32/31507_2.png) [@CodenameTim](https://forum.djangoproject.com/u/CodenameTim)\
**Post date:** [October 17, 2026, 5:35pm UTC](https://forum.djangoproject.com/t/where-is-the-dep-discussion/46183/8 "2026-10-17T17:35:38Z")

</div>

> [@villager](#):
>
> - Open Issues to draft DEPs that are missing discussion, asking the author to create and link a discussion.
> - Comment on DEPs still in Pull Request that are missing discussion, asking the author to create and link a discussion.

I don’t see any harm in you creating the threads for them if you’re willing to do it. Maybe tag them on the post so they get notifications? I think that’d be more efficient and shouldn’t step on toes.

---

<div class="post-metadata">

**Author:** ![villager](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/villager/32/24305_2.png) [@villager](https://forum.djangoproject.com/u/villager)\
**Post date:** [October 28, 2026, 2:23pm UTC](https://forum.djangoproject.com/t/where-is-the-dep-discussion/46183/9 "2026-10-28T14:23:24Z")

</div>

I like it!

I’ve begun by opening an [issue in the DEPs repo](https://github.com/django/deps/issues/125), to get a bit of clarity on what I open my PR against.

As well as suggesting a DEP sub category in the [OCWG repo](https://github.com/django/online-community-working-group/issues/41).
