3 ms·

Sounds like the distro problem. Yes, a lean, mean, linux machine is great, but when you have to hunt around for all the tools you want, it becomes a pain to man

Sounds like the distro problem. Yes, a lean, mean, linux machine is great, but when you have to hunt around for all the tools you want, it becomes a pain to manage. Far nicer to have a curated set of tools that most people can agree upon. In this case, mjolnir, the lean mean core, then the various subprojects, and finally the "distro", containing a curated set of popular modules that people can download as a turnkey system. Then, if you want your own custom setup, minus the bloat, you can set up your own distro. If you just want to use the damn thing and don't care about how the sausage is made, use the "recommended" distro.

kstenerud 10y ago
To elaborate: Have a centralized repository containing pointers to all available modules. Module creators can publish to this repository. Cocoapods does this rather nicely, and uses github for the centralized repo. Then have a tool inside mjolnir that allows administration of the repo (request adding your module, publish a new version of your module, etc). Then have a "distro" format that lists what modules are included in your distro. This is doubly cool because if you have to install another machine, you just call upon your distro, it installs everything and you're good to go. It also makes upgrading to the latest and greatest modules a breeze. I guarantee that 90% of your users will just go with the "recommended" distro, but the developers will love you for making it a lot easier to contribute. It's all about lowering friction, for users, power users, and devs.