Slashdot Mirror

I'm not saying that I don't agree the docs could be better. But that's nothing new for 99% of all projects, especially opensource, imho. Some of what's in /docs is seemingly ~4 years old. As far as slashcode goes, there've been many people who've complained the docs aren't great.

However, that you _can_ follow the INSTALL instructions and have a working slashcode system, you can't knock that. I guess when you ask "that's the best you can say?" I don't see anything wrong with that.

"lack of a full releass" kills the entire point of Slashdot users working on the Slashcode

Yes, it surely does. And the upgrade process from 2.2.6 to current is well, abysmal. It's do able with some effort (following the documentation), more so obviously if you don't know the project well. The lack of a "slashupgrade.pl" that site admins can run is a turnoff for many people still running 2.2.6. The lack of a current release just plain puts people off from even attempting to run the latest. And even if you are the running the latest, or somewhat the latest, you have to apply updates - by hand. There's no stock-included upgrade tool to go from T_2_5_0_128 to T_2_5_0_133.

Slashdot's complaining programmer user community is a huge pool.

Slashdot's surely is huge. Slashcode's, I don't agree with you there. Just look at the activity (or lackthereof) on the listserves. Slashdot and Slashcode are two different things. Which is kind of sad, because you'd think with the pool of talent Slashdot itself attracts there'd be many more people trying to help with Slashcode.

If the Slashdot org encouraged us with better docs, not just silence or the arch, obnoxious attitude you just displayed, more of use would join the team to produce a better Slashcode.

Obnoxious? ha.

The 'silence' is what's frustrating for me. Not knowing where the code is heading is aggravating at times.

And if you think that none of the many programmer users would have noticed the index datatype change in one scope but not the necessary one in another, you don't even understand Slashdot.

Well, no one noticed there could be a problem with that index in the stock code, obviously. The schema for comments wasn't changed for how long? The code's out there, been out in the open source land for years now. There's nothing stopping anyone from grabbing it an analyzing it. I still doubt that any "normal traffic" site would have noticed this limitation. Should someone have caught it? Sure. But most sites don't have the traffic slashdot has, so about the only site that'd ever run into this limitation with the slashcode code is Slashdot itself.

In fact, you've just shown you don't understand how OSS projects work

Oh? Please explain.

though you apparently understand how the OSS code works in this one

I think so, yes, at times, anyway.

Exactly my point. No wonder the Slashcode project is so unpopular, and therefore irrelevant. Which you seem more than happy about - defensive of, even. Congratulations.

Defensive? No. If my comment came off that way, that wasn't my reply's intent.

However, frustrated, yes. Frustrated that people pop into a project, claim "this sucks" but don't give any concrete examples where it sucks. Or, better yet, how about some constructive criticism and pointed suggestions such that if someone were to spend their own time helping trying to help with what's pointed out, the project *could be improved*.

For those of you that don't want to delve into the slashcode stylesheets, but are curious as to how they're done:

Details about SlashCSS layout

There's also quite of slashcode related information at http://slash.lottadot.com/.

For those of you that don't want to delve into the slashcode stylesheets, but are curious as to how they're done:

Details about SlashCSS layout

There's also quite of slashcode related information at http://slash.lottadot.com/.

Here's some details about the slashcss conversion.

I think some of what you're asking about is answered in that.

I decided to make my dreams come true and have my own slashsite. Wanting to migrate my successful GIS / RS mailing list to slash. http://www.matox.com/agisrs

SlashCSS is not "ready yet". I though it would be easy to setup the site, but even with a lot of help from the slash mailing lists and http://www.lottadot.com/ . A few weeks will be required for our launch announcement.

SlashCSS is really a great step in the right direction, however, my advice, if you're planning building a slash site, wait a little while, the whole process will be easier for you.

We chose slash over other CMS http://www.cmsmatrix.org/ mainly because of the great (even if flawed) moderation system.

I was reading the article and had the same thought.

We saw a blurb on TV a few weeks back about the US importing other country's trash (one of them was Japan) into our landfills. It is products like this that seem to perpetuate the situation. They scream that the one-use is OK, and don't worry about where this thing goes after you toss it. After all, it's "just the trash".

> without root access

That's pretty much what the documentation tells you, no?

There are hosting services that'll do Slash for you.

Is that what you want? If so, come out and help create the css-conversion of their stock theme.

Funny that you mention size. Slashdot had, a while back, a story that had a huge number of comments. It was rendering at over 1MB of information to transfer.

So we went and created a css-themed theme for
slashcode.

Here's the size differences:

stock:
shtml page: 410.3 kb
nested: 1.9mb

slashcss:
shtml page: 330030 bytes
nested view: 1008300 bytes

slashstrict:
shtml page: 252.6kb
nested: 983.8kb nested

That's quite a difference!! It's amazing what you can do with CSS.

The NY Times had an article about people bringing their cell phones onto the trail. I threw up a mention of it, check it out here.

I can understand wanting to have it packed away in your gear for emergencies, people just need to turn the ringer off or turn the phone off while they're out.

We did this too. Two years ago we picked up two mountain bikes (one for me, one for my wife) from our tax return.

We've had a blast ever since. We setup a website MTBMadness (slash-based!) to put information online. We take the digital camera with us whenever we go riding, and put the pictures online.

We've since hooked up with local mountain bike groups, as well as state-wide and multi-state, so as to go on group rides.

It's a blast, and it will definitely get you into shape real quick. I still don't like uphill climbs, but the downhill that comes after one makes it all worth it.