Hi list, I'm starting to wonder what the point of the contrib dir in stumpwm actually is. What is the advantage to having this stuff bundled alongside stumpwm?
There are some possible perceived benefits that don't stand up to scrutiny: * Stuff in contrib is kept in sync with the main progam. Blatantly untrue: nobody tests everything in contrib when making changes to stumpwm. * Being in the main repo makes users aware of the contrib software's existence. Debatable: this stuff is not mentioned in the stumpwm manual so I suspect most users find out about stuff that might be useful to them on IRC or the web. What if instead we had a database of stumpwm add-ons that were hosted elsewhere? This could be something as simple as a wiki page or a full-blown system with reviews, comments etc if anybody cared to make it. The authors of the add-ons could maintain their software in their own repos (including non-git repos if they have some strange aversion to git), and users could keep it up to date from there. The packages could use asdf to make it convenient to load them from stumpwmrc. There's some stuff that should probably remain in the main repo: stumpish and stumpwm-mode, stuff that is useful to distributors, utils for use on the stumpwm source, and example RCs. But anything that is strictly an add-on could be hosted elsewhere. Thoughts? Ben _______________________________________________ Stumpwm-devel mailing list Stumpwm-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/stumpwm-devel