# About the Committers category

**URL:** <https://discuss.python.org/t/about-the-committers-category/19>\
**Category:** Committers\
**Created:** [September 28, 2018, 7:29pm UTC](https://discuss.python.org/t/about-the-committers-category/19 "2018-09-28T19:29:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ambv](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ambv/32/25884_2.png) [@ambv](https://discuss.python.org/u/ambv)\
**Post date:** [September 28, 2018, 7:29pm UTC](https://discuss.python.org/t/about-the-committers-category/19/1 "2018-09-28T19:29:13Z")

</div>

The “argument clinic” for Python committers (people with the commit bit on [GitHub - python/cpython: The Python programming language](https://github.com/python/cpython) and related projects). Open for all to view.

Use this category for things you’d use the old [python-committers](https://mail.python.org/pipermail/python-committers/) and [python-dev](https://mail.python.org/pipermail/python-dev/) mailing lists:

- nominating new committers
- announcing new PEPs
- complaining about commits that broke something
- discussing release management
- discussing infrastructure changes that affect other committers
- discussing technical topics related to CPython that shouldn’t be a bug tracker issue

If you’re a committer but Discourse doesn’t know it yet, go to [Python core developers - Discussions on Python.org](https://discuss.python.org/groups/committers) and request access.

If you’re not a committer, you can use the #Python Help and #Ideas categories.

---

<div class="post-metadata">

**Author:** ![vstinner](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/vstinner/32/15130_2.png) [@vstinner](https://discuss.python.org/u/vstinner)\
**Post date:** [October 22, 2018, 8:52am UTC](https://discuss.python.org/t/about-the-committers-category/19/2 "2018-10-22T08:52:00Z")

</div>

I don’t understand if the Committers category is open to everybody or reserved to core developers. Once you write that you write “people with the commit bit” but then “Use this category for things you’d use the old [python-committers](https://mail.python.org/pipermail/python-committers/) and [python-dev](https://mail.python.org/pipermail/python-dev/) mailing lists”. python-dev is open to everyone and I would like to see a new category which would directly replace python-dev. Would it be possible to create a new “python-dev” category? (Or try to find a better name?) For me, python-ideas and python-dev are very different mailing lists. ideas is more to discuss design, dev is more to discuss the implementation.

“python-dev” is the list to discuss the implementation of CPython. Maybe call it “CPython implementation” to make it very explicit?

---

<div class="post-metadata">

**Author:** ![brettcannon](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/brettcannon/32/34895_2.png) [@brettcannon](https://discuss.python.org/u/brettcannon)\
**Post date:** [October 22, 2018, 8:12pm UTC](https://discuss.python.org/t/about-the-committers-category/19/3 "2018-10-22T20:12:05Z")

</div>

> [@vstinner](#):
>
> I don’t understand if the Committers category is open to everybody or reserved to core developers.

Anyone can read, only core devs can write.

---

<div class="post-metadata">

**Author:** ![ambv](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ambv/32/25884_2.png) [@ambv](https://discuss.python.org/u/ambv)\
**Post date:** [October 22, 2018, 8:37pm UTC](https://discuss.python.org/t/about-the-committers-category/19/4 "2018-10-22T20:37:56Z")

</div>

My feeling is that anything that should involve Users, including PEP discussions and other things related to CPython should happen in the Users category. I don’t see a point of creating a python-dev equivalent. When we end up needing sub-categories and tags there to make sure we can find the core-related things easier, we will do it then.

I think it’s rather beautiful to have design discussions and so on in the users space. With “python-dev” I always felt it’s like users are a second-class member of this mailing list. Let’s not try to replicate that here.

Since we all have the same accounts for the entirety of the Discourse installation, if any user notices a discussion happening on Committers that they can’t contribute to, they can let us know to move it if it’s better placed in Users. It’s now easier than ever for the community to follow committer discussions.

---

<div class="post-metadata">

**Author:** ![vstinner](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/vstinner/32/15130_2.png) [@vstinner](https://discuss.python.org/u/vstinner)\
**Post date:** [October 22, 2018, 8:40pm UTC](https://discuss.python.org/t/about-the-committers-category/19/5 "2018-10-22T20:40:44Z")

</div>

> [@ambv](#):
>
> I don’t see a point of creating a python-dev equivalent.With “python-dev” I always felt it’s like users are a second-class member of this mailing list. Let’s not try to replicate that here.

I am more interested by discussions on the implementation rather than on the design. So I am no longer subscribed to python-ideas. I unsubscribed because there was too much traffic and I was unable to follow it. I would prefer to have on category for design and one for implementation, to be able to follow discussions.
