Parade du Grotesque

Go to packages.slackware.com or slackbuilds.org and you will see the base system has reasonably up to date packages.

I have no idea what you are talking about. NetBSD is portable. Its performance is very good (it has to be, since it works on stuff like 68040 Amiga and Atari), but probably a bit under FreeBSD, since FreeBSD is mainly focused on Intel and AMD.

Slackware.

It. Just. Works.

I have used all 3 major BSDs (Free, Open and Net). FreeBSD is ideal for servers due to its performance. OpenBSD is perfect for security appliances and NetBSD is perfect if you have exotic legacy hardware.

This being said, I have also used OpenBSD for about two years as my daily driver on an old second hand laptop, and I really liked it. With a minimum of configuration, installing software was as easy as Debian (just your pkg_add), and configuration is just super easy since the OpenBSD documentation.

It has improved a lot done then: installing security updates (sysupdate) and upgrading (sysupgrade) from one version to the next is amazingly simple. If your hardware is supported, OpenBSD is just a pleasure to use. Its only default is the lack of “advanced” file systems and volume managers.

OwnCloud and Yunohost are the two that comes to mind. I will let you Google them.

If it’s several python modules, then yes, choose a license and then contact pypi and see if you can distribute your modules through them.

One very important thing is that you have to make sure everything is ready for distribution: check your project will work (possibly starting with a blank VM), what its dependencies are, that the requirements.txt file is good and operational, that automated tests are available for people to run after installing, etc.

In other words, the ideal project is not just a question of license but also all the scaffoldings you supply with it.

Thanks for opening your code!