# Creating a "python-dev" equivalent category

**URL:** <https://discuss.python.org/t/creating-a-python-dev-equivalent-category/951>\
**Category:** Discourse Feedback\
**Created:** [February 26, 2019, 11:49pm UTC](https://discuss.python.org/t/creating-a-python-dev-equivalent-category/951 "2019-02-26T23:49:00Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![methane](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/methane/32/43_2.png) [@methane](https://discuss.python.org/u/methane)\
**Post date:** [February 28, 2019, 12:11pm UTC](https://discuss.python.org/t/creating-a-python-dev-equivalent-category/951/12 "2019-02-28T12:11:56Z")

</div>

> [@jdemeyer](#):
>
> The thread [Adding char\* based APIs for Unix](https://discuss.python.org/t/adding-char-based-apis-for-unix/916/15) is another example of something that doesn’t belong in committers.

Ah, I’m sorry about it. I thought python-dev is merged into “Committers” category in discourse.  
I searched why I thought so… and find this.

> [@Python-committers is dead, long live discuss.python.org](https://discuss.python.org/t/python-committers-is-dead-long-live-discuss-python-org/30/1):
>
> As you can see, I combined python-committers and python-dev into just “Committers”. If we find in the future that this is too limiting, we can always open up another category. For now though I’d like to avoid the fate of python-dev where there’s 20k+ subscribers and we don’t know who is who.

---

_[View the full topic](https://discuss.python.org/t/creating-a-python-dev-equivalent-category/951)._