slashcode-general — This is the general discussion list. Install questions welcome.

Re: [Slashcode-general] Minimum version of every component for a successful Slash install?

[Clifton W. <cli...@gm...>]

"HEAD" means the latest revision published by whatever source code manager
you are using. If Slashcode has moved to git and git is working (last time I
tried, which was 6-10 months ago, git didn't work). I still think I have
that repository, somewhere. If I do, I'll tar it and drop it to you via
email.

- Cliff

On Sun, Feb 6, 2011 at 3:06 PM, George Taft <geo...@gm...> wrote:

> <preface>I want to say against any future critiques: my goal is to be
> a publisher. I want to run a large community discussion. I think the
> moderation system of Slashdot, realized in whatever eventual form, is
> the only one for my purposes.
>
> It should be no surprise that I'm much more of an editor than a coder.
> Ironically, though, the Slashcode community itself is in need of
> reinvigoration, which makes someone like me perhaps more useful at the
> moment than someone who can field-strip a Perl rifle.
>
> Please consider me an enlightened end-user: ignorant of the necessary
> minutiae, but educable. I'm not a developer. I don't yet understand
> certain jargon. I'll need to ask questions that may seem idiotic or
> pedantic to some. I ask your indulgence. (Since the community was all
> but dead a few days ago, what has anyone still here got to lose by
> letting me ask? The trail left by my questions will help and encourage
> others like me.)</preface>
>
> Shane -- Forgive my ignorance. When I go to
> <https://sourceforge.net/projects/slashcode/files/Bundle-Slash>, I see
> "Looking for the latest version? Download Bundle-Slash-2.52.tar.gz
> (2.1 KB)". Then I see the litany of versions prior to 2.52.
>
> I understand packages with version numbers. I don't understand what
> you mean by version "HEAD", the "last SCM-Head," or where to go to
> "get from src." Could you or someone explain?
>
> == George
>
>
> On Sun, Feb 6, 2011 at 1:09 PM, Shane Zatezalo <sh...@lo...> wrote:
> > Distro: CentOS
> > Slash-version: HEAD (from src, never package)
> >
> > Don't use the 2.2.6, it is just *too* ancient to bother with. And the
> upgrade from 2.26 -> SCM-Head was just brutal. Work from the last SCM-Head.
> >
> > If I recall I'd start off buy getting perl, mod_perl and apache compiled
> togther and functionally running.
> > While I was doing that, I'd (in another term window) install mySQL (and
> in another window) start installing CPAN modules (follow the
> cpan-instructions from slash-HEAD by the book).
> >
> > Once all that was done, I could make install and then 'install-slashsite'
> at will.
> >
> > On Feb 6, 2011, at 7:51 AM, George Taft wrote:
> >
> >> [...] let me ask those who are
> >> still here:
> >>
> >> The last time you successfully installed Slashcode so that it was up
> >> and fully functional, what distro did you use, and what versions of
> >> Perl, MySQL, Apache and...well, Slash? Was it actually 2.2.6, or was
> >> it something from the repo?
> >>
> >> For starters, I can tell you that on my second effort, it was Fedora
> >> 14, Perl 5.12.3,  MySQL 5.something, Apache 1.3.42, and Slash 2.52.
> >> Anyone see any red flags?
> >>
> >> We shouldn't expect anyone to want to use or support Slashcode when
> >> the documentation to install it is half-missing. I'd like to figure
> >> out what the latest of everything that work together for any given
> >> Linux distro. I volunteer to write that documentation. I could use
> >> your help.
> >>
> >> Hey, how about let's start with: what are the specs of what Slashdot
> >> itself is using right now?
> >>
> >> == George
>
>
> ------------------------------------------------------------------------------
> The modern datacenter depends on network connectivity to access resources
> and provide services. The best practices for maximizing a physical server's
> connectivity to a physical network are well understood - see how these
> rules translate into the virtual world?
> http://p.sf.net/sfu/oracle-sfdevnlfb
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> https://lists.sourceforge.net/lists/listinfo/slashcode-general
>

Re: [Slashcode-general] Minimum version of every component for a successful Slash install?

[George T. <geo...@gm...>]

<preface>I want to say against any future critiques: my goal is to be
a publisher. I want to run a large community discussion. I think the
moderation system of Slashdot, realized in whatever eventual form, is
the only one for my purposes.

It should be no surprise that I'm much more of an editor than a coder.
Ironically, though, the Slashcode community itself is in need of
reinvigoration, which makes someone like me perhaps more useful at the
moment than someone who can field-strip a Perl rifle.

Please consider me an enlightened end-user: ignorant of the necessary
minutiae, but educable. I'm not a developer. I don't yet understand
certain jargon. I'll need to ask questions that may seem idiotic or
pedantic to some. I ask your indulgence. (Since the community was all
but dead a few days ago, what has anyone still here got to lose by
letting me ask? The trail left by my questions will help and encourage
others like me.)</preface>

Shane -- Forgive my ignorance. When I go to
<https://sourceforge.net/projects/slashcode/files/Bundle-Slash>, I see
"Looking for the latest version? Download Bundle-Slash-2.52.tar.gz
(2.1 KB)". Then I see the litany of versions prior to 2.52.

I understand packages with version numbers. I don't understand what
you mean by version "HEAD", the "last SCM-Head," or where to go to
"get from src." Could you or someone explain?

== George


On Sun, Feb 6, 2011 at 1:09 PM, Shane Zatezalo <sh...@lo...> wrote:
> Distro: CentOS
> Slash-version: HEAD (from src, never package)
>
> Don't use the 2.2.6, it is just *too* ancient to bother with. And the upgrade from 2.26 -> SCM-Head was just brutal. Work from the last SCM-Head.
>
> If I recall I'd start off buy getting perl, mod_perl and apache compiled togther and functionally running.
> While I was doing that, I'd (in another term window) install mySQL (and in another window) start installing CPAN modules (follow the cpan-instructions from slash-HEAD by the book).
>
> Once all that was done, I could make install and then 'install-slashsite' at will.
>
> On Feb 6, 2011, at 7:51 AM, George Taft wrote:
>
>> [...] let me ask those who are
>> still here:
>>
>> The last time you successfully installed Slashcode so that it was up
>> and fully functional, what distro did you use, and what versions of
>> Perl, MySQL, Apache and...well, Slash? Was it actually 2.2.6, or was
>> it something from the repo?
>>
>> For starters, I can tell you that on my second effort, it was Fedora
>> 14, Perl 5.12.3,  MySQL 5.something, Apache 1.3.42, and Slash 2.52.
>> Anyone see any red flags?
>>
>> We shouldn't expect anyone to want to use or support Slashcode when
>> the documentation to install it is half-missing. I'd like to figure
>> out what the latest of everything that work together for any given
>> Linux distro. I volunteer to write that documentation. I could use
>> your help.
>>
>> Hey, how about let's start with: what are the specs of what Slashdot
>> itself is using right now?
>>
>> == George

Re: [Slashcode-general] Minimum version of every component for a successful Slash install?

[Shane Z. <sh...@lo...>]

Distro: CentOS
Slash-version: HEAD (from src, never package)

Don't use the 2.2.6, it is just *too* ancient to bother with. And the upgrade from 2.26 -> SCM-Head was just brutal. Work from the last SCM-Head.

If I recall I'd start off buy getting perl, mod_perl and apache compiled togther and functionally running.
While I was doing that, I'd (in another term window) install mySQL (and in another window) start installing CPAN modules (follow the cpan-instructions from slash-HEAD by the book).

Once all that was done, I could make install and then 'install-slashsite' at will.

On Feb 6, 2011, at 7:51 AM, George Taft wrote:

> [...] let me ask those who are
> still here:
> 
> The last time you successfully installed Slashcode so that it was up
> and fully functional, what distro did you use, and what versions of
> Perl, MySQL, Apache and...well, Slash? Was it actually 2.2.6, or was
> it something from the repo?
> 
> For starters, I can tell you that on my second effort, it was Fedora
> 14, Perl 5.12.3,  MySQL 5.something, Apache 1.3.42, and Slash 2.52.
> Anyone see any red flags?
> 
> We shouldn't expect anyone to want to use or support Slashcode when
> the documentation to install it is half-missing. I'd like to figure
> out what the latest of everything that work together for any given
> Linux distro. I volunteer to write that documentation. I could use
> your help.
> 
> Hey, how about let's start with: what are the specs of what Slashdot
> itself is using right now?
> 
> == George
> 
> ------------------------------------------------------------------------------
> The modern datacenter depends on network connectivity to access resources
> and provide services. The best practices for maximizing a physical server's
> connectivity to a physical network are well understood - see how these
> rules translate into the virtual world? 
> http://p.sf.net/sfu/oracle-sfdevnlfb
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> https://lists.sourceforge.net/lists/listinfo/slashcode-general

[Slashcode-general] Minimum version of every component for a successful Slash install?

[George T. <geo...@gm...>]

So I've made two attempts to install Slashcode on a virtualized
server. I can install any number of different distros. I've tried
CentOS 5.5 and Fedora 14, and crucial functionality seems to be
missing by the time I get done with Slash. (In the former case, I
couldn't see how to post comments; in the latter, I couldn't post
comments or stories, or manage users.)

My ability to manage an install is not strong. I may be making
bonehead mistakes. Or I may be using components that are too new.
Before I conclude that's a matter of PEBCAK, let me ask those who are
still here:

The last time you successfully installed Slashcode so that it was up
and fully functional, what distro did you use, and what versions of
Perl, MySQL, Apache and...well, Slash? Was it actually 2.2.6, or was
it something from the repo?

For starters, I can tell you that on my second effort, it was Fedora
14, Perl 5.12.3,  MySQL 5.something, Apache 1.3.42, and Slash 2.52.
Anyone see any red flags?

We shouldn't expect anyone to want to use or support Slashcode when
the documentation to install it is half-missing. I'd like to figure
out what the latest of everything that work together for any given
Linux distro. I volunteer to write that documentation. I could use
your help.

Hey, how about let's start with: what are the specs of what Slashdot
itself is using right now?

== George

Re: [Slashcode-general] I volunteer to help resuscitate Slashcode

[George T. <geo...@gm...>]

Tell you what. This is slashcode-general, after all. Whoever's still
here is interested in the functionality of Slash, regardless of what
form it takes.

Some of us, however few, think the original Perl code may be worth
saving. A few others think Slash's key functionality should be pursued
in other platforms. And a few others think that the set of value that
Slash represented -- which is more than just its moderation -- is
dead, gone and not coming back.

To the last, I say, if you feel that strongly, please unsubscribe and
drop us a farewell note; if you stay, don't badmouth whatever efforts
others might say they want to put in.

To those who think other platforms should be used: you may be right,
and you may be proven right shortly. If that's the way that people
here decide to go, then perhaps slashcode-general can still be used to
pursue that functionality in, say, Drupal.

To everyone, I say, though: there is this existing code base. It IS
being actively maintained, just not entirely open-source. The
maintainers are not trying to keep it from being open-source; they
just don't have the time to do things like upload the latest revision
to the repo, let alone to write the kind of documentation that would
help people like me install an instance of Slash successfully using
currently-maintained platforms.

There are at least three people who have contacted me privately saying
they all have limited time, but they'd still like to contribute to a
project like this however they can. That's enough for me.

I'd like to thank everyone for contributing to this thread. Even those
who were negative contributed crucial knowledge. I'd also like to see
this thread end. I'm starting a new one for people who are still
interested in Slashcode, in general. I hope that you can contribute to
the knowledge base that this project needs so badly.

== George

On Sat, Feb 5, 2011 at 12:48 PM, T. J. Brumfield <end...@gm...> wrote:
> http://drupal.org/project/slashcomments
>
> Someone already started on one. Apparently it works in modding posts up and
> down, but there is no framework for assigning moderation points in the first
> place. Someone could finish that off.
>
> On Sat, Feb 5, 2011 at 6:04 AM, Steve Perkins <li...@st...>
> wrote:
>>
>>     I would never tell an interested person to *not* work on a
>> project.  However, with there being dozens of viable and thriving CMS
>> systems out there today... I honestly believe your resources would be
>> better spent in developing a plugin for one (or more) of those.
>>
>>     The main selling point of Slash was (is) the moderation system.
>> However, it's not *that* big a task to add similar moderation to a CMS
>> through a plugin.  Maintaining the whole of Slash for this one feature
>> is like a car maker keeping an old model in production for its great
>> dashboard layout.  Few people are going to buy a car based on that
>> criteria alone... and it would be so much easier to copy the dashboard
>> layout into contemporary models.
>>
>>     This second point could ruffle feathers... but not only has the
>> Slash developer community dwindled, the larger Perl web development
>> community isn't what it was 10 years ago either.  I keep my skills sharp
>> enough to tweak old legacy stuff here and there, but in the year 2011 I
>> would never commit to any major new Perl 5 initiative.  You arguably
>> have Python as the main general-purpose Perl successor, Ruby is popular
>> among the more "artsy" crowd, and there's Java for people whose primary
>> job is writing business software.
>>
>>     However, the lion's share of "mod_perl" stuff has gone to PHP.
>> Yeah, it's an ugly hack of a language... but so was Perl!  Perl was
>> simply the ugly hack that most of us started out on and grew comfortable
>> with.  The largest plugin-based CMS systems are written in PHP, and that
>> developer community is large and vibrant.  You have to separate a lot of
>> wheat from the chaff with those guys, but that was always true with Perl
>> developers too.
>>
>>     If you found one or two motivated PHP coders (or hell, just learn
>> it yourself!)... you could probably have Slash-style moderation in a
>> Drupal or Wordpress plugin within weeks.  There may already be plugins
>> that are close, and could be forked and modified to fill the gaps.  The
>> work would be easier, and you would have a larger audience of possible
>> users (whereas nobody's going to drop Drupal for Slash).
>>
>>     Best of luck in whatever direction you pursue!
>>
>> Steve
>>
>>
>>
>> On 2/4/2011 5:13 AM, Eric Dannewitz wrote:
>> > 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
>> >
>> > ------------------------------------------------------------------------------
>> > The modern datacenter depends on network connectivity to access
>> > resources
>> > and provide services. The best practices for maximizing a physical
>> > server's
>> > connectivity to a physical network are well understood - see how these
>> > rules translate into the virtual world?
>> > http://p.sf.net/sfu/oracle-sfdevnlfb
>> > _______________________________________________
>> > Slashcode-general mailing list
>> > Sla...@li...
>> > https://lists.sourceforge.net/lists/listinfo/slashcode-general
>>
>>
>>
>> ------------------------------------------------------------------------------
>> The modern datacenter depends on network connectivity to access resources
>> and provide services. The best practices for maximizing a physical
>> server's
>> connectivity to a physical network are well understood - see how these
>> rules translate into the virtual world?
>> http://p.sf.net/sfu/oracle-sfdevnlfb
>> _______________________________________________
>> Slashcode-general mailing list
>> Sla...@li...
>> https://lists.sourceforge.net/lists/listinfo/slashcode-general
>
>
>
> --
> "I'm questioning my education
> Rewind and what does it show?
> Could be, the truth it becomes you
> I'm a seed, wondering why it grows"
> -- Pearl Jam, Education
>
> ------------------------------------------------------------------------------
> The modern datacenter depends on network connectivity to access resources
> and provide services. The best practices for maximizing a physical server's
> connectivity to a physical network are well understood - see how these
> rules translate into the virtual world?
> http://p.sf.net/sfu/oracle-sfdevnlfb
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> https://lists.sourceforge.net/lists/listinfo/slashcode-general
>
>

Re: [Slashcode-general] I volunteer to help resuscitate Slashcode

[T. J. B. <end...@gm...>]

http://drupal.org/project/slashcomments

Someone already started on one. Apparently it works in modding posts up and
down, but there is no framework for assigning moderation points in the first
place. Someone could finish that off.

On Sat, Feb 5, 2011 at 6:04 AM, Steve Perkins <li...@st...>wrote:

>     I would never tell an interested person to *not* work on a
> project.  However, with there being dozens of viable and thriving CMS
> systems out there today... I honestly believe your resources would be
> better spent in developing a plugin for one (or more) of those.
>
>     The main selling point of Slash was (is) the moderation system.
> However, it's not *that* big a task to add similar moderation to a CMS
> through a plugin.  Maintaining the whole of Slash for this one feature
> is like a car maker keeping an old model in production for its great
> dashboard layout.  Few people are going to buy a car based on that
> criteria alone... and it would be so much easier to copy the dashboard
> layout into contemporary models.
>
>     This second point could ruffle feathers... but not only has the
> Slash developer community dwindled, the larger Perl web development
> community isn't what it was 10 years ago either.  I keep my skills sharp
> enough to tweak old legacy stuff here and there, but in the year 2011 I
> would never commit to any major new Perl 5 initiative.  You arguably
> have Python as the main general-purpose Perl successor, Ruby is popular
> among the more "artsy" crowd, and there's Java for people whose primary
> job is writing business software.
>
>     However, the lion's share of "mod_perl" stuff has gone to PHP.
> Yeah, it's an ugly hack of a language... but so was Perl!  Perl was
> simply the ugly hack that most of us started out on and grew comfortable
> with.  The largest plugin-based CMS systems are written in PHP, and that
> developer community is large and vibrant.  You have to separate a lot of
> wheat from the chaff with those guys, but that was always true with Perl
> developers too.
>
>     If you found one or two motivated PHP coders (or hell, just learn
> it yourself!)... you could probably have Slash-style moderation in a
> Drupal or Wordpress plugin within weeks.  There may already be plugins
> that are close, and could be forked and modified to fill the gaps.  The
> work would be easier, and you would have a larger audience of possible
> users (whereas nobody's going to drop Drupal for Slash).
>
>     Best of luck in whatever direction you pursue!
>
> Steve
>
>
>
> On 2/4/2011 5:13 AM, Eric Dannewitz wrote:
> > 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
> >
> ------------------------------------------------------------------------------
> > The modern datacenter depends on network connectivity to access resources
> > and provide services. The best practices for maximizing a physical
> server's
> > connectivity to a physical network are well understood - see how these
> > rules translate into the virtual world?
> > http://p.sf.net/sfu/oracle-sfdevnlfb
> > _______________________________________________
> > Slashcode-general mailing list
> > Sla...@li...
> > https://lists.sourceforge.net/lists/listinfo/slashcode-general
>
>
>
> ------------------------------------------------------------------------------
> The modern datacenter depends on network connectivity to access resources
> and provide services. The best practices for maximizing a physical server's
> connectivity to a physical network are well understood - see how these
> rules translate into the virtual world?
> http://p.sf.net/sfu/oracle-sfdevnlfb
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> https://lists.sourceforge.net/lists/listinfo/slashcode-general
>



-- 
"I'm questioning my education
Rewind and what does it show?
Could be, the truth it becomes you
I'm a seed, wondering why it grows"
-- Pearl Jam, Education

Re: [Slashcode-general] I volunteer to help resuscitate Slashcode

[Steve P. <li...@st...>]

     I would never tell an interested person to *not* work on a 
project.  However, with there being dozens of viable and thriving CMS 
systems out there today... I honestly believe your resources would be 
better spent in developing a plugin for one (or more) of those.

     The main selling point of Slash was (is) the moderation system.  
However, it's not *that* big a task to add similar moderation to a CMS 
through a plugin.  Maintaining the whole of Slash for this one feature 
is like a car maker keeping an old model in production for its great 
dashboard layout.  Few people are going to buy a car based on that 
criteria alone... and it would be so much easier to copy the dashboard 
layout into contemporary models.

     This second point could ruffle feathers... but not only has the 
Slash developer community dwindled, the larger Perl web development 
community isn't what it was 10 years ago either.  I keep my skills sharp 
enough to tweak old legacy stuff here and there, but in the year 2011 I 
would never commit to any major new Perl 5 initiative.  You arguably 
have Python as the main general-purpose Perl successor, Ruby is popular 
among the more "artsy" crowd, and there's Java for people whose primary 
job is writing business software.

     However, the lion's share of "mod_perl" stuff has gone to PHP.  
Yeah, it's an ugly hack of a language... but so was Perl!  Perl was 
simply the ugly hack that most of us started out on and grew comfortable 
with.  The largest plugin-based CMS systems are written in PHP, and that 
developer community is large and vibrant.  You have to separate a lot of 
wheat from the chaff with those guys, but that was always true with Perl 
developers too.

     If you found one or two motivated PHP coders (or hell, just learn 
it yourself!)... you could probably have Slash-style moderation in a 
Drupal or Wordpress plugin within weeks.  There may already be plugins 
that are close, and could be forked and modified to fill the gaps.  The 
work would be easier, and you would have a larger audience of possible 
users (whereas nobody's going to drop Drupal for Slash).

     Best of luck in whatever direction you pursue!

Steve



On 2/4/2011 5:13 AM, Eric Dannewitz wrote:
> 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
> ------------------------------------------------------------------------------
> The modern datacenter depends on network connectivity to access resources
> and provide services. The best practices for maximizing a physical server's
> connectivity to a physical network are well understood - see how these
> rules translate into the virtual world?
> http://p.sf.net/sfu/oracle-sfdevnlfb
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> https://lists.sourceforge.net/lists/listinfo/slashcode-general

Re: [Slashcode-general] I volunteer to help resuscitate Slashcode

[Alex M. <al...@ow...>]

On Fri, Feb 4, 2011 at 2:24 PM, Alexandre Leroux
<ale...@ec...>wrote:

>
> Hi George,
>
> While I wish you good luck, I too believe Slashcode is heading nowhere
> (other than Slashdot, of course). I've been running a Slashsite from
> 2005 to August 2010, so until fairly recently,
> ...
> So, after 5 years of semi-torture with slash, we finally moved to Drupal
> 6 last August. I don't regret it a bit. While Drupal isn't perfect (what
> is?), I, a non-developer, can manage it and easily configure it.
> Especially important when considering that this ex-slashsite is a
> side-project that I can devote very little time to it. With the
> thousands of Drupal modules and its very active community, I have access
> to plenty of features I would never had access in slash. I should have
> migrated years ago.
>


This is my view also. The Slashcode community no longer exists. I can see no
reason to stick with Slashcode.
Drupal is my CMS of choice nowadays. I even looked into importing Slashcode
databases into Drupal.


Alex Mc

Re: [Slashcode-general] I volunteer to help resuscitate Slashcode

[Alexandre L. <ale...@ec...>]

Hi George,

While I wish you good luck, I too believe Slashcode is heading nowhere 
(other than Slashdot, of course). I've been running a Slashsite from 
2005 to August 2010, so until fairly recently,

Look at the mailing list archives, I think they are revealing. In short, 
there is *no* slashcode community anymore. And very few sites use it 
now. With the help of an experienced slash developer, we even developed 
interesting modules for slashcode, such as GeoRSS support and 
interactive web maps in stories. But community support was inexistent. 
2005-2010 was already too late for Slash to be revived in my opinion.

I've been a big fan of the Slashcode moderation system since early 
2000s, that's why I dived. But I found out that for the system to work 
fine, you need tens of comments per day on your site. That ended up not 
being our case, so the superb slash moderation system was ultimately not 
being exploited to its potential by our site.

So, after 5 years of semi-torture with slash, we finally moved to Drupal 
6 last August. I don't regret it a bit. While Drupal isn't perfect (what 
is?), I, a non-developer, can manage it and easily configure it. 
Especially important when considering that this ex-slashsite is a 
side-project that I can devote very little time to it. With the 
thousands of Drupal modules and its very active community, I have access 
to plenty of features I would never had access in slash. I should have 
migrated years ago.


I loved slash (and still love Slashdot), but I believe slashcode is dead 
and its successful revival would be a miracle. But miracles happen! Good 
luck if you try :-)


Alex, slashgeo.org
--
Alexandre Leroux, M.Sc., ing.
Section de la réponse aux urgences environnementales /
Environmental Emergency Response Section
Centre météorologique canadien / Canadian Meteorological Centre
Environnement Canada / Environment Canada
ale...@ec... - (514) 421-5024


On 02/03/11 19:22, George Taft 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 almost disappeared, like so
> many Mac clones.
> 
> Over the past three months, I've tried to install Slash myself, and I
> run into the sorts of problems that are documented elsewhere. I relied
> on the woefully out-of-date alternate install document at
> misterorange.com. And I still don't know: am I using the right
> distro...is there a best distro? Is this version of Perl too new? This
> version of MySQL or Apache? Why is this thing not working...and why is
> it so hard to make work? The friend who's been helping me through this
> process has constantly grumbled about the suite's age, its reliance on
> aged platforms, and wouldn't I like to try something more modern?
> 
> Nevertheless, no one can name me a CMS that does as good or better a
> job of moderation. (I desperately wish someone could, because I'd be
> pleased to go use that.) The coders have given their reasoning for why
> they still use Perl and Apache 1.3: because they still work. Slashdot
> is living proof that Slashcode works. I buy their logic.
> 
> I believe so strongly in its value as a discussion-moderating tool
> that I'm pledging to volunteer time to revive the Slashcode project.
> I'm asking for help from whoever will give it.
> 
> I'm at best a feral coder. (I found a bug in installing 2.52 the other
> night, a typo that screws up the install at the creation of the
> "Preview" table. I was able to fix it and get the whole install done,
> but it took forever and it only half-works.) But I know what good user
> interface design looks like, and I'm an excellent writer and
> documenter. I'd like at least to help make the installation more
> user-friendly.
> 
> Perhaps it's naive of me to think that this email will make something
> happen. But if you have even a smidgen of interest in making Slash
> accessible to a slightly more general audience, please, please post
> here. Let's begin this project anew.
> 
> == George
> 
> ------------------------------------------------------------------------------
> The modern datacenter depends on network connectivity to access resources
> and provide services. The best practices for maximizing a physical server's
> connectivity to a physical network are well understood - see how these
> rules translate into the virtual world? 
> http://p.sf.net/sfu/oracle-sfdevnlfb
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> https://lists.sourceforge.net/lists/listinfo/slashcode-general

Re: [Slashcode-general] I volunteer to help resuscitate Slashcode

[Shane Z. <sh...@lo...>]

Hello everyone.

I was quite "surprised" to see any email from this listserve. Honestly, I had thought I unsubscribed from it last year, guess not ;)

I don't agree with the below summarization. I think they were saying "look, we do not have the time, resources to do everything that is required to do a proper release build, so we're not packing up tarballs/zips anymore. If you want it, grab it from SCM. If it passes our builds and tests, we tag it R_{foo}. You can base your own stability builds/tests off that versioning, where T_{foo} is unstable."

I not see anything wrong with this, in that there is hardly a project I have participated in over the past few years that I didn't clone (or fork) the project from Github. A zip? A tarball? How antiquated.

I also did not see anything wrong with them saying "we don't have the resources to do a full release". This is a community, afterall. If you want a release, work at it. Is this cumbersome? It can be. Is it community damning? It can be. Maybe it was. But I don't recall anyone from the community stepping up and saying "I'll devote the time, resources, effort, to do releases". (IMHO, to do properly, it's a lot of work, especially if there's no propert test/TDD rig/harness system already in place to help automate things).

I think it's been nearly a year since I did anything slashcode related. I closed my ISP hosting business in 2010, which had a sole last straggling slashcode-using customer until sometime last year. But as to development, ~2009 when I last really did any work in slashcode. I think it was the Geo patch/plugin, which was never finished nor publicly released.

The thing that upset me was the migration from Subversion to Git. Updates to the public tree were seemingly stopped. Replies were "we're getting it setup... just hold on a bit" to "we know it's not working... hold on a bit". To this day, to my knowledge, none of the Geek.net code-base changes have been pushed the public Git repo. If it even exists still? On SF? Github? Look at the log: http://bit.ly/hwRAB2 the last commit was 16 months ago? C'mon, you've got to be kidding me.

Slashcode was, is, a great engine. In many aspects it's design/implementation were far, far ahead of the curve; quite possibly still are. If one tended to have the perl modules it required installed (ie you were already hosting various perl-based projects/websites *or* you just had done a lot of perl development over the years) the installation of Slashcode could be an absolute *breeze*. But w/o the modules, it could be tricky. And let's be clear -- it was the modules/supporting software infrastructure that was a PITA to deal with, not Slashcode's installation. 

As far as someone resurrecting this CMS and putting a group of people together to move it forward, I wish you all the best and I hope you pull it off. I now have current engagements and commitments to other projects, I do not think I have the time, resources, and possibly not even the inclination, to help with this cause.

With that said, this *is* open source. If you could get the Slashdot crew to do a push to their git repo, one could take it, fork it, and run with it. Even if one isn't a developer, you can either learn to be, or devote your time/help in many other ways (documentation/testing/builds/PR... or just plain $$$ so the developers can feed their families).

 Shane



On Feb 4, 2011, at 5:13 AM, Eric Dannewitz wrote:

> And the last post on slash code was basically saying we
> aren't supporting it, but here is where you can get the code.

--
Shane Zatezalo
CEO Lottadot LLC
http://lottadot.com/

[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

Re: [Slashcode-general] I volunteer to help resuscitate Slashcode

[George T. <geo...@gm...>]

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 almost disappeared, like so
>>> >> many Mac clones.
>>> >>
>>> >> Over the past three months, I've tried to install Slash myself, and I
>>> >> run into the sorts of problems that are documented elsewhere. I relied
>>> >> on the woefully out-of-date alternate install document at
>>> >> misterorange.com. And I still don't know: am I using the right
>>> >> distro...is there a best distro? Is this version of Perl too new? This
>>> >> version of MySQL or Apache? Why is this thing not working...and why is
>>> >> it so hard to make work? The friend who's been helping me through this
>>> >> process has constantly grumbled about the suite's age, its reliance on
>>> >> aged platforms, and wouldn't I like to try something more modern?
>>> >>
>>> >> Nevertheless, no one can name me a CMS that does as good or better a
>>> >> job of moderation. (I desperately wish someone could, because I'd be
>>> >> pleased to go use that.) The coders have given their reasoning for why
>>> >> they still use Perl and Apache 1.3: because they still work. Slashdot
>>> >> is living proof that Slashcode works. I buy their logic.
>>> >>
>>> >> I believe so strongly in its value as a discussion-moderating tool
>>> >> that I'm pledging to volunteer time to revive the Slashcode project.
>>> >> I'm asking for help from whoever will give it.
>>> >>
>>> >> I'm at best a feral coder. (I found a bug in installing 2.52 the other
>>> >> night, a typo that screws up the install at the creation of the
>>> >> "Preview" table. I was able to fix it and get the whole install done,
>>> >> but it took forever and it only half-works.) But I know what good user
>>> >> interface design looks like, and I'm an excellent writer and
>>> >> documenter. I'd like at least to help make the installation more
>>> >> user-friendly.
>>> >>
>>> >> Perhaps it's naive of me to think that this email will make something
>>> >> happen. But if you have even a smidgen of interest in making Slash
>>> >> accessible to a slightly more general audience, please, please post
>>> >> here. Let's begin this project anew.
>>> >>
>>> >> == George
>>>
>>> --
>>>
>>> -Andrew Holden
>>> cell/text: 610-212-3466
>>>
>> --
>> "I'm questioning my education
>> Rewind and what does it show?
>> Could be, the truth it becomes you
>> I'm a seed, wondering why it grows"
>> -- Pearl Jam, Education
>>
>>
>
> ------------------------------------------------------------------------------
> The modern datacenter depends on network connectivity to access resources
> and provide services. The best practices for maximizing a physical server's
> connectivity to a physical network are well understood - see how these
> rules translate into the virtual world?
> http://p.sf.net/sfu/oracle-sfdevnlfb
>
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> https://lists.sourceforge.net/lists/listinfo/slashcode-general
>
> ------------------------------------------------------------------------------
> The modern datacenter depends on network connectivity to access resources
> and provide services. The best practices for maximizing a physical server's
> connectivity to a physical network are well understood - see how these
> rules translate into the virtual world?
> http://p.sf.net/sfu/oracle-sfdevnlfb
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> https://lists.sourceforge.net/lists/listinfo/slashcode-general
>
>

Re: [Slashcode-general] I volunteer to help resuscitate Slashcode

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

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 almost disappeared, like so
>> >> many Mac clones.
>> >>
>> >> Over the past three months, I've tried to install Slash myself, and I
>> >> run into the sorts of problems that are documented elsewhere. I relied
>> >> on the woefully out-of-date alternate install document at
>> >> misterorange.com. And I still don't know: am I using the right
>> >> distro...is there a best distro? Is this version of Perl too new? This
>> >> version of MySQL or Apache? Why is this thing not working...and why is
>> >> it so hard to make work? The friend who's been helping me through this
>> >> process has constantly grumbled about the suite's age, its reliance on
>> >> aged platforms, and wouldn't I like to try something more modern?
>> >>
>> >> Nevertheless, no one can name me a CMS that does as good or better a
>> >> job of moderation. (I desperately wish someone could, because I'd be
>> >> pleased to go use that.) The coders have given their reasoning for why
>> >> they still use Perl and Apache 1.3: because they still work. Slashdot
>> >> is living proof that Slashcode works. I buy their logic.
>> >>
>> >> I believe so strongly in its value as a discussion-moderating tool
>> >> that I'm pledging to volunteer time to revive the Slashcode project.
>> >> I'm asking for help from whoever will give it.
>> >>
>> >> I'm at best a feral coder. (I found a bug in installing 2.52 the other
>> >> night, a typo that screws up the install at the creation of the
>> >> "Preview" table. I was able to fix it and get the whole install done,
>> >> but it took forever and it only half-works.) But I know what good user
>> >> interface design looks like, and I'm an excellent writer and
>> >> documenter. I'd like at least to help make the installation more
>> >> user-friendly.
>> >>
>> >> Perhaps it's naive of me to think that this email will make something
>> >> happen. But if you have even a smidgen of interest in making Slash
>> >> accessible to a slightly more general audience, please, please post
>> >> here. Let's begin this project anew.
>> >>
>> >> == George
>>
>> --
>>
>> -Andrew Holden
>> cell/text: 610-212-3466
>>
>> --
> "I'm questioning my education
> Rewind and what does it show?
> Could be, the truth it becomes you
> I'm a seed, wondering why it grows"
>  -- Pearl Jam, Education
>
>
>
------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world?
http://p.sf.net/sfu/oracle-sfdevnlfb

_______________________________________________
Slashcode-general mailing list
Sla...@li...
https://lists.sourceforge.net/lists/listinfo/slashcode-general

Re: [Slashcode-general] I volunteer to help resuscitate Slashcode

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

There are some moderation plugins for wordpress

Sent from my iSomething

On Feb 3, 2011, at 6:45 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 almost disappeared, like so
>>> many Mac clones.
>>>
>>> Over the past three months, I've tried to install Slash myself, and I
>>> run into the sorts of problems that are documented elsewhere. I relied
>>> on the woefully out-of-date alternate install document at
>>> misterorange.com. And I still don't know: am I using the right
>>> distro...is there a best distro? Is this version of Perl too new? This
>>> version of MySQL or Apache? Why is this thing not working...and why is
>>> it so hard to make work? The friend who's been helping me through this
>>> process has constantly grumbled about the suite's age, its reliance on
>>> aged platforms, and wouldn't I like to try something more modern?
>>>
>>> Nevertheless, no one can name me a CMS that does as good or better a
>>> job of moderation. (I desperately wish someone could, because I'd be
>>> pleased to go use that.) The coders have given their reasoning for why
>>> they still use Perl and Apache 1.3: because they still work. Slashdot
>>> is living proof that Slashcode works. I buy their logic.
>>>
>>> I believe so strongly in its value as a discussion-moderating tool
>>> that I'm pledging to volunteer time to revive the Slashcode project.
>>> I'm asking for help from whoever will give it.
>>>
>>> I'm at best a feral coder. (I found a bug in installing 2.52 the other
>>> night, a typo that screws up the install at the creation of the
>>> "Preview" table. I was able to fix it and get the whole install done,
>>> but it took forever and it only half-works.) But I know what good user
>>> interface design looks like, and I'm an excellent writer and
>>> documenter. I'd like at least to help make the installation more
>>> user-friendly.
>>>
>>> Perhaps it's naive of me to think that this email will make something
>>> happen. But if you have even a smidgen of interest in making Slash
>>> accessible to a slightly more general audience, please, please post
>>> here. Let's begin this project anew.
>>>
>>> == George
>>>
>>> ------------------------------------------------------------------------------
>>> The modern datacenter depends on network connectivity to access resources
>>> and provide services. The best practices for maximizing a physical server's
>>> connectivity to a physical network are well understood - see how these
>>> rules translate into the virtual world?
>>> http://p.sf.net/sfu/oracle-sfdevnlfb
>>> _______________________________________________
>>> Slashcode-general mailing list
>>> Sla...@li...
>>> https://lists.sourceforge.net/lists/listinfo/slashcode-general
>>
>> ------------------------------------------------------------------------------
>> The modern datacenter depends on network connectivity to access resources
>> and provide services. The best practices for maximizing a physical server's
>> connectivity to a physical network are well understood - see how these
>> rules translate into the virtual world?
>> http://p.sf.net/sfu/oracle-sfdevnlfb
>> _______________________________________________
>> Slashcode-general mailing list
>> Sla...@li...
>> https://lists.sourceforge.net/lists/listinfo/slashcode-general
>>
>
>
>
> --
>
> -Andrew Holden
> cell/text: 610-212-3466
>
> ------------------------------------------------------------------------------
> The modern datacenter depends on network connectivity to access resources
> and provide services. The best practices for maximizing a physical server's
> connectivity to a physical network are well understood - see how these
> rules translate into the virtual world?
> http://p.sf.net/sfu/oracle-sfdevnlfb
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> https://lists.sourceforge.net/lists/listinfo/slashcode-general

Re: [Slashcode-general] I volunteer to help resuscitate Slashcode

[Clifton W. <cli...@gm...>]

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 almost disappeared, like so
>> >> many Mac clones.
>> >>
>> >> Over the past three months, I've tried to install Slash myself, and I
>> >> run into the sorts of problems that are documented elsewhere. I relied
>> >> on the woefully out-of-date alternate install document at
>> >> misterorange.com. And I still don't know: am I using the right
>> >> distro...is there a best distro? Is this version of Perl too new? This
>> >> version of MySQL or Apache? Why is this thing not working...and why is
>> >> it so hard to make work? The friend who's been helping me through this
>> >> process has constantly grumbled about the suite's age, its reliance on
>> >> aged platforms, and wouldn't I like to try something more modern?
>> >>
>> >> Nevertheless, no one can name me a CMS that does as good or better a
>> >> job of moderation. (I desperately wish someone could, because I'd be
>> >> pleased to go use that.) The coders have given their reasoning for why
>> >> they still use Perl and Apache 1.3: because they still work. Slashdot
>> >> is living proof that Slashcode works. I buy their logic.
>> >>
>> >> I believe so strongly in its value as a discussion-moderating tool
>> >> that I'm pledging to volunteer time to revive the Slashcode project.
>> >> I'm asking for help from whoever will give it.
>> >>
>> >> I'm at best a feral coder. (I found a bug in installing 2.52 the other
>> >> night, a typo that screws up the install at the creation of the
>> >> "Preview" table. I was able to fix it and get the whole install done,
>> >> but it took forever and it only half-works.) But I know what good user
>> >> interface design looks like, and I'm an excellent writer and
>> >> documenter. I'd like at least to help make the installation more
>> >> user-friendly.
>> >>
>> >> Perhaps it's naive of me to think that this email will make something
>> >> happen. But if you have even a smidgen of interest in making Slash
>> >> accessible to a slightly more general audience, please, please post
>> >> here. Let's begin this project anew.
>> >>
>> >> == George
>>
>> --
>>
>> -Andrew Holden
>> cell/text: 610-212-3466
>>
>> --
> "I'm questioning my education
> Rewind and what does it show?
> Could be, the truth it becomes you
> I'm a seed, wondering why it grows"
>  -- Pearl Jam, Education
>
>
>

Re: [Slashcode-general] I volunteer to help resuscitate Slashcode

[Andre-John M. <aj...@sy...>]

I tried contributing to Slashcode a few years back, but I found some of the
Perl libraries used weren't getting the necessary developer attention. 
Because of that I had wondered whether it would have been better just to
migrate the code base to PHP, or some other web oriented language with a
more active community, though given the size of the task I didn't
give it another thought.

Just my 5c.

On 3-Feb-2011, at 20:56, Marc G. Fournier wrote:

> 
> 
> I'd be interested in seeing this go somewhere myself ... to the point that 
> if someone wished to fork (assuming the current developers are no longer 
> available / interested), I'd provide resources towards that end ... I own 
> my own servers, so providing a VM on one of them is simple enough ...
> 
> 
> 
> On Thu, 3 Feb 2011, George Taft 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 almost disappeared, like so
>> many Mac clones.
>> 
>> Over the past three months, I've tried to install Slash myself, and I
>> run into the sorts of problems that are documented elsewhere. I relied
>> on the woefully out-of-date alternate install document at
>> misterorange.com. And I still don't know: am I using the right
>> distro...is there a best distro? Is this version of Perl too new? This
>> version of MySQL or Apache? Why is this thing not working...and why is
>> it so hard to make work? The friend who's been helping me through this
>> process has constantly grumbled about the suite's age, its reliance on
>> aged platforms, and wouldn't I like to try something more modern?
>> 
>> Nevertheless, no one can name me a CMS that does as good or better a
>> job of moderation. (I desperately wish someone could, because I'd be
>> pleased to go use that.) The coders have given their reasoning for why
>> they still use Perl and Apache 1.3: because they still work. Slashdot
>> is living proof that Slashcode works. I buy their logic.
>> 
>> I believe so strongly in its value as a discussion-moderating tool
>> that I'm pledging to volunteer time to revive the Slashcode project.
>> I'm asking for help from whoever will give it.
>> 
>> I'm at best a feral coder. (I found a bug in installing 2.52 the other
>> night, a typo that screws up the install at the creation of the
>> "Preview" table. I was able to fix it and get the whole install done,
>> but it took forever and it only half-works.) But I know what good user
>> interface design looks like, and I'm an excellent writer and
>> documenter. I'd like at least to help make the installation more
>> user-friendly.
>> 
>> Perhaps it's naive of me to think that this email will make something
>> happen. But if you have even a smidgen of interest in making Slash
>> accessible to a slightly more general audience, please, please post
>> here. Let's begin this project anew.
>> 
>> == George
>> 
>> ------------------------------------------------------------------------------
>> The modern datacenter depends on network connectivity to access resources
>> and provide services. The best practices for maximizing a physical server's
>> connectivity to a physical network are well understood - see how these
>> rules translate into the virtual world?
>> http://p.sf.net/sfu/oracle-sfdevnlfb
>> _______________________________________________
>> Slashcode-general mailing list
>> Sla...@li...
>> https://lists.sourceforge.net/lists/listinfo/slashcode-general
>> 
> 
> ----
> Marc G. Fournier                        Hub.Org Hosting Solutions S.A.
> sc...@hu...                                     http://www.hub.org
> 
> Yahoo:yscrappy    Skype: hub.org    ICQ:7615664    MSN:sc...@hu...
> 
> ------------------------------------------------------------------------------
> The modern datacenter depends on network connectivity to access resources
> and provide services. The best practices for maximizing a physical server's
> connectivity to a physical network are well understood - see how these
> rules translate into the virtual world? 
> http://p.sf.net/sfu/oracle-sfdevnlfb
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> https://lists.sourceforge.net/lists/listinfo/slashcode-general
> 

Re: [Slashcode-general] I volunteer to help resuscitate Slashcode

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

I made the conversion to wordpress from slash and it was fairly painless

Sent from my iSomething

On Feb 3, 2011, at 6:40 PM, Clifton Wood <cli...@gm...> wrote:

I've done Wordpress and it's missing something that Slashcode brings to the
table. I guess I'm biased. I've worked with Slashcode for years and
Wordpress is unfamiliar and...well... PHP. Slashcode's template system makes
sense to me and the one that Wordpress uses seems unnecessarily complex.

In My Humble Opinion, I would NOT recommend moving from Slash to Wordpress
unless you had serious help to do so. To those who have made the conversion,
you have my respect.

I'd be all for reinvigorating the Slashcode community, however I don't know
how much time I'd have to contribute to it.

To all who endeavor to do so, you'd have whatever support I can give.

Good luck!

- Cliff

On Thu, Feb 3, 2011 at 8:56 PM, Marc G. Fournier <sc...@hu...> wrote:

>
>
> I'd be interested in seeing this go somewhere myself ... to the point that
> if someone wished to fork (assuming the current developers are no longer
> available / interested), I'd provide resources towards that end ... I own
> my own servers, so providing a VM on one of them is simple enough ...
>
>
>
> On Thu, 3 Feb 2011, George Taft 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 almost disappeared, like so
> > many Mac clones.
> >
> > Over the past three months, I've tried to install Slash myself, and I
> > run into the sorts of problems that are documented elsewhere. I relied
> > on the woefully out-of-date alternate install document at
> > misterorange.com. And I still don't know: am I using the right
> > distro...is there a best distro? Is this version of Perl too new? This
> > version of MySQL or Apache? Why is this thing not working...and why is
> > it so hard to make work? The friend who's been helping me through this
> > process has constantly grumbled about the suite's age, its reliance on
> > aged platforms, and wouldn't I like to try something more modern?
> >
> > Nevertheless, no one can name me a CMS that does as good or better a
> > job of moderation. (I desperately wish someone could, because I'd be
> > pleased to go use that.) The coders have given their reasoning for why
> > they still use Perl and Apache 1.3: because they still work. Slashdot
> > is living proof that Slashcode works. I buy their logic.
> >
> > I believe so strongly in its value as a discussion-moderating tool
> > that I'm pledging to volunteer time to revive the Slashcode project.
> > I'm asking for help from whoever will give it.
> >
> > I'm at best a feral coder. (I found a bug in installing 2.52 the other
> > night, a typo that screws up the install at the creation of the
> > "Preview" table. I was able to fix it and get the whole install done,
> > but it took forever and it only half-works.) But I know what good user
> > interface design looks like, and I'm an excellent writer and
> > documenter. I'd like at least to help make the installation more
> > user-friendly.
> >
> > Perhaps it's naive of me to think that this email will make something
> > happen. But if you have even a smidgen of interest in making Slash
> > accessible to a slightly more general audience, please, please post
> > here. Let's begin this project anew.
>
------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world?
http://p.sf.net/sfu/oracle-sfdevnlfb

_______________________________________________
Slashcode-general mailing list
Sla...@li...
https://lists.sourceforge.net/lists/listinfo/slashcode-general

Re: [Slashcode-general] I volunteer to help resuscitate Slashcode

[T. J. B. <end...@gm...>]

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 almost disappeared, like so
> >> many Mac clones.
> >>
> >> Over the past three months, I've tried to install Slash myself, and I
> >> run into the sorts of problems that are documented elsewhere. I relied
> >> on the woefully out-of-date alternate install document at
> >> misterorange.com. And I still don't know: am I using the right
> >> distro...is there a best distro? Is this version of Perl too new? This
> >> version of MySQL or Apache? Why is this thing not working...and why is
> >> it so hard to make work? The friend who's been helping me through this
> >> process has constantly grumbled about the suite's age, its reliance on
> >> aged platforms, and wouldn't I like to try something more modern?
> >>
> >> Nevertheless, no one can name me a CMS that does as good or better a
> >> job of moderation. (I desperately wish someone could, because I'd be
> >> pleased to go use that.) The coders have given their reasoning for why
> >> they still use Perl and Apache 1.3: because they still work. Slashdot
> >> is living proof that Slashcode works. I buy their logic.
> >>
> >> I believe so strongly in its value as a discussion-moderating tool
> >> that I'm pledging to volunteer time to revive the Slashcode project.
> >> I'm asking for help from whoever will give it.
> >>
> >> I'm at best a feral coder. (I found a bug in installing 2.52 the other
> >> night, a typo that screws up the install at the creation of the
> >> "Preview" table. I was able to fix it and get the whole install done,
> >> but it took forever and it only half-works.) But I know what good user
> >> interface design looks like, and I'm an excellent writer and
> >> documenter. I'd like at least to help make the installation more
> >> user-friendly.
> >>
> >> Perhaps it's naive of me to think that this email will make something
> >> happen. But if you have even a smidgen of interest in making Slash
> >> accessible to a slightly more general audience, please, please post
> >> here. Let's begin this project anew.
> >>
> >> == George
> >>
> >>
> ------------------------------------------------------------------------------
> >> The modern datacenter depends on network connectivity to access
> resources
> >> and provide services. The best practices for maximizing a physical
> server's
> >> connectivity to a physical network are well understood - see how these
> >> rules translate into the virtual world?
> >> http://p.sf.net/sfu/oracle-sfdevnlfb
> >> _______________________________________________
> >> Slashcode-general mailing list
> >> Sla...@li...
> >> https://lists.sourceforge.net/lists/listinfo/slashcode-general
> >
> >
> ------------------------------------------------------------------------------
> > The modern datacenter depends on network connectivity to access resources
> > and provide services. The best practices for maximizing a physical
> server's
> > connectivity to a physical network are well understood - see how these
> > rules translate into the virtual world?
> > http://p.sf.net/sfu/oracle-sfdevnlfb
> > _______________________________________________
> > Slashcode-general mailing list
> > Sla...@li...
> > https://lists.sourceforge.net/lists/listinfo/slashcode-general
> >
>
>
>
> --
>
> -Andrew Holden
> cell/text: 610-212-3466
>
>
> ------------------------------------------------------------------------------
> The modern datacenter depends on network connectivity to access resources
> and provide services. The best practices for maximizing a physical server's
> connectivity to a physical network are well understood - see how these
> rules translate into the virtual world?
> http://p.sf.net/sfu/oracle-sfdevnlfb
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> https://lists.sourceforge.net/lists/listinfo/slashcode-general
>



-- 
"I'm questioning my education
Rewind and what does it show?
Could be, the truth it becomes you
I'm a seed, wondering why it grows"
-- Pearl Jam, Education

Re: [Slashcode-general] I volunteer to help resuscitate Slashcode

[A H <hol...@gm...>]

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 almost disappeared, like so
>> many Mac clones.
>>
>> Over the past three months, I've tried to install Slash myself, and I
>> run into the sorts of problems that are documented elsewhere. I relied
>> on the woefully out-of-date alternate install document at
>> misterorange.com. And I still don't know: am I using the right
>> distro...is there a best distro? Is this version of Perl too new? This
>> version of MySQL or Apache? Why is this thing not working...and why is
>> it so hard to make work? The friend who's been helping me through this
>> process has constantly grumbled about the suite's age, its reliance on
>> aged platforms, and wouldn't I like to try something more modern?
>>
>> Nevertheless, no one can name me a CMS that does as good or better a
>> job of moderation. (I desperately wish someone could, because I'd be
>> pleased to go use that.) The coders have given their reasoning for why
>> they still use Perl and Apache 1.3: because they still work. Slashdot
>> is living proof that Slashcode works. I buy their logic.
>>
>> I believe so strongly in its value as a discussion-moderating tool
>> that I'm pledging to volunteer time to revive the Slashcode project.
>> I'm asking for help from whoever will give it.
>>
>> I'm at best a feral coder. (I found a bug in installing 2.52 the other
>> night, a typo that screws up the install at the creation of the
>> "Preview" table. I was able to fix it and get the whole install done,
>> but it took forever and it only half-works.) But I know what good user
>> interface design looks like, and I'm an excellent writer and
>> documenter. I'd like at least to help make the installation more
>> user-friendly.
>>
>> Perhaps it's naive of me to think that this email will make something
>> happen. But if you have even a smidgen of interest in making Slash
>> accessible to a slightly more general audience, please, please post
>> here. Let's begin this project anew.
>>
>> == George
>>
>> ------------------------------------------------------------------------------
>> The modern datacenter depends on network connectivity to access resources
>> and provide services. The best practices for maximizing a physical server's
>> connectivity to a physical network are well understood - see how these
>> rules translate into the virtual world?
>> http://p.sf.net/sfu/oracle-sfdevnlfb
>> _______________________________________________
>> Slashcode-general mailing list
>> Sla...@li...
>> https://lists.sourceforge.net/lists/listinfo/slashcode-general
>
> ------------------------------------------------------------------------------
> The modern datacenter depends on network connectivity to access resources
> and provide services. The best practices for maximizing a physical server's
> connectivity to a physical network are well understood - see how these
> rules translate into the virtual world?
> http://p.sf.net/sfu/oracle-sfdevnlfb
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> https://lists.sourceforge.net/lists/listinfo/slashcode-general
>



-- 

-Andrew Holden
cell/text: 610-212-3466

Re: [Slashcode-general] I volunteer to help resuscitate Slashcode

[Marc G. F. <sc...@hu...>]

On Thu, 3 Feb 2011, Eric Dannewitz wrote:

> I'd ditch slash for wordpress. I did and have never regretted it

Wordpress has its place, replacing Slashcode isn't it ... I use it for our 
main web site, but that is mostly static content ... ppl use it for blogs 
... but, slashcode is so much more ...




  >
> 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 almost disappeared, like so
>> many Mac clones.
>>
>> Over the past three months, I've tried to install Slash myself, and I
>> run into the sorts of problems that are documented elsewhere. I relied
>> on the woefully out-of-date alternate install document at
>> misterorange.com. And I still don't know: am I using the right
>> distro...is there a best distro? Is this version of Perl too new? This
>> version of MySQL or Apache? Why is this thing not working...and why is
>> it so hard to make work? The friend who's been helping me through this
>> process has constantly grumbled about the suite's age, its reliance on
>> aged platforms, and wouldn't I like to try something more modern?
>>
>> Nevertheless, no one can name me a CMS that does as good or better a
>> job of moderation. (I desperately wish someone could, because I'd be
>> pleased to go use that.) The coders have given their reasoning for why
>> they still use Perl and Apache 1.3: because they still work. Slashdot
>> is living proof that Slashcode works. I buy their logic.
>>
>> I believe so strongly in its value as a discussion-moderating tool
>> that I'm pledging to volunteer time to revive the Slashcode project.
>> I'm asking for help from whoever will give it.
>>
>> I'm at best a feral coder. (I found a bug in installing 2.52 the other
>> night, a typo that screws up the install at the creation of the
>> "Preview" table. I was able to fix it and get the whole install done,
>> but it took forever and it only half-works.) But I know what good user
>> interface design looks like, and I'm an excellent writer and
>> documenter. I'd like at least to help make the installation more
>> user-friendly.
>>
>> Perhaps it's naive of me to think that this email will make something
>> happen. But if you have even a smidgen of interest in making Slash
>> accessible to a slightly more general audience, please, please post
>> here. Let's begin this project anew.
>>
>> == George
>>
>> ------------------------------------------------------------------------------
>> The modern datacenter depends on network connectivity to access resources
>> and provide services. The best practices for maximizing a physical server's
>> connectivity to a physical network are well understood - see how these
>> rules translate into the virtual world?
>> http://p.sf.net/sfu/oracle-sfdevnlfb
>> _______________________________________________
>> Slashcode-general mailing list
>> Sla...@li...
>> https://lists.sourceforge.net/lists/listinfo/slashcode-general
>
> ------------------------------------------------------------------------------
> The modern datacenter depends on network connectivity to access resources
> and provide services. The best practices for maximizing a physical server's
> connectivity to a physical network are well understood - see how these
> rules translate into the virtual world?
> http://p.sf.net/sfu/oracle-sfdevnlfb
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> https://lists.sourceforge.net/lists/listinfo/slashcode-general
>

----
Marc G. Fournier                        Hub.Org Hosting Solutions S.A.
sc...@hu...                                     http://www.hub.org

Yahoo:yscrappy    Skype: hub.org    ICQ:7615664    MSN:sc...@hu...

Re: [Slashcode-general] I volunteer to help resuscitate Slashcode

[Clifton W. <cli...@gm...>]

I've done Wordpress and it's missing something that Slashcode brings to the
table. I guess I'm biased. I've worked with Slashcode for years and
Wordpress is unfamiliar and...well... PHP. Slashcode's template system makes
sense to me and the one that Wordpress uses seems unnecessarily complex.

In My Humble Opinion, I would NOT recommend moving from Slash to Wordpress
unless you had serious help to do so. To those who have made the conversion,
you have my respect.

I'd be all for reinvigorating the Slashcode community, however I don't know
how much time I'd have to contribute to it.

To all who endeavor to do so, you'd have whatever support I can give.

Good luck!

- Cliff

On Thu, Feb 3, 2011 at 8:56 PM, Marc G. Fournier <sc...@hu...> wrote:

>
>
> I'd be interested in seeing this go somewhere myself ... to the point that
> if someone wished to fork (assuming the current developers are no longer
> available / interested), I'd provide resources towards that end ... I own
> my own servers, so providing a VM on one of them is simple enough ...
>
>
>
> On Thu, 3 Feb 2011, George Taft 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 almost disappeared, like so
> > many Mac clones.
> >
> > Over the past three months, I've tried to install Slash myself, and I
> > run into the sorts of problems that are documented elsewhere. I relied
> > on the woefully out-of-date alternate install document at
> > misterorange.com. And I still don't know: am I using the right
> > distro...is there a best distro? Is this version of Perl too new? This
> > version of MySQL or Apache? Why is this thing not working...and why is
> > it so hard to make work? The friend who's been helping me through this
> > process has constantly grumbled about the suite's age, its reliance on
> > aged platforms, and wouldn't I like to try something more modern?
> >
> > Nevertheless, no one can name me a CMS that does as good or better a
> > job of moderation. (I desperately wish someone could, because I'd be
> > pleased to go use that.) The coders have given their reasoning for why
> > they still use Perl and Apache 1.3: because they still work. Slashdot
> > is living proof that Slashcode works. I buy their logic.
> >
> > I believe so strongly in its value as a discussion-moderating tool
> > that I'm pledging to volunteer time to revive the Slashcode project.
> > I'm asking for help from whoever will give it.
> >
> > I'm at best a feral coder. (I found a bug in installing 2.52 the other
> > night, a typo that screws up the install at the creation of the
> > "Preview" table. I was able to fix it and get the whole install done,
> > but it took forever and it only half-works.) But I know what good user
> > interface design looks like, and I'm an excellent writer and
> > documenter. I'd like at least to help make the installation more
> > user-friendly.
> >
> > Perhaps it's naive of me to think that this email will make something
> > happen. But if you have even a smidgen of interest in making Slash
> > accessible to a slightly more general audience, please, please post
> > here. Let's begin this project anew.
>

Re: [Slashcode-general] I volunteer to help resuscitate Slashcode

[Marc G. F. <sc...@hu...>]

I'd be interested in seeing this go somewhere myself ... to the point that 
if someone wished to fork (assuming the current developers are no longer 
available / interested), I'd provide resources towards that end ... I own 
my own servers, so providing a VM on one of them is simple enough ...



On Thu, 3 Feb 2011, George Taft 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 almost disappeared, like so
> many Mac clones.
>
> Over the past three months, I've tried to install Slash myself, and I
> run into the sorts of problems that are documented elsewhere. I relied
> on the woefully out-of-date alternate install document at
> misterorange.com. And I still don't know: am I using the right
> distro...is there a best distro? Is this version of Perl too new? This
> version of MySQL or Apache? Why is this thing not working...and why is
> it so hard to make work? The friend who's been helping me through this
> process has constantly grumbled about the suite's age, its reliance on
> aged platforms, and wouldn't I like to try something more modern?
>
> Nevertheless, no one can name me a CMS that does as good or better a
> job of moderation. (I desperately wish someone could, because I'd be
> pleased to go use that.) The coders have given their reasoning for why
> they still use Perl and Apache 1.3: because they still work. Slashdot
> is living proof that Slashcode works. I buy their logic.
>
> I believe so strongly in its value as a discussion-moderating tool
> that I'm pledging to volunteer time to revive the Slashcode project.
> I'm asking for help from whoever will give it.
>
> I'm at best a feral coder. (I found a bug in installing 2.52 the other
> night, a typo that screws up the install at the creation of the
> "Preview" table. I was able to fix it and get the whole install done,
> but it took forever and it only half-works.) But I know what good user
> interface design looks like, and I'm an excellent writer and
> documenter. I'd like at least to help make the installation more
> user-friendly.
>
> Perhaps it's naive of me to think that this email will make something
> happen. But if you have even a smidgen of interest in making Slash
> accessible to a slightly more general audience, please, please post
> here. Let's begin this project anew.
>
> == George
>
> ------------------------------------------------------------------------------
> The modern datacenter depends on network connectivity to access resources
> and provide services. The best practices for maximizing a physical server's
> connectivity to a physical network are well understood - see how these
> rules translate into the virtual world?
> http://p.sf.net/sfu/oracle-sfdevnlfb
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> https://lists.sourceforge.net/lists/listinfo/slashcode-general
>

----
Marc G. Fournier                        Hub.Org Hosting Solutions S.A.
sc...@hu...                                     http://www.hub.org

Yahoo:yscrappy    Skype: hub.org    ICQ:7615664    MSN:sc...@hu...

Re: [Slashcode-general] I volunteer to help resuscitate Slashcode

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

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 almost disappeared, like so
> many Mac clones.
>
> Over the past three months, I've tried to install Slash myself, and I
> run into the sorts of problems that are documented elsewhere. I relied
> on the woefully out-of-date alternate install document at
> misterorange.com. And I still don't know: am I using the right
> distro...is there a best distro? Is this version of Perl too new? This
> version of MySQL or Apache? Why is this thing not working...and why is
> it so hard to make work? The friend who's been helping me through this
> process has constantly grumbled about the suite's age, its reliance on
> aged platforms, and wouldn't I like to try something more modern?
>
> Nevertheless, no one can name me a CMS that does as good or better a
> job of moderation. (I desperately wish someone could, because I'd be
> pleased to go use that.) The coders have given their reasoning for why
> they still use Perl and Apache 1.3: because they still work. Slashdot
> is living proof that Slashcode works. I buy their logic.
>
> I believe so strongly in its value as a discussion-moderating tool
> that I'm pledging to volunteer time to revive the Slashcode project.
> I'm asking for help from whoever will give it.
>
> I'm at best a feral coder. (I found a bug in installing 2.52 the other
> night, a typo that screws up the install at the creation of the
> "Preview" table. I was able to fix it and get the whole install done,
> but it took forever and it only half-works.) But I know what good user
> interface design looks like, and I'm an excellent writer and
> documenter. I'd like at least to help make the installation more
> user-friendly.
>
> Perhaps it's naive of me to think that this email will make something
> happen. But if you have even a smidgen of interest in making Slash
> accessible to a slightly more general audience, please, please post
> here. Let's begin this project anew.
>
> == George
>
> ------------------------------------------------------------------------------
> The modern datacenter depends on network connectivity to access resources
> and provide services. The best practices for maximizing a physical server's
> connectivity to a physical network are well understood - see how these
> rules translate into the virtual world?
> http://p.sf.net/sfu/oracle-sfdevnlfb
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> https://lists.sourceforge.net/lists/listinfo/slashcode-general

[Slashcode-general] I volunteer to help resuscitate Slashcode

[George T. <geo...@gm...>]

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 almost disappeared, like so
many Mac clones.

Over the past three months, I've tried to install Slash myself, and I
run into the sorts of problems that are documented elsewhere. I relied
on the woefully out-of-date alternate install document at
misterorange.com. And I still don't know: am I using the right
distro...is there a best distro? Is this version of Perl too new? This
version of MySQL or Apache? Why is this thing not working...and why is
it so hard to make work? The friend who's been helping me through this
process has constantly grumbled about the suite's age, its reliance on
aged platforms, and wouldn't I like to try something more modern?

Nevertheless, no one can name me a CMS that does as good or better a
job of moderation. (I desperately wish someone could, because I'd be
pleased to go use that.) The coders have given their reasoning for why
they still use Perl and Apache 1.3: because they still work. Slashdot
is living proof that Slashcode works. I buy their logic.

I believe so strongly in its value as a discussion-moderating tool
that I'm pledging to volunteer time to revive the Slashcode project.
I'm asking for help from whoever will give it.

I'm at best a feral coder. (I found a bug in installing 2.52 the other
night, a typo that screws up the install at the creation of the
"Preview" table. I was able to fix it and get the whole install done,
but it took forever and it only half-works.) But I know what good user
interface design looks like, and I'm an excellent writer and
documenter. I'd like at least to help make the installation more
user-friendly.

Perhaps it's naive of me to think that this email will make something
happen. But if you have even a smidgen of interest in making Slash
accessible to a slightly more general audience, please, please post
here. Let's begin this project anew.

== George

[Slashcode-general] consulting opportunity

[<as...@sp...>]

I seek assistance in setting up a slash code site.  This might be an  
on-going opportunity for some support as well.