# How can we create a leaner ecosystem for Julia?

**URL:** <https://discourse.julialang.org/t/how-can-we-create-a-leaner-ecosystem-for-julia/32904>\
**Category:** Statistics\
**Tags:** package, proposal, time-series, machine-learning\
**Created:** [January 3, 2020, 1:35am UTC](https://discourse.julialang.org/t/how-can-we-create-a-leaner-ecosystem-for-julia/32904 "2020-01-03T01:35:55Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Roger-luo](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/roger-luo/32/3399_2.png) [@Roger-luo](https://discourse.julialang.org/u/Roger-luo)\
**Post date:** [January 3, 2020, 1:51am UTC](https://discourse.julialang.org/t/how-can-we-create-a-leaner-ecosystem-for-julia/32904/3 "2020-01-03T01:51:34Z")

</div>

I’m wondering if we should provide some standard keywords to the Pkg registery like what they do in pip (although `pip` itself might be bad, but I like the keyword idea). To register a package in General the author have to choose at least one keyword, so we can always find all registered packages for a given domain from the project configuration itself instead of a loose github tag (or maybe the package is not hosted on github at all!)

---

_[View the full topic](https://discourse.julialang.org/t/how-can-we-create-a-leaner-ecosystem-for-julia/32904)._
