TLDR I think it might be time to have a webpage like crates.io or npmjs.com where we could list packages and start supporting a healthy ecosystem to remove the concept that everything needs to go into core. Help?
--- A stated value in some communities (node specifically) is that core should be minimal in order to promote a healthy ecosystem of solutions to problems. For my money, the monolithic model is one thing I was trying to get away from other rtos projects, and I think dependency management is THE superpower of the newt tool, but I feel like were starting to fall into the monolithic trap with mynewt core. We've got an almost unreasonable amount of bsps (especially for nordic platforms) in core, and of note, we recently we seem to have merged competing debounce packages in two different locations `hw/drivers/debounce` and most recently `util/debounce`. It doesnt surprise me that there are two takes on debouncing, or bsps or drivers. These are exactly the kind of opinionated implementation specific solutions where tastes will differ and we should support that. In my mind the It seems like this isnt happening yet, possibly because upstream is seen as the only place to have your code seen and therefore be validated for your contribution. Id like to hear any and all solutions, but one possible way to solve this would be to have some kind of webpage ala crates.io or npmjs.com where we could list packages. Maybe even example projects, tutorials, etc and see dependency graphs. Does anyone agree? If so does anyone have capacity to help? I feel like it might be smart to do the backend in golang, since well presumably want to ingest pkg.yml from git repos we already have a nice codebase that does that.
