[imc-sf-active] announcement: CMS proposal and kick off ircmeeting

[kwadronaut at autistici.org]

Hello,

Sorry for this english-only e-mail, french or dutch on request.
I appreciate the proposals and ideas, i have 2 concerns though:

1. Wouldn't it be good to set up a seperate list for this proposal (if  
it goes through in some form)? I suspect that not every techie is on  
imc-sf-active and the general techlist might not appreciate the  
shitload of mails that will be send about it.

2. as far as i understood, correct me if i'm wrong: we would first  
discuss if we are going to look for an outside cms. Maybe we walk out  
of the meeting having decided that we will rather look at frameworks  
or specific languages to redo all the work but now concentrated and  
build one specific indymedia-codebase or leave everything like it is.  
My point is: before proposing/analysing a particular cms, it could be  
practical to first think if we do accept the proposal (personally i  
do) and second to think of how to organise that in a hopefully  
efficient way.

I don't want to scare people away from documenting or telling their  
experiences with a particular cms nor do i want to install  
bureaucracy, just trying to get focussed a bit.

-
kwadronaut



Quoting "devin at nacredata.com" <devin at nacredata.com>:

> Completely agree. I had client loose their phpNuke site completely a few
> years after I set it up for them and they didn't keep up with updates.
>
> Has anyone looked at the Slash code base? It's perl, which I like a lot, and
> it has some pretty nice rating and meta-moderating features.
>
> -- devin
>
>
>
> --- Quinten Steenhuis <quinten at andrew.cmu.edu> wrote:
>>
>> This proposal sounds sensible. Unfortunately I won't be able to attend
>> the meeting, but I wanted to make sure that security concerns are also
>> addressed. Uniformity of CMS can be dangerous if it makes it easier to
>> coordinate an attack against all IMCs at once. Currently the small usage
>> base for the major IMC codebases provide a less-tempting target for
>> hackers than Mambo, etc, except politically motivated ones who are
>> usually only a short-term nuisance. Of course these more standard CMS
>> packages do get frequent updates, but security is definitely something
>> that should be taken into account. Perhaps it would make sense to choose
>> 2 or 3 different CMSs, and add some scripts to lock down or strip out
>> unused pieces of the codebases that could make the software more
> vulnerable.
>>
>> Pseudo Punk wrote:
>> > Hi,
>> >
>> > During the techmeet in Sao Paulo, Max, Ryan and a number of other
>> > Indymedia techies and developers have brooded on a proposal
>> > for the future of indymedia CMSes:
>> >
>> > http://techmeet.sarava.org/English/CMSProposal
>> >
>> > The basic idea is to move away from developing indymedia-specific
>> > CMSes and instead pick a general CMS and customize it for indymedia.
>> > This way, we hope to reduce the work load and improve indymedia
>> > sites in general.
>> >
>> > The next step in moving this proposal proposal forward will be an
>> > irc meeting on september 10th 2006, at 1700 UTC in the #cms channel
>> > on http://chat.indymedia.org
>> >
>> >
>> >
>> >
>> > Greetings,
>> >
>> >
>> > Bart
>> > _______________________________________________