[imc-scotland-discussion] meetings

[LA]

O/H Tom Morton ??????:
> chris wrote:
>   
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Meetings. I think one is overdue, more so me being at one. I am in
>> Edinburgh over xmas so would like to meet folk for a bit chat.
>>     
I'm off Edinburgh beginning from the day after tomorrow, and I am sad 
there has been no meeting for the short time I was here. I've said, and 
I insist on it, that regular meetings are significant for the well-being 
of any collective. So I'd say do it, and even try for decentralized 
meetings, if there is a need for that.
>> My technical skills are improving slowly but from a very low base and
>> low knowledge of the existing systems. Seems there's 3 options though:
>> * keep on with DadaIMC
>>     
>
> for the time being :)
>   
I agree. As you might have read, Klaus, one of the volunteering 
maintainers of our web-server, tweaked the code of DadaIMC for letting 
it function properly with PHP5, which it didn't. So let's hope that no 
big issues will arise.

I have heard that some of the American websites still maintain Dada. 
There may be people out there who do maintain the code. I will post a 
question and let you know of the feedback.
>   
>> * join the Drupal IMC process
>>     
>
> Here is the drupal IMC thing:
>
> http://docs.indymedia.org/view/Devel/ImcDrupalDevDrupal5
>
> I don't know if anyone uses it in the form available on that site. There 
> are other drupal IMCs that are configured completely differently, with 
> different custom modules, etc. For example http://indymedia.be
>
> In my opinion the ImcDrupalDevDrupal5 work is insufficient to make a 
> replacement for Dada as it stands. It lacks some of the more important 
> features like WYSIWYG (what you see is what you get) article editing, 
> youtube style handling of videos, some editorial policy stuff, ...
>
>   
Yes, I think there is something being organised in the CMS group that 
gets in contact through imc-cms {at} lists.indymedia.org and #cms 
irc.indymedia.org channel. I would say we should work together with 
existing work-group so as we take advantage of the existing code and 
have a more wide range of code contributors. We should not only develop 
new modules, but try to push the existing Drupal modules to support the 
functions we want. I am also interested in building stuff for this 
project, so if I know more I will try to let you know.
> When I get out of this awful christmas job of mine and have free time 
> again I'd like to work on these and feed the results back into the 
> drupal IMC dev. It may result in something useful.
>
>   
>> * join Ireland & Bristol with Oscait
>>     
>
> Oscait might be worth a look. however, the IMC tech people decided with 
> good reason to abandon the home-grown approaches like mir, sfactive, 
> dada and instead climb on the shoulders of an open source CMS. This has 
> many advantages. we don't need to maintain the universal low-level code 
> which makes up the bulk of a CMS - only the small custom modules we 
> write. We get access to the wealth of modules people have written for 
> drupal. eg: I was looking for a solution to the youtube video problem. i 
> searched for 'flash video' in the drupal module list and it turned out 
> someone had already solved the problem.
>   
I completely aggree. Athens IMC has already been burnt twice by codes 
which were developped with individuals once and stopped being maintained 
after a while. Similar the case for dada I think.
>   
>> Discussions like these can be hellish, though. I suggest that we need to
>> think hard and come up with a list of reuirements, improvements, wishes
>> etc. Everything that we want our IMC 2.0 ;) to do. I've started one but
>> don't have time to type it up this evening.
>>     
>
> yes that would be useful
>
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.indymedia.org/pipermail/imc-scotland-discussion/attachments/20071218/d5e901b3/attachment.htm