# Package subtopic

**URL:** <https://discourse.julialang.org/t/package-subtopic/55871>\
**Category:** Meta Discussion\
**Tags:** packages\
**Created:** [February 23, 2021, 6:13pm UTC](https://discourse.julialang.org/t/package-subtopic/55871 "2021-02-23T18:13:13Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![airpmb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/airpmb/32/7826_2.png) [@airpmb](https://discourse.julialang.org/u/airpmb)\
**Post date:** [February 23, 2021, 6:13pm UTC](https://discourse.julialang.org/t/package-subtopic/55871/1 "2021-02-23T18:13:13Z")

</div>

Any reason there isn’t a subtopic under Tooling (or maybe Usage) specifically for package management (Pkg, registry, etc.)?

---

<div class="post-metadata">

**Author:** ![dilumaluthge](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dilumaluthge/32/29283_2.png) [@dilumaluthge](https://discourse.julialang.org/u/dilumaluthge)\
**Post date:** [February 23, 2021, 8:25pm UTC](https://discourse.julialang.org/t/package-subtopic/55871/2 "2021-02-23T20:25:23Z")

</div>

Sounds like a good idea to me.

---

<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:** [February 23, 2021, 8:37pm UTC](https://discourse.julialang.org/t/package-subtopic/55871/3 "2021-02-23T20:37:03Z")

</div>

Sure, we could create that. Could you come up with the category “brief”? What should go there, what’s it about, etc.

---

<div class="post-metadata">

**Author:** ![airpmb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/airpmb/32/7826_2.png) [@airpmb](https://discourse.julialang.org/u/airpmb)\
**Post date:** [February 23, 2021, 9:12pm UTC](https://discourse.julialang.org/t/package-subtopic/55871/4 "2021-02-23T21:12:11Z")

</div>

Sure: Any questions and discussions specifically about the package manager, the registry, processes related to these, and so on. The package ecosystem being such a central piece of the healthy growth of Julia, it seems to me this merits a distinct place on Discourse just like e.g. VS Code or Pluto.

Also I’d hope it would encourage more such discussion to be here instead of Slack, where the slackhole ‘event horizon’ is apparently less than 2 weeks behind us:

![image](https://global.discourse-cdn.com/julialang/original/3X/9/4/940a45748edd9762022be15bdb7ca58759c3bda7.png)

---

<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:** [February 23, 2021, 9:17pm UTC](https://discourse.julialang.org/t/package-subtopic/55871/5 "2021-02-23T21:17:55Z")

</div>

I’m specifically after what goes in the initially pinned topic for the category. Here’s the placeholder prompt:

> (Replace this first paragraph with a brief description of your new category. This guidance will appear in the category selection area, so try to keep it below 200 characters. **Until you edit this description or create topics, this category won’t appear on the categories page.** )
> 
> Use the following paragraphs for a longer description, or to establish category guidelines or rules:
> 
> - Why should people use this category? What is it for?
> - How exactly is this different than the other categories we already have?
> - What should topics in this category generally contain?
> - Do we need this category? Can we merge with another category, or subcategory?

Also what should the exact category name be? Tooling → Packages? Or Package Management? Are there some topics off the top of your head that should get moved there?

---

<div class="post-metadata">

**Author:** ![airpmb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/airpmb/32/7826_2.png) [@airpmb](https://discourse.julialang.org/u/airpmb)\
**Post date:** [February 23, 2021, 9:31pm UTC](https://discourse.julialang.org/t/package-subtopic/55871/6 "2021-02-23T21:31:42Z")

</div>

So like this then? [About the VS Code category](https://discourse.julialang.org/t/about-the-vs-code-category/9673)

j/k… I’ll put something together. To be clear I’m suggesting a subcategory of Tooling as opposed to a top level category.

---

<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:** [February 23, 2021, 9:40pm UTC](https://discourse.julialang.org/t/package-subtopic/55871/7 "2021-02-23T21:40:41Z")

</div>

Hahah, yeah, that’s what I want to prevent. 🙂

Thank you!

---

<div class="post-metadata">

**Author:** ![airpmb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/airpmb/32/7826_2.png) [@airpmb](https://discourse.julialang.org/u/airpmb)\
**Post date:** [February 23, 2021, 9:55pm UTC](https://discourse.julialang.org/t/package-subtopic/55871/8 "2021-02-23T21:55:28Z")

</div>

* * *

Questions, comments, suggestions and other discussion concerning package management in Julia. This can include discussion of Julia’s package manager [Pkg.jl](https://julialang.github.io/Pkg.jl/v1/) itself, about package registries, processes around registration, and so on.

To be clear it’s _not_ a place to start a new topic about a specific package unless the topic is mainly around packaging itself as opposed to usage of said package. The exception of course is Pkg.jl, and perhaps others concerned primarily with packaging such as PkgTemplates.jl.

\<placeholder to put packaging FAQ’s and pointers to the most important packaging related docs\>

* * *

> - Do we need this category? Can we merge with another category, or subcategory?

I think so – I don’t think any existing subcategories cover it and the most appropriate place would be under Tooling without a subcategory, and with the ‘pkg’ label. But I think that might be not so discoverable and labels aren’t used consistently.

> Also what should the exact category name be? Tooling → Packages? Or Package Management?

Tooling → Package Management is better, I think. Tooling → Packages sounds like a clearinghouse for questions about any random package.

> Are there some topics off the top of your head that should get moved there?

I think most things with a pkg tag would belong:

[https://discourse.julialang.org/tag/pkg/l/top](https://discourse.julialang.org/tag/pkg/l/top)

---

<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:** [February 23, 2021, 9:58pm UTC](https://discourse.julialang.org/t/package-subtopic/55871/9 "2021-02-23T21:58:48Z")

</div>

That’s perfect. I’ll create it later this evening or tomorrow if nobody beats me to it.

---

<div class="post-metadata">

**Author:** ![dilumaluthge](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dilumaluthge/32/29283_2.png) [@dilumaluthge](https://discourse.julialang.org/u/dilumaluthge)\
**Post date:** [February 23, 2021, 10:12pm UTC](https://discourse.julialang.org/t/package-subtopic/55871/10 "2021-02-23T22:12:53Z")

</div>

Should we also fix the description for the VS Code category?

---

<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:** [February 24, 2021, 10:31pm UTC](https://discourse.julialang.org/t/package-subtopic/55871/11 "2021-02-24T22:31:28Z")

</div>

Done!

> **[Package Management](https://discourse.julialang.org/c/tools/pkg/59)**
>
> Questions, comments, suggestions and other discussion concerning package management in Julia. This can include discussion of Julia’s package manager Pkg.jl itself, about package registries, processes around registration, and so on.

And, yes, let’s fix any others, too. ~~How about I make them wikis?~~ VS Code is already is a wiki!