Menu
▾
▴
slashcode-general — This is the general discussion list. Install questions welcome.
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
(30) |
Mar
(123) |
Apr
(188) |
May
(90) |
Jun
(68) |
Jul
(129) |
Aug
(72) |
Sep
(97) |
Oct
(99) |
Nov
(168) |
Dec
(35) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(75) |
Feb
(55) |
Mar
(104) |
Apr
(49) |
May
(12) |
Jun
(11) |
Jul
(47) |
Aug
(104) |
Sep
(14) |
Oct
(26) |
Nov
(31) |
Dec
(10) |
| 2003 |
Jan
(78) |
Feb
(76) |
Mar
(47) |
Apr
(30) |
May
(19) |
Jun
(36) |
Jul
(48) |
Aug
(43) |
Sep
(54) |
Oct
(25) |
Nov
(79) |
Dec
(39) |
| 2004 |
Jan
(43) |
Feb
(14) |
Mar
(17) |
Apr
(15) |
May
(18) |
Jun
(20) |
Jul
(7) |
Aug
(30) |
Sep
(49) |
Oct
(17) |
Nov
(14) |
Dec
(72) |
| 2005 |
Jan
(55) |
Feb
(27) |
Mar
(34) |
Apr
(15) |
May
(8) |
Jun
(23) |
Jul
(7) |
Aug
(19) |
Sep
(3) |
Oct
(44) |
Nov
(3) |
Dec
|
| 2006 |
Jan
(20) |
Feb
(5) |
Mar
(8) |
Apr
(12) |
May
(16) |
Jun
(22) |
Jul
(39) |
Aug
(65) |
Sep
(4) |
Oct
(11) |
Nov
|
Dec
(5) |
| 2007 |
Jan
(2) |
Feb
(2) |
Mar
(8) |
Apr
(3) |
May
(28) |
Jun
(6) |
Jul
(3) |
Aug
(9) |
Sep
(15) |
Oct
|
Nov
(12) |
Dec
(2) |
| 2008 |
Jan
(3) |
Feb
(14) |
Mar
|
Apr
(4) |
May
|
Jun
(12) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
| 2009 |
Jan
|
Feb
(2) |
Mar
(4) |
Apr
|
May
|
Jun
(14) |
Jul
|
Aug
(1) |
Sep
(66) |
Oct
(21) |
Nov
|
Dec
(1) |
| 2010 |
Jan
(2) |
Feb
(2) |
Mar
(2) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
(100) |
Mar
(17) |
Apr
(1) |
May
(1) |
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
|
From: Marc G. F. <sc...@hu...> - 2009-09-22 00:56:10
|
On Mon, 21 Sep 2009, Shane Zatezalo wrote: > I have "finish, clean and put up on github" on my todo list for it, when > there's this thing called "Freetime" that I'm not finding too often. > Maybe someday. Would you be willing to share these in their current form, without the 'clean'? Might help get those using the "old code" to upgrade to the "new code"? ---- 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-22 00:48:32
|
Chris, I figure you do, else you guys wouldn't be using it ... how does one checkout the 'new code' to install? I'm an old CVSer, barely know enough to hurt myself with SVN, never touched git ... ---- 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 21:39:11
|
On Mon, 21 Sep 2009, Chris Nandor wrote: > Briefly, the technical reason is that we had the Slashdot theme as a > separate module in CVS, but Git is not as easy to work with that way. > So now we have it all in one repo, and we don't want that stuff > public. We have a script to make a new repo without that stuff in it, > to push to a public server, it just needs setting up, which is what > we're working on. Sounds cool ... I got from one of your previous was that the Slashdot/Slashcode code bases were effectively forked, but from this, it sounds like the plan is to *more or less* merge them back together again (minus the slashdot theme, of course) ... Is that correct? ---- 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 21:09:30
|
On Sep 21, 2009, at 12:41, Axel Beckert wrote: > Well it could enlarge the community of developers. But I guess that's > nothing important to aspire. In our business model, no, it's not. Which is why I said I am plenty willing to help other people find a way to do things like Apache2 and Postgres support, releases, and so on. I just can't commit significant time or resources to it. -- Chris Nandor pu...@po... http://pudge.net/ Slashdot / SourceForge pu...@sl... http://slashdot.org/ |
|
From: Chris N. <pu...@sl...> - 2009-09-21 21:09:03
|
Briefly, the technical reason is that we had the Slashdot theme as a separate module in CVS, but Git is not as easy to work with that way. So now we have it all in one repo, and we don't want that stuff public. We have a script to make a new repo without that stuff in it, to push to a public server, it just needs setting up, which is what we're working on. On Sep 21, 2009, at 12:49, Shane Zatezalo wrote: > I think what he's referring to, is the fact that when they moved to > github they were pushing to the public git-repo for a spell, but then > that stopped and really hasn't ever started up with any regularity (to > my knowledge, it's been a long time since I looked). > > Where as, when it used Sourceforge (before the github move) the > updates were about weekly if not quicker with T_ and R_ tags ensuing > to match the 'updates' file/information. -- Chris Nandor pu...@po... http://pudge.net/ Slashdot / SourceForge pu...@sl... http://slashdot.org/ |
|
From: Shane Z. <sh...@lo...> - 2009-09-21 20:54:08
|
On Sep 21, 2009, at 2:02 PM, Marc G. Fournier wrote: > [...] >> 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 > ... http://github.com/scc/slash I think what he's referring to, is the fact that when they moved to github they were pushing to the public git-repo for a spell, but then that stopped and really hasn't ever started up with any regularity (to my knowledge, it's been a long time since I looked). Where as, when it used Sourceforge (before the github move) the updates were about weekly if not quicker with T_ and R_ tags ensuing to match the 'updates' file/information. Shane |
|
From: Shane Z. <sh...@lo...> - 2009-09-21 20:10:11
|
On Sep 21, 2009, at 3:19 PM, Axel Beckert wrote: > Hi, > > great to see that not all people lost hope. :-) > > On Mon, Sep 21, 2009 at 01:56:43PM -0300, 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 ... > > There is a patch from 2004 at > http://www.crackerjack.net/slash-2.2.6-modperl2.diff.txt against the > last > stable release 2.2.6. > > Another thing Slashcode needs (at least WRT the public) is a release > management. Proper stable releases and changelogs. This will help > people who package software for distributions a lot. We did come up with a system for automated updates. We used it on our slash-hosting environment for years; We even upgraded a number of clients from the pre (2.2.6) to cvs-HEAD (at the time) using the tools. A few years ago I think I did package them up and sent them (or bits and pieces) to someone from the OSTG Slashcode crew for perusal. I don't honestly recall what ever happened with it; I'm fairly certain some of the patches I wrote/wanted/submitted to the Slash::Install module made it into the public tree. Some didn't. (An example was recursive slash.conf calls, I think it turned out modding the installer was a bit more of a task to make it work then what I had time to contribute towards that). The update system's code, while functional, was just never finished "aka cleaned up and releasable" by me. It "worked for us" (in about 2 minutes time we were able to update an entire slash-farm on a weekly basis) and that was enough, and we had to move on towards other money making ventures. I have "finish, clean and put up on github" on my todo list for it, when there's this thing called "Freetime" that I'm not finding too often. Maybe someday. Shane |
|
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: 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: Axel B. <ab...@no...> - 2009-09-21 19:41:34
|
On Mon, Sep 21, 2009 at 11:00:04AM -0700, Chris Nandor wrote: > > at some point you guys will likely end up having to upgrade, right? > > Can you give me a reason why we would? When the ASF decides to stop security support for the 1.3 series. Except if you plan to do that yourself then... No idea how the ASF thinks about the future of Apache 1.3 (found no kind of roadmap on httpd.apache.org), but I would expect that 1.3 will die once and 2.x or later will continue. > 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. You're right WRT to technical issues: If Apache 1.3 works and you compile your own Apache, why bother? > Exactly: there's no significant benefit to going to Apache 2.x. Well it could enlarge the community of developers. But I guess that's nothing important to aspire. 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: Chris N. <pu...@sl...> - 2009-09-21 19:38:39
|
We are open to input, but our schedules our tight. We can't just accept anything. And as noted in another post, it's not just running Apache2 code that works, it's configuring and managing Apache2 servers, which is not an insignificant tax on our resources. On Sep 21, 2009, at 11:48, Larson, Timothy E. wrote: > So it's really, "Why should Slashdot (since that's who is putting > resources into it) do this work for nothing?" That leads to the > question, how open are slash developers "on the inside" to input > "from the outside"? If someone were to do the heavy lifting, would > it be accepted? Would /. conceivably switch over to the new version > and run Apache2? -- Chris Nandor pu...@po... http://pudge.net/ Slashdot / SourceForge pu...@sl... http://slashdot.org/ |
|
From: Chris N. <pu...@sl...> - 2009-09-21 19:36:31
|
On Sep 21, 2009, at 11:59, Marc G. Fournier wrote: > Let me try with the latest public repo ... is there an 'upgrade > path' for upgrading from 2.2.6 -> repo? Or should it just work if I > untar over the old, or ... ? There's some scripts in there. It's a separate topic of discussion though. Let us just try to get the code up. :-) > So, what is at http://www.slashcode.com is literally what is running > on slashdot.org? No. It was until sometime this year or late last year. Basically, we would test all our code on slashcode.com/use.perl.org (which is the same machine/code) before putting it on Slashdot. But we moved to using internal virtualized sandboxes, and so this function was no longer necessary, and due to a shift in our development that had us doing a lot of work on Slashdot-specific CSS tied to functionality, it became too much of a burden to continue that path. So, for years that code was in sync with Slashdot, but as of this year, it's not. >> If someone is interested in this, the only thing I'd request is >> that you discuss the name with us before releasing ... the company >> owns the naming rights to some degree and I don't know how to deal >> with that. But the rest of the code is open, so knock yourself out. > > Rather contribute into the existing project vs do a parallel > development, but I'm gathering that that isn't possible? I don't want our slowness to get in the way of other people doing releases. So *maybe* we could have someone do releases on SF.net under the slashcode project. I don't know. But if not, then it seems like we'd probably just end up getting in other peoples' way. > so the only *major* issue I can see (if I'm understandign things > right) is doing new releases ... we'd have to fork to do that, > wouldn't we? No, what I described is just having a wrapper around our repo to do releases with. I wouldn't consider that a fork at all, even if it added other things to our repo. -- Chris Nandor pu...@po... http://pudge.net/ Slashdot / SourceForge pu...@sl... http://slashdot.org/ |
|
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: Axel B. <ab...@no...> - 2009-09-21 19:19:18
|
Hi, great to see that not all people lost hope. :-) On Mon, Sep 21, 2009 at 01:56:43PM -0300, 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 ... There is a patch from 2004 at http://www.crackerjack.net/slash-2.2.6-modperl2.diff.txt against the last stable release 2.2.6. Another thing Slashcode needs (at least WRT the public) is a release management. Proper stable releases and changelogs. This will help people who package software for distributions a lot. > Someone from the Debian camp pointed out taht lack of Apache 2.x support > was a major hindrance from the Debian side ... That was me, the last maintainer of slash in Debian. > any out there able to do Debian packages if I can get Apache 2.2 > support in there? I would at least have a look at it, but I won't promise anything... > 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 ... Sounds promising, but when I remember my last (project internal) Slashcode hacking party, I'm not that optimistic. (And I'm usually more the optimist. But OTOH that was many, many years ago and we all were young and unexperienced... ;-) Regards, Axel -- Axel Beckert - ab...@de..., ab...@no... - http://noone.org/abe/ |
|
From: Marc G. F. <sc...@hu...> - 2009-09-21 18:59:44
|
On Mon, 21 Sep 2009, Chris Nandor wrote: > On Sep 21, 2009, at 11:02, Marc G. Fournier wrote: > >> Chris, you live!! > > I replied on Sept. 18 to your private email last week. Didn't see it ... have to check my spam filters, might have quarantined it ... > It could be there's problems with the old data dumps. I don't know. The > code works fine. Let me try with the latest public repo ... is there an 'upgrade path' for upgrading from 2.2.6 -> repo? Or should it just work if I untar over the old, or ... ? > We hook into many parts of the Apache 1.x cycle, and it's changed > significantly in 2.x. (Not to mention, of course, being a completely > different type of server, we'd have to expend significant resources into > figuring out how best to configure and deploy the servers for our needs. > No small task there.) As someone else asked, if the work was down outside of slashdot, could it be incorporated into http://www.slashcode.com? > I am not sure where that function would be called, or what that has to > do with different perl versions. Again, let me test on the newer code ... I suspect that its something that was long fixed ... > Yeah the URLs changed. Right now it is on (and out of date) on github. > I want to put it on SourceForge too. And I want it done this week or > next. Stay tuned. It's something we've pushed to fix up in the last > month or so, and I hope it's done soon. Great news, thanks ... > I do not anticipate any releases. We simply do not have the resources. So, what is at http://www.slashcode.com is literally what is running on slashdot.org? "Community involvement" in that code base (either as code, or releases) isn't possible? > If someone is interested in this, the only thing I'd request is that you > discuss the name with us before releasing ... the company owns the > naming rights to some degree and I don't know how to deal with that. But > the rest of the code is open, so knock yourself out. Rather contribute into the existing project vs do a parallel development, but I'm gathering that that isn't possible? > Most of what is being discussed would not require a fork; even Apache2 > support, being mostly in a few modules, could be perhaps designed as > drop-in replacements (and patches to the main codebase requiring a > small amount of work to such ends would be welcome). Doing any fork would be very unappealing ... and I suspect that, based on what I've heard here, if the main repo has what alot of ppl thought were missing already, its only teh Apache 2 that seems to be at issue ... so the only *major* issue I can see (if I'm understandign things right) is doing new releases ... we'd have to fork to do that, wouldn't we? Or is there something else we can do to get past the old 2.2.6 and some new code in a release package? ---- 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: Michael L. <mik...@ma...> - 2009-09-21 18:54:01
|
On Sep 21, 2009, at 1:50 PM, Marc G. Fournier wrote: > 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... > > ------------------------------------------------------------------------------ > 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: 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: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: Marc G. F. <sc...@hu...> - 2009-09-21 18:49:53
|
On Mon, 21 Sep 2009, Chris Nandor wrote: > It never left MySQL. It's always been MySQL-only. We had some very > basic Postgres support, but our site never ran on Postgres. And we > never touched DB2. I think SourceForge.net may have followed the route > you described; perhaps that is what you are thinking of. I am not sure > what SF.net is running now. Ack, yes, my confusion ... it was sourceforge that switched DBs ... ---- 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 18:48:44
|
> > 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. So it's really, "Why should Slashdot (since that's who is putting resources into it) do this work for nothing?" That leads to the question, how open are slash developers "on the inside" to input "from the outside"? If someone were to do the heavy lifting, would it be accepted? Would /. conceivably switch over to the new version and run Apache2? Tim |
|
From: Chris N. <pu...@sl...> - 2009-09-21 18:47:34
|
On Sep 21, 2009, at 11:02, Marc G. Fournier wrote: > Chris, you live!! I replied on Sept. 18 to your private email last week. > 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 ... It could be there's problems with the old data dumps. I don't know. The code works fine. > 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? We hook into many parts of the Apache 1.x cycle, and it's changed significantly in 2.x. (Not to mention, of course, being a completely different type of server, we'd have to expend significant resources into figuring out how best to configure and deploy the servers for our needs. No small task there.) > 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? I am not sure where that function would be called, or what that has to do with different perl versions. > 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 > ... Yeah the URLs changed. Right now it is on (and out of date) on github. I want to put it on SourceForge too. And I want it done this week or next. Stay tuned. It's something we've pushed to fix up in the last month or so, and I hope it's done soon. > What can *we*, as a community, do to get things moving again? Get a > new > release put out? I do not anticipate any releases. We simply do not have the resources. That said, if people wanted to make releases based on our code, we'd be willing to provide some basic support. If it were me working outside the Slashdot team making a release -- I've done something like this in the past, with MacPerl -- I'd make the slash repo a subdirectory of my release directory (or vice versa), so I can keep those sources up to date separately, and then add whatever else I wanted to the release in the separate directories: themes, Postgres support, whatever. If someone is interested in this, the only thing I'd request is that you discuss the name with us before releasing ... the company owns the naming rights to some degree and I don't know how to deal with that. But the rest of the code is open, so knock yourself out. Most of what is being discussed would not require a fork; even Apache2 support, being mostly in a few modules, could be perhaps designed as drop-in replacements (and patches to the main codebase requiring a small amount of work to such ends would be welcome). -- Chris Nandor pu...@po... http://pudge.net/ Slashdot / SourceForge pu...@sl... http://slashdot.org/ |
|
From: Chris N. <pu...@sl...> - 2009-09-21 18:44:35
|
On Sep 21, 2009, at 11:10, Marc G. Fournier 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 ... It never left MySQL. It's always been MySQL-only. We had some very basic Postgres support, but our site never ran on Postgres. And we never touched DB2. I think SourceForge.net may have followed the route you described; perhaps that is what you are thinking of. I am not sure what SF.net is running now. > 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/ Feel free to look there, but that was a temporary place. Now that SF.net has Git, we are probably moving back to SF.net for our public repo. -- Chris Nandor pu...@po... http://pudge.net/ Slashdot / SourceForge pu...@sl... http://slashdot.org/ |
|
From: Chris N. <pu...@sl...> - 2009-09-21 18:41:46
|
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. -- Chris Nandor pu...@po... http://pudge.net/ Slashdot / SourceForge pu...@sl... http://slashdot.org/ |
|
From: Larson, T. E. <TEL...@we...> - 2009-09-21 18:28:29
|
> 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 think the attitude has been, "the repo is public, we tag stable points, whatever you grab is your release". Tim |
19 messages has been excluded from this view by a project administrator.
