Slax author's Blog (RSS)

Slax modules all temporarily enabled

If you didn't notice yet, Slax modules are now all visible. Even the unverified ones. I did that in order to bump some discussion about it. Now you can see what horrible mess is inside. Here are possible next steps:

If there are some volunteers who will help maintaining the modules section, they will have to verify all modules and delete bad ones. Then the modules section will be cleaned, I will hide unverified modules and we can continue this way forever. This requires some smart people to donate their time (a lot of time) and skills (a lot of skills).

If there are no skilled volunteers, I will have to do something on my own. That would be: delete all the unverified modules in the whole repository, disable module uploading, and tell people to submit slackbuilds to slackbuilds.org if they need to add some software to Slax. That would have several advantages.
It would move the 'quality ensurance' to someone else (slackbuilds crew), it would also ensure that all modules can have build scripts available (which is IMHO essential for further maintenance), and finally, it would mean that the effort of the module creator will be usable not only in Slax, but also in Slackware.

Slax modules repository would then consist of three parts:
1) required and suggested modules (001-core, ..., 006-devel)
2) all slackware's official TGZ packages (auto creation is simple)
3) all software from slackbuilds.org, which compiles in Slax

One problem is with icons, because as you can see, every module has small icon and one screenshot. That would need to be created manually, but I guess I could permit that for everybody to upload new screenshots/icons.

Well, what do you think? Do you prefer the current setup with volunteers? Or perhaps a combination of both these methods? This is a RFC (request for comments) so I hope you'll join the discussion :) Thank you.

User comments