# \[Pre-RFC\]: Packages as Namespaces

**URL:** <https://internals.rust-lang.org/t/pre-rfc-packages-as-namespaces/8628>\
**Category:** cargo\
**Created:** [October 19, 2018, 11:32pm UTC](https://internals.rust-lang.org/t/pre-rfc-packages-as-namespaces/8628 "2018-10-19T23:32:31Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![sgrif](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/sgrif/32/3339_2.png) [@sgrif](https://internals.rust-lang.org/u/sgrif)\
**Post date:** [October 20, 2018, 8:17pm UTC](https://internals.rust-lang.org/t/pre-rfc-packages-as-namespaces/8628/7 "2018-10-20T20:17:36Z")

</div>

> [@kornel](#):
>
> but can also mean "works with the `project` ".

This is my personal opinion. It should not be taken as a statement from the [crates.io](http://crates.io/) team, nor does it imply that anybody else on the team shares my opinion.

I think that's the _significantly_ more common case. Often it's both. `diesel-migrations` happens to be maintained by the Diesel project, but the more important property is "it's an implementation of database migrations for Diesel". Try searching for `chrono-` or `tokio-` or `diesel-` in the [crates.io](http://crates.io) search. All the top results are things that integrate with or add new behaviors to those projects, and are not maintained by the owner of the main project. (Note: I am not trying to present this as evidence that this is the most common case. This obviously has sampling bias. However I think those are some really good examples of the kinds of crates I'm referring to)

I would like to re-iterate that these are my personal opinions, and I am not speaking on behalf of the team.

---

_[View the full topic](https://internals.rust-lang.org/t/pre-rfc-packages-as-namespaces/8628)._