From: Marc G. F. <sc...@hu...> - 2009-09-19 04:10:31
|
Started playing with Slashcode this week to setup a news site ... most impressed overall, but didn't clue in how ancient the code is that I'm using ... I should have figured somethign was 'funny' when the PostgreSQL code was alpha, considering that Slashdot ran production on it for awhile ... That said ... someone suggested a code fork, since apparently the developers out 'in-communicado'? I read one person commenting on their company having done plugins (ie. the Geo / mapping stuff), so presumable there is *some* internals knowledge there ... ? I run a hosting company, and already support both Horde and PostgreSQL ... providing resources to a third would be easy, if there were others that were interested ... ? Even just taking the current code and modernizing it (Apache 2.2, MySQL 5.x, Perl 5.8.9 ... I'd be interested in getting PostgreSQL support *out* of alpha myself) would be a huge improvement ... Anyone interested enough to do more then just talk about it ... ? :) Unless Slashcode is trademarked, we could fork / name it something similar ... not too keen on SlashcodeTNG, but something along those lines? Anyone? ---- 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... |
From: Marc G. F. <sc...@hu...> - 2009-09-19 05:07:51
|
Just as a follow up, I've email'd the three developers / maintainers of Slashcode itself to see if there is some way of handing things off to a new crew ... there is just soooooo much in place now, and the project name is a known quantity, that the idea of forking and rebranding sounds like such a waste of history if we can somehow just revive what is there ... Will let y'all know if / what I hear back ... *cross fingers* On Sat, 19 Sep 2009, Marc G. Fournier wrote: > > Started playing with Slashcode this week to setup a news site ... most > impressed overall, but didn't clue in how ancient the code is that I'm > using ... I should have figured somethign was 'funny' when the PostgreSQL > code was alpha, considering that Slashdot ran production on it for awhile > ... > > That said ... someone suggested a code fork, since apparently the > developers out 'in-communicado'? > > I read one person commenting on their company having done plugins (ie. the > Geo / mapping stuff), so presumable there is *some* internals knowledge > there ... ? > > I run a hosting company, and already support both Horde and PostgreSQL ... > providing resources to a third would be easy, if there were others that > were interested ... ? > > Even just taking the current code and modernizing it (Apache 2.2, MySQL > 5.x, Perl 5.8.9 ... I'd be interested in getting PostgreSQL support *out* > of alpha myself) would be a huge improvement ... > > Anyone interested enough to do more then just talk about it ... ? :) > > Unless Slashcode is trademarked, we could fork / name it something similar > ... not too keen on SlashcodeTNG, but something along those lines? > > Anyone? > > ---- > 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... > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > 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... |
From: Alexandre L. <ale...@ec...> - 2009-09-21 14:27:57
|
Bonjour Marc, I'm the author "Slashcode is dead?" post. With the answers I got (some on my /. journal, some replies to this list and some personal email), it's clear that unless something suddenly significantly change, Slashcode is really dead. I'm obviously not really happy about this, having invested a lot of efforts in the past 5 years. I still really love the Slash approach and technology, but there has been no development for years and the Slashdot team seems unwilling (for various good reasons I guess) to share their latest versions. Also consider that Shane Zatezalo, the main Slash helper outside the slash team has himself, to my knowledge, stopped using Slash and spending time on it. The community has degraded to mostly nothing. I am not trying to discourage you, just to inform you. I of course wish you the best of luck at reviving Slashcode! Meanwhile, I plan to move my small Slashsite (slashgeo.org, about 30,000 daily hits, 2100 registered members, very few comments) to Drupal. There is an existing migration method to go from Slash to Drupal. I wish to try that avenue in the coming months. I may change my mind, but that will happen only if we can get Slashcode back to modernity (with the Slashdot code?) *and* reassemble a vivid developers community. Bonne chance Marc ! Keep us updated on your findings. Alex :-) -- Alexandre Leroux, M.Sc., Ing. Environnement Canada / Environment Canada Centre météorologique canadien / Canadian Meteorological Centre Section de la réponse aux urgences environnementales / Environmental Emergency Response Section ale...@ec... On 09/19/09 01:07, Marc G. Fournier wrote: > Just as a follow up, I've email'd the three developers / maintainers of > Slashcode itself to see if there is some way of handing things off to a > new crew ... there is just soooooo much in place now, and the project name > is a known quantity, that the idea of forking and rebranding sounds like > such a waste of history if we can somehow just revive what is there ... > > Will let y'all know if / what I hear back ... *cross fingers* > > On Sat, 19 Sep 2009, Marc G. Fournier wrote: > >> Started playing with Slashcode this week to setup a news site ... most >> impressed overall, but didn't clue in how ancient the code is that I'm >> using ... I should have figured somethign was 'funny' when the PostgreSQL >> code was alpha, considering that Slashdot ran production on it for awhile >> ... >> >> That said ... someone suggested a code fork, since apparently the >> developers out 'in-communicado'? >> >> I read one person commenting on their company having done plugins (ie. the >> Geo / mapping stuff), so presumable there is *some* internals knowledge >> there ... ? >> >> I run a hosting company, and already support both Horde and PostgreSQL ... >> providing resources to a third would be easy, if there were others that >> were interested ... ? >> >> Even just taking the current code and modernizing it (Apache 2.2, MySQL >> 5.x, Perl 5.8.9 ... I'd be interested in getting PostgreSQL support *out* >> of alpha myself) would be a huge improvement ... >> >> Anyone interested enough to do more then just talk about it ... ? :) >> >> Unless Slashcode is trademarked, we could fork / name it something similar >> ... not too keen on SlashcodeTNG, but something along those lines? >> >> Anyone? >> >> ---- >> 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... >> >> ------------------------------------------------------------------------------ >> Come build with us! The BlackBerry® Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart your >> developing skills, take BlackBerry mobile applications to market and stay >> ahead of the curve. Join us from November 9-12, 2009. Register now! >> http://p.sf.net/sfu/devconf >> _______________________________________________ >> 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... > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Slashcode-general mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-general |
From: Axel B. <ab...@no...> - 2009-09-21 19:20:19
|
Hi Alex, On Mon, Sep 21, 2009 at 10:27:41AM -0400, Alexandre Leroux wrote: > There is an existing migration method to go from Slash to Drupal. Any pointers to resources about this on the web? Regards, Axel -- Axel Beckert - ab...@de..., ab...@no... - http://noone.org/abe/ |
From: Alexandre L. <ale...@ec...> - 2009-09-21 19:39:05
|
On 09/21/09 15:20, Axel Beckert wrote: > On Mon, Sep 21, 2009 at 10:27:41AM -0400, Alexandre Leroux wrote: >> There is an existing migration method to go from Slash to Drupal. > > Any pointers to resources about this on the web? Sure :-) Here's what I've been invited to use: http://drupal.org/node/235564 But even more important to me, someone from my Slashgeo user community who manages major Drupal sites offered to actually do the migration from Slashcode to Drupal for free because he likes us (Slashgeo is a registered non-profit org). He even already did the front end, I just need to find some time to give him access to our Slashcode database for him to start the migration of users and stories. (Well, I must choose a reliable Drupal host first) I'm not sure if today's discussion about reviving Slash will change my mind and make me stick with Slashcode. You see, I'm no developer myself (I can help, but not that much), getting support from the Slash community is probably way harder than relying on Drupal or Wordpress documentation, wikis, active communities, etc. I am paying a (very friendly :-) Slash developer for support at the moment, but that developer isn't doing Slashcode projects anymore. Drupal has so much more features than Slash, I fear there is so much catching up to do if I stick with Slash. (that said, I haven't seen the latest Slash backend, since the code was nowhere to be found until today) Cheers, Alex |
From: Marc G. F. <sc...@hu...> - 2009-09-21 18:51:18
|
On Mon, 21 Sep 2009, Chris Nandor wrote: > On Sep 21, 2009, at 11:26, Larson, Timothy E. wrote: > >> I think it comes down to "why deploy two servers if you can do >> one?" Most people these days, if they're going Apache, are going >> Apache2. Apache isn't exactly lightweight. So deploying a second >> heavy server just to run slash seems overkill for something that >> ought to be much more straightforward. That's my take on it. > > I hear you, but that is not a problem for Slashdot, of course. So the > question for *us* -- considering resources we'd have to devote to make > a change -- is of what's inherently better about Apache2 that would > justify the change for us. One thing to note along this thread ... is Apache 1.x even considered "dead" yet? When did 1.3.41 come out? Wasn't it just recently? ---- 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... |
From: Axel B. <ab...@no...> - 2009-09-21 19:50:19
|
On Mon, Sep 21, 2009 at 03:50:43PM -0300, Marc G. Fournier wrote: > One thing to note along this thread ... is Apache 1.x even considered > "dead" yet? Probably not. If a security issue is found in Apache 2.0x and/or 1.3.x, I would guess, there will be new releases. To some degree, the ASF still "recommends" Apache 1.3: http://www.apache.org/dist/httpd/Announcement1.3.html > When did 1.3.41 come out? Wasn't it just recently? If you see "more than one and a half year ago" as recently, yes: 19th of January 2008 according to http://httpd.apache.org/. BTW the same date as the last 2.0.x release, which were both security releases. Regards, Axel -- Axel Beckert - ab...@de..., ab...@no... - http://noone.org/abe/ |
From: Marc G. F. <sc...@hu...> - 2009-09-21 17:16:08
|
The sad thing is that, from what I've been able to determine, the code itself is very well written / stable ... I put up two sites this weekend and the hardest thing for me (and it doesn't matter what 'templating software' I use) was figuring out how to change things visually ... but even that (after a weekend) I'm fairly comfortable with ... My prior desire is to modernize the technology ... newer perl, newer apache, newer mysql, improved postgresql support ... to me, those are the easy parts though ... Does anyone here know anything about GIT that would be interested in helping out? I have no knowledge of it at all ... Someone from the Debian camp pointed out taht lack of Apache 2.x support was a major hindrance from the Debian side ... any out there able to do Debian packages if I can get Apache 2.2 support in there? If there is enough interest in doing this, we could probably get a SlashCode3.0 out the door in <30 days, whose primary focus is just to get the technology up to '09 standards ... and then build from there ... On Mon, 21 Sep 2009, Alexandre Leroux wrote: > > Bonjour Marc, > > I'm the author "Slashcode is dead?" post. With the answers I got (some on my > /. journal, some replies to this list and some personal email), it's clear > that unless something suddenly significantly change, Slashcode is really > dead. I'm obviously not really happy about this, having invested a lot of > efforts in the past 5 years. I still really love the Slash approach and > technology, but there has been no development for years and the Slashdot team > seems unwilling (for various good reasons I guess) to share their latest > versions. > > Also consider that Shane Zatezalo, the main Slash helper outside the slash > team has himself, to my knowledge, stopped using Slash and spending time on > it. The community has degraded to mostly nothing. I am not trying to > discourage you, just to inform you. I of course wish you the best of luck at > reviving Slashcode! > > Meanwhile, I plan to move my small Slashsite (slashgeo.org, about 30,000 > daily hits, 2100 registered members, very few comments) to Drupal. There is > an existing migration method to go from Slash to Drupal. I wish to try that > avenue in the coming months. I may change my mind, but that will happen only > if we can get Slashcode back to modernity (with the Slashdot code?) *and* > reassemble a vivid developers community. > > > Bonne chance Marc ! Keep us updated on your findings. > > Alex :-) > -- > Alexandre Leroux, M.Sc., Ing. > Environnement Canada / Environment Canada > Centre m?t?orologique canadien / Canadian Meteorological Centre > Section de la r?ponse aux urgences environnementales / > Environmental Emergency Response Section > ale...@ec... > > > On 09/19/09 01:07, Marc G. Fournier wrote: >> Just as a follow up, I've email'd the three developers / maintainers of >> Slashcode itself to see if there is some way of handing things off to a new >> crew ... there is just soooooo much in place now, and the project name is a >> known quantity, that the idea of forking and rebranding sounds like such a >> waste of history if we can somehow just revive what is there ... >> >> Will let y'all know if / what I hear back ... *cross fingers* >> >> On Sat, 19 Sep 2009, Marc G. Fournier wrote: >> >>> Started playing with Slashcode this week to setup a news site ... most >>> impressed overall, but didn't clue in how ancient the code is that I'm >>> using ... I should have figured somethign was 'funny' when the PostgreSQL >>> code was alpha, considering that Slashdot ran production on it for awhile >>> ... >>> >>> That said ... someone suggested a code fork, since apparently the >>> developers out 'in-communicado'? >>> >>> I read one person commenting on their company having done plugins (ie. the >>> Geo / mapping stuff), so presumable there is *some* internals knowledge >>> there ... ? >>> >>> I run a hosting company, and already support both Horde and PostgreSQL ... >>> providing resources to a third would be easy, if there were others that >>> were interested ... ? >>> >>> Even just taking the current code and modernizing it (Apache 2.2, MySQL >>> 5.x, Perl 5.8.9 ... I'd be interested in getting PostgreSQL support *out* >>> of alpha myself) would be a huge improvement ... >>> >>> Anyone interested enough to do more then just talk about it ... ? :) >>> >>> Unless Slashcode is trademarked, we could fork / name it something similar >>> ... not too keen on SlashcodeTNG, but something along those lines? >>> >>> Anyone? >>> >>> ---- >>> 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... >>> >>> >>> ------------------------------------------------------------------------------ >>> Come build with us! The BlackBerry® Developer Conference in SF, CA >>> is the only developer event you need to attend this year. Jumpstart your >>> developing skills, take BlackBerry mobile applications to market and stay >>> ahead of the curve. Join us from November 9-12, 2009. Register >>> now! >>> http://p.sf.net/sfu/devconf >>> _______________________________________________ >>> 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... >> >> >> ------------------------------------------------------------------------------ >> Come build with us! The BlackBerry® Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart your >> developing skills, take BlackBerry mobile applications to market and stay >> ahead of the curve. Join us from November 9-12, 2009. Register now! >> http://p.sf.net/sfu/devconf >> _______________________________________________ >> 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... |
From: Larson, T. E. <TEL...@we...> - 2009-09-21 17:21:22
|
> Someone from the Debian camp pointed out taht lack of Apache 2.x > support > was a major hindrance from the Debian side ... any out there able to do > Debian packages if I can get Apache 2.2 support in there? If you can do this, I'd consider doing a pkgsrc package. I've done a number of them for various projects already. > If there is enough interest in doing this, we could probably get a > SlashCode3.0 out the door in <30 days, whose primary focus is just to > get > the technology up to '09 standards ... and then build from there ... I, personally, would love to see Slash running on an Apache 2.x stack. That alone might encourage me to get off my duff and finally build the site I've been pondering for many years now. Tim |
From: Alexandre L. <ale...@ec...> - 2009-09-21 17:32:35
|
On 09/21/09 12:56, Marc G. Fournier wrote: > My prior desire is to modernize the technology ... newer perl, newer > apache, newer mysql, improved postgresql support ... to me, those are > the easy parts though ... Great intentions! :-) That's for the backend, but do you have any plans regarding the modernization of the front-end? What users actually have to deal with? (e.g. the AJAX code that Slashdot now uses) Good luck! Alex |
From: W. S. L. I. <sc...@gu...> - 2009-09-21 17:37:54
|
Is that stuff not in the tarball anymore? On Mon, 2009-09-21 at 13:11 -0400, Alexandre Leroux wrote: > On 09/21/09 12:56, Marc G. Fournier wrote: > > My prior desire is to modernize the technology ... newer perl, newer > > apache, newer mysql, improved postgresql support ... to me, those are > > the easy parts though ... > > Great intentions! :-) That's for the backend, but do you have any plans > regarding the modernization of the front-end? What users actually have > to deal with? (e.g. the AJAX code that Slashdot now uses) > > > Good luck! > > Alex > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Slashcode-general mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-general -- W. Scott Lockwood III <sc...@gu...> LRSE Hosting |
From: Chris N. <pu...@sl...> - 2009-09-21 17:42:24
|
There's no need for newer perl, mysql, or, IMO, Apache. We use MySQL 5 and perl 5.10. We use Apache 1.x, never upgrading because it's not easy (we use a lot of hooks which have changed) and there's no tangible benefit to it. As to the front-end Ajax stuff, that's mostly available in the public repo (which hasn't been updated in awhile but hopefully will be real soon), plugins/Ajax/. A lot of the CSS is not available in the public repo though. On Sep 21, 2009, at 10:11, Alexandre Leroux wrote: > > On 09/21/09 12:56, Marc G. Fournier wrote: >> My prior desire is to modernize the technology ... newer perl, newer >> apache, newer mysql, improved postgresql support ... to me, those are >> the easy parts though ... > > Great intentions! :-) That's for the backend, but do you have any > plans > regarding the modernization of the front-end? What users actually have > to deal with? (e.g. the AJAX code that Slashdot now uses) -- Chris Nandor pu...@po... http://pudge.net/ Slashdot / SourceForge pu...@sl... http://slashdot.org/ |
From: W. S. L. I. <sc...@gu...> - 2009-09-21 17:48:17
|
The fact that almost _no one_ uses it in production anymore is kind of a clue... Even _Debian_ has moved totally away from 1.x for Apache. I realize that you guys don't care so much about the rest of us, as has been stated several times by Rob on many different occasions and posts, but at some point you guys will likely end up having to upgrade, right? Is there any time frame or roadmap for that for /.? I'm really leery of advocating a fork where it's really not necessary, and where the community would gain no benefit, but at the same time that's basically what we'd have to do in order to get it working on Apache 2.x at this point. Support for databases that don't silently eat your data would be nice, too, I.E. PostgreSQL. On Mon, 2009-09-21 at 10:42 -0700, Chris Nandor wrote: > There's no need for newer perl, mysql, or, IMO, Apache. -- W. Scott Lockwood III <sc...@gu...> LRSE Hosting |
From: Marc G. F. <sc...@hu...> - 2009-09-21 18:06:16
|
On Mon, 21 Sep 2009, W. Scott Lockwood III wrote: > The fact that almost _no one_ uses it in production anymore is kind of a > clue... Even _Debian_ has moved totally away from 1.x for Apache. I > realize that you guys don't care so much about the rest of us, as has > been stated several times by Rob on many different occasions and posts, > but at some point you guys will likely end up having to upgrade, right? > Is there any time frame or roadmap for that for /.? I'm really leery of > advocating a fork where it's really not necessary, and where the > community would gain no benefit We'd lose more then gain, actually, as we'd have to build up a whole new community ... better to kick start what is there now, if we can ... > but at the same time that's basically what we'd have to do in order to > get it working on Apache 2.x at this point. Why? Has anyone actually identified *why* the current code doesn't work under Apache 2.2? Is it purely a mod_perl 1.x vs 2.x issue? If so, we can probably work around that easily enough ... > Support for databases that don't silently eat your data would be nice, > too, I.E. PostgreSQL. I will sooooooo volunteer in that department ... I haven't seen the public repo yet, so this might not even be an issue over there ... ---- 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... |
From: Marc G. F. <sc...@hu...> - 2009-09-21 17:52:46
|
On Mon, 21 Sep 2009, Larson, Timothy E. wrote: >> Someone from the Debian camp pointed out taht lack of Apache 2.x >> support >> was a major hindrance from the Debian side ... any out there able to do >> Debian packages if I can get Apache 2.2 support in there? > > If you can do this, I'd consider doing a pkgsrc package. I've done a number of them for various projects already. > >> If there is enough interest in doing this, we could probably get a >> SlashCode3.0 out the door in <30 days, whose primary focus is just to >> get >> the technology up to '09 standards ... and then build from there ... > > I, personally, would love to see Slash running on an Apache 2.x stack. > That alone might encourage me to get off my duff and finally build the > site I've been pondering for many years now. Perusing the lists archive, I got the impression that at some point, someone had put forward mod_perl2 patches ... am I mis-remembering? Or does such a beast exist out there? ---- 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... |
From: Axel B. <ab...@no...> - 2009-09-21 19:54:02
|
On Mon, Sep 21, 2009 at 02:52:34PM -0300, Marc G. Fournier wrote: > > I, personally, would love to see Slash running on an Apache 2.x stack. > > That alone might encourage me to get off my duff and finally build the > > site I've been pondering for many years now. > > Perusing the lists archive, I got the impression that at some point, > someone had put forward mod_perl2 patches ... am I mis-remembering? Or > does such a beast exist out there? http://www.crackerjack.net/slash-2.2.6-modperl2.diff.txt http://www.slashcode.com/article.pl?sid=04/02/19/2144259&tid=9&tid=4 http://www.slashcode.com/submit.pl?op=viewsub&subid=9782¬e=&title=Slash+%26amp%3B+Apache2%2Fmod_perl2%2C+three+years+later%3F Regards, Axel -- Axel Beckert - ab...@de..., ab...@no... - http://noone.org/abe/ |
From: Eric D. <eri...@ja...> - 2009-09-21 17:52:48
|
I think you are wasting your time. About 2 years ago, I migrated my Slashcode sites to Wordpress. This was on an old dual Pentium II server. Not only did Wordpress run faster, it taxed the system less. The only thing hard about it was trying to get the nested comments imported because at that time Wordpress did not support it (it does now). Now I have sites that have a rich plugin community, lots of support, themes, tutorial, and the source code is being developed and still free. I'm not sure why the once Pro-Opensource guys at /. decided to stop giving out their source (if that is true). There are a couple of cool features that Slashdot has, but I rarely go their anymore. Stories are slow, and the conversations are not what they used to be....... But if you have a little bit of SQL skill, you can easily get all your stuff into Wordpress. It is worth it. On Sep 21, 2009, at 9:56 AM, Marc G. Fournier wrote: > > The sad thing is that, from what I've been able to determine, the code > itself is very well written / stable ... I put up two sites this > weekend > and the hardest thing for me (and it doesn't matter what 'templating > software' I use) was figuring out how to change things visually ... > but > even that (after a weekend) I'm fairly comfortable with ... > > My prior desire is to modernize the technology ... newer perl, newer > apache, newer mysql, improved postgresql support ... to me, those > are the > easy parts though ... > > Does anyone here know anything about GIT that would be interested in > helping out? I have no knowledge of it at all ... > > Someone from the Debian camp pointed out taht lack of Apache 2.x > support > was a major hindrance from the Debian side ... any out there able to > do > Debian packages if I can get Apache 2.2 support in there? > > If there is enough interest in doing this, we could probably get a > SlashCode3.0 out the door in <30 days, whose primary focus is just > to get > the technology up to '09 standards ... and then build from there ... > > > > On Mon, 21 Sep 2009, Alexandre Leroux wrote: > >> >> Bonjour Marc, >> >> I'm the author "Slashcode is dead?" post. With the answers I got >> (some on my >> /. journal, some replies to this list and some personal email), >> it's clear >> that unless something suddenly significantly change, Slashcode is >> really >> dead. I'm obviously not really happy about this, having invested a >> lot of >> efforts in the past 5 years. I still really love the Slash approach >> and >> technology, but there has been no development for years and the >> Slashdot team >> seems unwilling (for various good reasons I guess) to share their >> latest >> versions. >> >> Also consider that Shane Zatezalo, the main Slash helper outside >> the slash >> team has himself, to my knowledge, stopped using Slash and spending >> time on >> it. The community has degraded to mostly nothing. I am not trying to >> discourage you, just to inform you. I of course wish you the best >> of luck at >> reviving Slashcode! >> >> Meanwhile, I plan to move my small Slashsite (slashgeo.org, about >> 30,000 >> daily hits, 2100 registered members, very few comments) to Drupal. >> There is >> an existing migration method to go from Slash to Drupal. I wish to >> try that >> avenue in the coming months. I may change my mind, but that will >> happen only >> if we can get Slashcode back to modernity (with the Slashdot code?) >> *and* >> reassemble a vivid developers community. >> >> >> Bonne chance Marc ! Keep us updated on your findings. >> >> Alex :-) >> -- >> Alexandre Leroux, M.Sc., Ing. >> Environnement Canada / Environment Canada >> Centre m?t?orologique canadien / Canadian Meteorological Centre >> Section de la r?ponse aux urgences environnementales / >> Environmental Emergency Response Section >> ale...@ec... >> >> >> On 09/19/09 01:07, Marc G. Fournier wrote: >>> Just as a follow up, I've email'd the three developers / >>> maintainers of >>> Slashcode itself to see if there is some way of handing things off >>> to a new >>> crew ... there is just soooooo much in place now, and the project >>> name is a >>> known quantity, that the idea of forking and rebranding sounds >>> like such a >>> waste of history if we can somehow just revive what is there ... >>> >>> Will let y'all know if / what I hear back ... *cross fingers* >>> >>> On Sat, 19 Sep 2009, Marc G. Fournier wrote: >>> >>>> Started playing with Slashcode this week to setup a news site ... >>>> most >>>> impressed overall, but didn't clue in how ancient the code is >>>> that I'm >>>> using ... I should have figured somethign was 'funny' when the >>>> PostgreSQL >>>> code was alpha, considering that Slashdot ran production on it >>>> for awhile >>>> ... >>>> >>>> That said ... someone suggested a code fork, since apparently the >>>> developers out 'in-communicado'? >>>> >>>> I read one person commenting on their company having done plugins >>>> (ie. the >>>> Geo / mapping stuff), so presumable there is *some* internals >>>> knowledge >>>> there ... ? >>>> >>>> I run a hosting company, and already support both Horde and >>>> PostgreSQL ... >>>> providing resources to a third would be easy, if there were >>>> others that >>>> were interested ... ? >>>> >>>> Even just taking the current code and modernizing it (Apache 2.2, >>>> MySQL >>>> 5.x, Perl 5.8.9 ... I'd be interested in getting PostgreSQL >>>> support *out* >>>> of alpha myself) would be a huge improvement ... >>>> >>>> Anyone interested enough to do more then just talk about >>>> it ... ? :) >>>> >>>> Unless Slashcode is trademarked, we could fork / name it >>>> something similar >>>> ... not too keen on SlashcodeTNG, but something along those lines? >>>> >>>> Anyone? >>>> >>>> ---- >>>> 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... >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Come build with us! The BlackBerry® Developer Conference in >>>> SF, CA >>>> is the only developer event you need to attend this year. >>>> Jumpstart your >>>> developing skills, take BlackBerry mobile applications to market >>>> and stay >>>> ahead of the curve. Join us from November 9-12, 2009. Register >>>> now! >>>> http://p.sf.net/sfu/devconf >>>> _______________________________________________ >>>> 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... >>> >>> >>> ------------------------------------------------------------------------------ >>> Come build with us! The BlackBerry® Developer Conference in >>> SF, CA >>> is the only developer event you need to attend this year. >>> Jumpstart your >>> developing skills, take BlackBerry mobile applications to market >>> and stay >>> ahead of the curve. Join us from November 9-12, 2009. Register >>> now! >>> http://p.sf.net/sfu/devconf >>> _______________________________________________ >>> 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... > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart > your > developing skills, take BlackBerry mobile applications to market and > stay > ahead of the curve. Join us from November 9-12, 2009. Register > now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Slashcode-general mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-general |
From: Marc G. F. <sc...@hu...> - 2009-09-21 18:08:20
|
On Mon, 21 Sep 2009, Eric Dannewitz wrote: > I'm not sure why the once Pro-Opensource guys at /. decided to stop > giving out their source (if that is true). I'm kinda gathering that it isn't so much 'stop giving out their source' as it is 'nobody can find it' ... someone mentioned once about a repo move, an dChris just mentioned a public repo that I've yet to be able to find, that has alot of the more modern stuff ... > There are a couple of cool features that Slashdot has, but I rarely go > their anymore. Stories are slow, and the conversations are not what they > used to be....... I go there daily, and have it RSS'd from my iphone ... but I'm one that grew up with the 2400 modem, so dont' really notice much if a site loads a little slower ... ---- 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... |
From: Marc G. F. <sc...@hu...> - 2009-09-21 17:54:45
|
On Mon, 21 Sep 2009, Alexandre Leroux wrote: > > On 09/21/09 12:56, Marc G. Fournier wrote: >> My prior desire is to modernize the technology ... newer perl, newer >> apache, newer mysql, improved postgresql support ... to me, those are the >> easy parts though ... > > Great intentions! :-) That's for the backend, but do you have any plans > regarding the modernization of the front-end? What users actually have to > deal with? (e.g. the AJAX code that Slashdot now uses) I'm a backend & infrastructure person ... we'll need someone to step up to the plate for bringing in "new features" ... personally, I have 0 experience with AJAX, so it won't be me ... My immediate goal will be to get tthings running on newer backends, so that places that have moved past Apache 1 + MySQL 4.0 can actually use it ... ---- 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... |
From: Chris N. <pu...@sl...> - 2009-09-21 18:00:19
|
On Sep 21, 2009, at 10:48, W. Scott Lockwood III wrote: > The fact that almost _no one_ uses it in production anymore is kind > of a > clue... Even if true that almost no one uses it, a clue leads to something. What is your clue leading to? A flaw in Apache 1.x we should be aware of? > at some point you guys will likely end up having to upgrade, right? Can you give me a reason why we would? No person has ever given me a serious reason why we should use Apache 2, other than what you did: everyone else does it. It would take significant resources, for no significant benefit, so we haven't bothered. > Is there any time frame or roadmap for that for /.? I'm really leery > of > advocating a fork where it's really not necessary, and where the > community would gain no benefit Exactly: there's no significant benefit to going to Apache 2.x. > Support for databases that don't silently eat your data would be nice, > too, I.E. PostgreSQL. MySQL has never eaten our data, silently or otherwise. And we have quite a bit of data. -- Chris Nandor pu...@po... http://pudge.net/ Slashdot / SourceForge pu...@sl... http://slashdot.org/ |
From: Andre-John M. <aj...@sy...> - 2009-09-23 02:12:48
|
On 21-Sep-2009, at 14:00, Chris Nandor wrote: > On Sep 21, 2009, at 10:48, W. Scott Lockwood III wrote: > >> The fact that almost _no one_ uses it in production anymore is kind >> of a >> clue... > > Even if true that almost no one uses it, a clue leads to something. > What is your clue leading to? A flaw in Apache 1.x we should be aware > of? > > >> at some point you guys will likely end up having to upgrade, right? > > Can you give me a reason why we would? No person has ever given me a > serious reason why we should use Apache 2, other than what you did: > everyone else does it. It would take significant resources, for no > significant benefit, so we haven't bothered. The one I would provide is IPv6 support, but then again I am on the IPv6 bandwagon ;) Then again given that libwww maintainers aren't even looking in that direction, Slashcode would have this to resolve first. André |
From: Marc G. F. <sc...@hu...> - 2009-09-21 18:02:13
|
Chris, you live!! On Mon, 21 Sep 2009, Chris Nandor wrote: > There's no need for newer perl, mysql, or, IMO, Apache. We use MySQL 5 > and perl 5.10. We use Apache 1.x, never upgrading because it's not easy > (we use a lot of hooks which have changed) and there's no tangible > benefit to it. Okay, "we use" ...? who is we? I've tried MySQL 5.1 -> 5.0 and finally gave up and went down to 4.0 before I could get the data to load ... it seemed to be just a change in the schema, but hadn't had a chance yet to dive into it ... As to Apache 2 ... I haven't played with it with Slash yet, but ti shouldn't be a whole lot of changes to make it work, should it? Or is it just mod_perl that is the hang up? As for 'newer' perl ... I'm running on 5.8.9, and the only issue I hate was taht the newer Schedule::Cron 0.99 doesn't seem to have a public build_init_queue function, only an internal _build_init_queue ... I had to revert down to 0.97 to get around it, and everything else *seems* to work okay with 5.8.9 ... so, from what I could tell, only that needs a tweak to run with newer Perl, but maybe taht is already fixed in the public repo too? > As to the front-end Ajax stuff, that's mostly available in the public > repo (which hasn't been updated in awhile but hopefully will be real > soon), plugins/Ajax/. A lot of the CSS is not available in the public > repo though. What public repo? I looked for that too ... the site mentions http://cvs.slashcode.com, but that just brought me back to the main page ... What can *we*, as a community, do to get things moving again? Get a new release put out? ---- 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... |
From: Marc G. F. <sc...@hu...> - 2009-09-21 18:10:12
|
On Mon, 21 Sep 2009, Chris Nandor wrote: > MySQL has never eaten our data, silently or otherwise. And we have > quite a bit of data. Slashdot is back on MySQL? I know it went from MySQL -> PostgreSQL -> DB2(?) ... didn't know it went back to MySQL yet again ... As for 'eating data' ... I'm not much into MySQL myself, but I've never heard of it 'eating data' before either ... ---- 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... |
From: Eric D. <eri...@ja...> - 2009-09-21 18:52:00
|
Really? I don't think slash ever moved from mysql. As I remember it, they had some support for postgresql but don't ever recall them moving slash to it --- send out and aboot on my iPhone --- On Sep 21, 2009, at 11:10 AM, "Marc G. Fournier" <sc...@hu...> wrote: > On Mon, 21 Sep 2009, Chris Nandor wrote: > >> MySQL has never eaten our data, silently or otherwise. And we have >> quite a bit of data. > > Slashdot is back on MySQL? I know it went from MySQL -> PostgreSQL -> > DB2(?) ... didn't know it went back to MySQL yet again ... > > As for 'eating data' ... I'm not much into MySQL myself, but I've > never > heard of it 'eating data' before either ... > > ---- > 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... > > --- > --- > --- > --------------------------------------------------------------------- > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart > your > developing skills, take BlackBerry mobile applications to market and > stay > ahead of the curve. Join us from November 9-12, 2009. Register > now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Slashcode-general mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-general |
From: Marc G. F. <sc...@hu...> - 2009-09-21 18:24:50
|
On Mon, 21 Sep 2009, Marc G. Fournier wrote: > I'm a backend & infrastructure person ... we'll need someone to step up > to the plate for bringing in "new features" ... personally, I have 0 > experience with AJAX, so it won't be me ... Wow ... thanks to Chris' comment about public repo, went searching a bit, and the Ajax code looks to have been added around Mar '08 ... The problem isn't that the code isn't there, the problem is its never been released ... Chris, any chance of getting a new release worked up? I've gotta figure out this GIT software and try out the repo code ... Public Repo: http://github.com/scc/slash AJAX Plugin: http://github.com/scc/slash/tree/master/plugins/Ajax/ As nice as Apache2.x and beyond would be nice, I don't think that lack of that is as much as a dis-service to the community as not getting a new release out on Apache 1.x ... :) ---- 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... |