# Proposal: ability to add entire organizations (ecosystems) with a single command

**URL:** <https://discourse.julialang.org/t/proposal-ability-to-add-entire-organizations-ecosystems-with-a-single-command/103531>\
**Category:** Package Management\
**Created:** [September 5, 2023, 5:33am UTC](https://discourse.julialang.org/t/proposal-ability-to-add-entire-organizations-ecosystems-with-a-single-command/103531 "2023-09-05T05:33:48Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![ParadaCarleton](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/paradacarleton/32/20005_2.png) [@ParadaCarleton](https://discourse.julialang.org/u/ParadaCarleton)\
**Post date:** [September 8, 2023, 5:30pm UTC](https://discourse.julialang.org/t/proposal-ability-to-add-entire-organizations-ecosystems-with-a-single-command/103531/21 "2023-09-08T17:30:16Z")

</div>

Another way to solve this problem, which I think would be less error-prone: Git submodules or subtrees! If it was easy to add packages in subtrees to the registry automatically, and subtrees were treated as subpackages, I think we’d see a lot more meta-packages popping up.

A major problem with adding a whole organization’s packages at once is that something like `import JuliaStats` would probably take a long time importing unnecessary packages.

[Previous page](https://discourse.julialang.org/t/proposal-ability-to-add-entire-organizations-ecosystems-with-a-single-command/103531.md?page=1)