# Where should Julia feature requests go?

**URL:** <https://discourse.julialang.org/t/where-should-julia-feature-requests-go/102835>\
**Category:** Internals & Design\
**Tags:** github, discourse, feature-request\
**Created:** [August 15, 2023, 3:45pm UTC](https://discourse.julialang.org/t/where-should-julia-feature-requests-go/102835 "2023-08-15T15:45:09Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![mbauman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbauman/32/31082_2.png) [@mbauman](https://discourse.julialang.org/u/mbauman)\
**Post date:** [August 16, 2023, 4:29pm UTC](https://discourse.julialang.org/t/where-should-julia-feature-requests-go/102835/19 "2023-08-16T16:29:40Z")

</div>

> [@Sukera](#):
>
> In other communities, it is usually custom to open an issue for discussion first.

Perhaps so with smaller projects and libraries, but as `@jariji` [showed](https://github.com/JuliaLang/julia/pull/50881#issuecomment-1675462935) it’s quite a mix. With larger projects, I’ve found that I always have to acquaint myself with the norms of every different community before being able to post appropriately.

- Rust: pushes feature requests to discourse in their new-issue form, but uses [the enhancement label](https://github.com/rust-lang/rust/labels/C-enhancement) for targeted feature-y issues
- Go: uses issues, but with a [structured process](https://go.dev/s/proposal-process) to close many
- CPython: pushes feature requests to discourse, but allows using issues after a discourse discussion that shows support

Additionally:

- Numpy: asks for **both** a discourse thread and an issue simultaneously
- Scipy: uses issues

It’s a mix — and in my view, I think this is very reflective of the blurry lines and wide variety in feature requests. There’s a distinction between _explicitly inviting_ feature requests as issues and using issues for some feature requests.

---

_[View the full topic](https://discourse.julialang.org/t/where-should-julia-feature-requests-go/102835)._