[Slashcode-general] I volunteer to help resuscitate Slashcode

[Eric D. <eri...@ja...>]

If you search through the archives, you'd see I was a regular poster
on this list.....when it lived. Honestly, this little discussion is
probably the most traffic the list has seen in half a decade.

>From what I remember, the slash code guys basically gave the
impression that they were never going to put together another tar ball
release (and I dont think they ever have) and as for updates for the
community......good luck.

So, that is when I decided to leave and finally spent one weekend and
came up with SQL scripts to convert my stories and users to word
press.

Protest? No. I'd rather think myself as a person warning others that
slash code is a dead end. That when I switched to word press, I had
joined a vibrant community where there were plugins. Documentation on
the codebase. Upgrades that were easy. Themes. Easy customizations.
Etc. And the performance on my server was as good if not better than
before. Compare that to slash code. There is no community. The slash
code site was last updated.....2009? and before that there was a post
in 2008......And the last post on slash code was basically saying we
aren't supporting it, but here is where you can get the code. Good
luck.

I think I'd rather take my chances with php and word press cause there
are more than about 10 people who use it....


On Friday, February 4, 2011, George Taft <geo...@gm...> wrote:
> Eric -- I appreciate your frustration with Slashcode. Perhaps like
> Scott you had forgotten the list existed. Nevertheless, you responded
> to my initial post, not once but four times.
>
> I guess my only question to you would be, why reply unless you still
> cared? Methinks you protest too much. If you're a coder, a new effort
> to revive the project might be able to use your help. == George
>
> On Fri, Feb 4, 2011 at 12:10 AM, Eric Dannewitz <eri...@ja...> wrote:
>> Reason why I ditched slashcode was that it was never updated, and it was
>> never documented. The upgrade paths from the builds was a nightmare. Stuff
>> would work, then not.
>> Migrating to wordpress has resulted in a faster site, and I can take
>> advantage of a huge supply of plugins and interest in the platform. And the
>> upgrade path to new versions is well documented and easy
>> There isn't anything remotely like with slashcode. Ever. Since 98 or
>> whenever. It was a pain until 2008 when I decided to figure out how to
>> migrate my stuff to wordpress.
>>
>> Sent from my iSomething
>> On Feb 3, 2011, at 9:03 PM, Clifton Wood <cli...@gm...> wrote:
>>
>> The problem here is that we'd spend more time making Drupal into Slashcode
>> than making a better Slashcode.
>> - Cliff
>>
>> On Thu, Feb 3, 2011 at 10:28 PM, T. J. Brumfield <end...@gm...>
>> wrote:
>>>
>>> There are some Drupal modules that were started to add Slashcode style
>>> features, such as Slashcode moderation.
>>>
>>> http://drupal.org/project/slashcomments
>>>
>>> In a perfect world, I think Slashcode might be better off recreated in
>>> Drupal 7.
>>>
>>> There are far more extensions/modules for it. It is mature, stable, tested
>>> and well used. It would be easier to get support for. I would seriously kill
>>> for a slick, Drupal 7 powered Slashcode of the future.
>>>
>>> On Thu, Feb 3, 2011 at 8:44 PM, A H <hol...@gm...> wrote:
>>>>
>>>> And can Wordpress do moderation points like Slash?
>>>>
>>>> The moderation system was what attracted me to Slash but I had to give
>>>> up on it - too many undocumented "features".
>>>>
>>>> I think it's still a relevant format and I would love to see it
>>>> flourish. My contribution would need to be in documentation because I
>>>> am not a programmer.
>>>>
>>>> -Andrew
>>>>
>>>> On Thu, Feb 3, 2011 at 8:39 PM, Eric Dannewitz <eri...@ja...>
>>>> wrote:
>>>> > I'd ditch slash for wordpress. I did and have never regretted it
>>>> >
>>>> > Sent from my iSomething
>>>> >
>>>> > On Feb 3, 2011, at 4:23 PM, George Taft <geo...@gm...>
>>>> > wrote:
>>>> >
>>>> >> An Open Letter to the Developers of Slashdot, and What's Left of the
>>>> >> Slashcode Community --
>>>> >>
>>>> >> I'm an avid reader of Slashdot. I don't comment much, but I've always
>>>> >> been impressed by Slashdot's moderation system. It manages what should
>>>> >> be an unmanageable task: ensuring a civil discussion among thousands
>>>> >> and thousands of users.
>>>> >>
>>>> >> I've come into a situation where I now need a system much like
>>>> >> Slashdot's: an extensible and scalable readership-moderated online
>>>> >> discussion forum. Lo and behold, Slashdot make Slash open source years
>>>> >> ago. They even got an O'Reilly book.
>>>> >>
>>>> >> But Slashcode was never the priority of the coders. The last official
>>>> >> release is, what, nine years old? There's been much more modern code
>>>> >> released, but even that's a couple of years old. What little traces I
>>>> >> can find of other sites using Slash involve those sites migrating to
>>>> >> something else. This message is evidently the first post on
>>>> >> slashcode-general in almost a year. The coders have written that
>>>> >> management of the open-source branch of the codebase is still not
>>>> >> their priority. And so the userbase has almos