Namespacing about supermarket HOT 2 CLOSED

This has larger ramifications than just the community site. Berkshelf and librarian, for example. I think the idea that the cookbook itself should be canonically named after the metadata is an obvious win, and one I know folks are looking to have enforced in Chef 12.

That would, at least, get you the ability to have repositories or cookbook paths that are divorced from the cookbook name itself. Then you would need to change the actual Supermarket implementation. That's without talking about whether namespaces help or hurt - plenty of counter arguments abound in both directions.

One of the things that bums me out the most is that we can't actually improve the code we have deployed today - it's a complete dead end.

I know one use case for having private copies of Supermarket is to rely preciesly on the single namespace - so that an organization could have a local copy with a canonical repo. Don't think that invalidates the namespace request, but its interesting to think about.

from supermarket.

I am closing out this issue as part of some housekeeping. But first, a couple of thoughts and notes:

• I have a discussion label so we can revisit this at some point in the future.
• There really is no right answer here. Both sides have valid points. The question becomes, for me anyway, if we make the switch, is there a high enough likelyhood that we are going to gain the wins we expect to get to warrant the massive amount of pain involved in making the change?
• Because I think it is useful to state biases in conversations like this, I am personally opposed to this change.

Finally, thank you to everyone for the discussion. Starting and participating in these discussions in a constructive manner is time consuming and involved, so thank you.

from supermarket.