Re: [Slashcode-general] Jumping in here late ... Slashcode is Dead ...

[Chris N. <pu...@sl...>]

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/