Hi,

The 'Slackware-Links' wiki discussion should be reviewed and used.

I think that a 'Slackware-IRC Links-Wiki' should be created to provide the means of a channel list. I don't use the 'IRC' so the creation and maintenance would have to be done by someone else. If I understand the IRC idea then the LQ forum would surpass.

I think the LQ forums provide a means to information/answers and general discussion about GNU/LINUX/Slackware. Also a good archival reference to any posts.

I don't look at the 'Slackware-Links' as a link dump. If others feel it as such then so be it. The intent originally was to provide for the GNU/Linux Slackware community a list of links. Slackware falls within that community. Everyone's taste varies and it is hard to satisfy all. I take the criticism constructively and welcome the discussion.

As for the warning for the page length. The message is posted because of the possibility of the user's browser being either 'Netscape or Opera', with versions that don't handle the pages properly. The user should upgrade to a known good or real browser.

For the commenting of links. I think the link should provide as much detail as possible yet remain simple and short. The expansion comment can provide more information but that too should be limited not verbose. Short and definitive. We're not constructing a HOWTO.

BTW, I do this to assist the community and I do have other things to do throughout the day. The community participation is welcome! I think a reconstruction can be done in parallel without interruption.

I'm not flaming anyone! Just responding to the suggestions. Thanks to all the suggesters.

I've just done some minor cleanup, and I've got some ideas floating around in my head for a more thorough cleanup, but I don't want to step on too many toes in the process...

As an example, I think the section on LiveCD's is a bit too verbose - why do we link to non-Slackware-derived livecd images? I'm also not entirely sure I like the idea of linking to external projects (such as samba) when they're included in Slackware -- I think that creates the risk of a new user (not knowing any better) trying to compile it from source and creating conflicts between what they compile and what's shipped in Slackware.

Also, why do we need to link individual mirrors? All official mirrors are listed at slackware.com, and alphageek has an unofficial list that he maintains (which we can add to the wiki) - that will shorten the Mirror section to two links while still providing the same information...

Linking to offsite mirror lists sounds like a big time saver and makes a lot of sense to me. If we have long lists of mirrors on the wiki, someone will have to check they still work and update them. Simply linking to existing links cuts down on the number of broken links you have to patrol. Why do work if someone else will do it for you?

Yeah, that's what I'm talking about. I'm not saying it's a link dump ... those are far worse. Also, I agree that the description should be small, and yet long enough to give the surfer an idea of what's up ahead should they choose this path. If this is not done, the surfer will need to do much more surfing and reading trying to figure out what a particular link is about, then they may just give up. It's a delicate balance ... too much wording and the surfer will stop reading and move on to somewhere else, too few words and the surfer will have to do extra surfing and reading to find out what a link is about. Thus, there should be just enough to convey what awaits the surfer upon clicking a link. Ahhh ... much philosophy about nothing.

Anyway, I also understand that you (onebuck) are busy and can't maintain it full time. I can tell you that you are not alone (but you probably already know that).

How about a contents list at the top of the page? By which I mean a list of sections. That will save the visitor some scrolling.

Hi,

Any help is greatly appreciated. No toes being stepped on that I know of.

My basic reasoning for the 'Slackware LQ Suggestions Links!' which is now 'Slackware-Links' was to provide links for GNU/LINUX Slackware to possible tools that a user would find useful. Not just Slackware specific. I use all available tools when trouble shooting therefore the Livecd list is from my experiences. I do see the possibility of a problem for a new user. But do we have to be spoon feeding pablum all the time? A user should be able to see and make some decisions for themselves.

I agree that would shorten the page. Not everyone will look at the Slackware.com for mirrors. Some of the listed mirrors I found exceptional and that's why the inclusion. I like the idea of including the suggested links. That way there's less work.

BTW, robby I do appreciate the time you have given to Slackware and to the LQ community. I know your time is as valuable as anyone. So thanks! I look forward to any assistance, recommendations or constructive criticism. That's the Slackware way from my viewpoint.

Hi,

I think the openness of the discussion is valuable.

Yes, the commenting must be a balance and a wise choice of wording to keep the viewer/user from having to much information to absorb or discern. Look forward to the assistance!


Yes, we all are pretty busy. Yet, I do seem to find time to get things done. Slowly I turn...

I like to give back to the community as much as possible. It seems things always work out to the best.

I hope I'm conveying my ideas to everyone. Meaning I don't take the criticism personally. I really want the 'Slackware-Links' to be a service to the GNU/Linux Slackware community. I just can't do it alone.

Hi,

One of many in the TO-DO. The TOC is there but I do believe a list of the sections could expand for better understanding.