SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The "get Slack" still mentions 'slackware store', although with a broken link. Besides, the news page could mention Slackware funding so that more users would know about it.
The "get Slack" still mentions 'slackware store', although with a broken link. Besides, the news page could mention Slackware funding so that more users would know about it.
True, but these things have been raised a number of times in the past, so I wouldn't expect much to change I'm afraid.
I agree! The website's backend needs a complete overhaul from my understanding and the one done before for some reason wasn't adopted by our BDFL. Hopefully this issue is rectified before the release of Slackware 15!
Perhaps somebody who wants to contribute to Slackware, has web development skills, and lacks funds to donate could revamp the site? Throw together a new layout and then quietly contact Pat. If he likes the effort he can wget spider the pages to the web site and add a tagline or colophon acknowledging the designer.
Don't use JavaSh_it and keep the same background -- throwing that out probably would irritate many long time Slackers.
I think that only Pat or his helpers can edit Slackware.com.
As far as I know the website was setup originally by the Walnut Creek people (which devolved into the Slackware Store) and not even Pat can maintain it (except for trivial changes like some texts.
As far as I know the website was setup originally by the Walnut Creek people (which devolved into the Slackware Store) and not even Pat can maintain it (except for trivial chsnges like some texts.
But according to whois the domain slackware.com is owned by PV personally so he could easily move the physical location of the site, change the look etc. If he wants to of course...
However, a newcomer to Slackware may have a hard time figuring things out, since information is quite scattered.
The layout doesn't bother me too much, but the website as it stands definitely gives the casual browser an impression that Slackware is finished. Last news release in 2016, and a bunch of completely out of date things. For example, statements like "The site is designed to be viewed with at least a 640x480 display", support links like this and this (and perhaps other defunct businesses being listed), a link to freshmeat.net (an old site which since changed to Freecode and shut down in 2014), various references and links to the dreaded Slackware store, a link to Slack S/390, badly outdated FAQ section, etc etc. One would have to look at the changelog to know that it's still an active project!
Discussions of the design aside, it's hard to argue that the content of the site is doing Slackware any good as a project. No doubt there's plenty of people around willing to help, but the website appears to be in full zombie mode for whatever reason. That's unfortunate since it creates an impression contrary to the distribution itself, which is still rolling and works great.
As far as I know the website was setup originally by the Walnut Creek people (which devolved into the Slackware Store) and not even Pat can maintain it (except for trivial changes like some texts.
That can't be right. I remember news about the website's codebase being updated just a few years ago. Previously, it had required an older version of Slackware to serve it.
That can't be right. I remember news about the website's codebase being updated just a few years ago. Previously, it had required an older version of Slackware to serve it.
That was in 2012, more than just "a few" years ago (about the same year Slackware 14.0 was released). Lots has happened since then, the versions they used then are probably longtime unsupported (and superceded). I.e. php was still at version 5.4 then.
PHP is needed for the stable and current ChangeLogs, though I suppose nowadays that can be replaced with just straight links to the ChangeLog.txt files from a mirror. It is also used for the security advisories.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.