{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihnjthhfe6i4eatkax2472uvm5xuvbeep6pw4u3n7osvvnsdwt54i",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mffw3zxryzx2"
  },
  "path": "/t/child-thread-survey-of-registry-namespace-designs-for-cargo-and-crates-io/24030#post_4",
  "publishedAt": "2026-02-21T09:50:28.000Z",
  "site": "https://internals.rust-lang.org",
  "tags": [
    "Child Thread: Survey of organizational ownership designs for Cargo and Crates.io - #2 by kornel"
  ],
  "textContent": "You have hit on an important point (both here and in the other thread at Child Thread: Survey of organizational ownership designs for Cargo and Crates.io - #2 by kornel): the real world is messy, and simple hierarchical designs rarely work.\n\nPerhaps it would be better to _not_ go down the route of hierarchical namespaces or ownership at all. Tag systems tend to be more flexible and reflect reality better. I don't know what such a design would look like in detail for this case (tag based namespacing sounds... difficult), but perhaps it is something worth thinking over.",
  "title": "Child Thread: Survey of registry namespace designs for Cargo and Crates.io"
}