Split Registries management to a separate repository

[AntoineDao]

@mostaphaRoudsari brought this up briefly during a call but did not have time to explain his thoughts fully. Would you mind explaining in a bit more detail what your thinking was here so we can keep track of this development proposal?

[mostaphaRoudsari]

From showing and explaining queenbee to a handful number of people I felt it will be helpful to separate the package manager functionalities from the queenbee schemas. The package manager part will provide functionalities to package, pull, ... the Queenbee recipes and plugins while Queenbee provides the functionalities for writing the recipes, plugins and plugin functions.

Maybe we can call it Beehive or Queenbee package manager -> qpm!

[AntoineDao]

I like the idea. It would provide a nice abstraction to work from also. Are we ok parking this issue for now and you or I can sift through the codebase to figure out how straightforward it will be to extract this stuff?

PS: I really want to call it Beehive but Queenbee Package Manager is probably more sensible... 🙃

[mostaphaRoudsari]

Are we ok parking this issue for now and you or I can sift through the codebase to figure out how straightforward it will be to extract this stuff?

I would say so. Let's do it after the early access. I think it is nice to have but it is not critical right now.

The functionalities are almost separate so it shouldn't be that hard to separate them into its own package.