[Imc-drupal-dev] relaunch ourselves: all/modules

Wed Dec 5 05:43:14 PST 2007

hi,
i'm new to this list and glad to discover all this drupal knowledge.

and i'm involved in a dutch-indy-related group (http://open-radio.nl)  
who have offered to re-launch radio.indymedia.org using an updated  
version (drupal 6.0) of our drupal/icecast/mplayer open-publishing  
radio stream.

it seems to me the re-launch could be a good 'test case' for the  
results of this thread... we're probably aiming for around february.

ciao ciao
levin

Quoting jonhattan <jonhattan at faita.net>:

> clara escribió:
>> Hi,
>> maybe I get that wrong - but the update status module only gives your
>> information about the modules you already got.
>>
> Yes. The starting point of this thread was:
>
> 1. must to complete a list of modules, at
> https://docs.indymedia.org/view/Devel/ImcDrupalDevModules
>
> 2. find a way to easily manage common modules for all IMCs.
> update_status, cvs_deploy, drush are part of it.
>
>> What might be more interesting at this stage is already the questions
>> which modules the different IMCs are using, or even better using to
>> achive what. I suppose there are both different solutions for similar
>> problems around as well as also different aims/ideas/traits that
>> collectives want for their sites.
>>
> In the modules page I've put a group of mods for comments and moderation.
>
> What about starting a thread for each area of a typical IMC, to agree a
> list of modules and to generate doc based on them ? Perhaps can we
> assign ourselves a topic and start a thread with some alternatives to
> discussion on ?
>
> a first list of Areas / Topics :
>
> * image
> * audio
> * video
> (those three in separate threads to fine grane, they're long enough to
> not be a generalistic "multimedia" topic)
>
> * moderation
> * spam / anti-bot / captcha
> * accesibility
> * calendar / events
> * easy admin & editing (javascript, admin facilities, wysiwyg,...)
> * theming, css, layout, customization.
> * syndication.
> * l10n / i18n.
>
>
>
> -- jonhattan
>
>
>> maybe a wiki might be easier to get this knowledge together because it
>> will easily allow for annotations.
>> And from that being able to make a typical IMC setup that gives an
>> easier start to new drupal sites.
>>
>> greetings
>> antje
>>
>> Bruno De Bondt wrote:
>>
>>> jonhattan wrote:
>>>
>>>> mark burdett escribiÃ³:
>>>>
>>>>
>>>>> Hi, i still depend on svn or other scm for all my projects,
>>>>> but, the drupal infrastructure could suit us quite well for maintaining
>>>>> a large number of sites: the update_status module will tell you if your
>>>>> modules are out of date, and prompt you to upgrade.
>>>>>
>>>>>
>>>> Yes, update_status is very useful, but it only handles releases as
>>>> 5.x-x-x. Some maintainers recommend you to use the -dev tarball, that
>>>> can't be handled by update_status.
>>>>
>>>> Perhaps I've been misunderstood. Although update_status tell you about
>>>> current versions, you still have to manually download, untar and do
>>>> update.php. I propose to download & untar in a shared folder and any imc
>>>> could update it's modules just downloading (ftp, svn up,...) this shared
>>>> folder to her server.
>>>>
>>>>
>>> Perhaps the CVS deploy module could help (http://drupal.org/node/151342)
>>> ? Haven't used it myself though.
>>>
>>> -- bruno
>>>
>>>
>>>
>>>
>>>> We also have specific patches for indymedia, such as the ones involved
>>>> with "hidden" contents or anonymization, that could be applied in that
>>>> shared folder.
>>>>
>>>>
>>>>
>>>>>  meanwhile, install
>>>>> profiles will soon be available for download as tarballs which include
>>>>> all required modules.
>>>>>
>>>>>
>>>>>
>>>> are you talking about drupal or indymedia?
>>>> if about drupal, is there a way to automagically generate a profile or
>>>> must we go through
>>>> http://drupal.org/node/67921 ?
>>>> if about indymedia, what are all required modules? :P
>>>>
>>>>
>>>>
>>>>> it seems ideal to use (and contribute to) drupal.org infrastructure
>>>>> rather than building parallel systems.
>>>>>
>>>>>
>>>>>
>>>> My proposal doesn't need to drop a line of code, is a way to manage
>>>> existing code updating. It's made by hand, no automation, but it's made
>>>> once and no as many times as drupal imc's there be.
>>>>
>>>> Anyway, I'm doing imc-canarias drupal in theese days, adding all the doc
>>>> to  ImcDrupalDev, and my all/modules will be shared for those wo don't
>>>> want to go through downloading and untaring a bunch of modules.
>>>>
>>>>
>>>> jonhattan
>>>>
>>>>
>>>>
>>>>> --mark
>>>>>
>>>>> On Sun, 02 Dec 2007 21:37:17 +0000, jonhattan wrote:
>>>>>
>>>>>
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> time by time a new drupal indysite is launched, each one is built from
>>>>>> scratch.
>>>>>> We still haven't a comprehensive list of modules nor a installation
>>>>>> profile, but a lot of individual efforts on commenting it's own work on
>>>>>> a external wiki or blog. It's good to have the work documented, it's
>>>>>> better to merge (not group ;)) documentation in a common place:
>>>>>> ImcDrupalDev.
>>>>>>
>>>>>> I think a common project that can sum our disperse efforts could be to
>>>>>> complete the modules list [1] with all modules that can be part of a
>>>>>> common indysite instance. We know drupal has tons of modules, let's
>>>>>> select the key ones.
>>>>>> Also I think it will be very useful to have a "shared folder" (sorry my
>>>>>> MS expression :P) to put the last version of modules. This shared folder
>>>>>> could be a repository, collaborative managed and providing an easy
>>>>>> method to update local imc's via a simple svn/cvs/.. update. Instead of
>>>>>> each one manually updating 20+ modules on own servers, let's share the
>>>>>> effort.
>>>>>>
>>>>>>
>>>>>>
>>>>>> [1] https://docs.indymedia.org/view/Devel/ImcDrupalDevModules
>>>>>>
>>>>>>
>>>>>> jonhattan,
>>>>>> imc-canarias
>>>>>> _______________________________________________
>>>>>> Imc-drupal-dev mailing list
>>>>>> Info: https://docs.indymedia.org/view/Devel/ImcDrupalDev
>>>>>> Imc-drupal-dev at lists.indymedia.org
>>>>>> http://lists.indymedia.org/mailman/listinfo/imc-drupal-dev
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>> _______________________________________________
>>>> Imc-drupal-dev mailing list
>>>> Info: https://docs.indymedia.org/view/Devel/ImcDrupalDev
>>>> Imc-drupal-dev at lists.indymedia.org
>>>> http://lists.indymedia.org/mailman/listinfo/imc-drupal-dev
>>>>
>>>>
>>>>
>> _______________________________________________
>> Imc-drupal-dev mailing list
>> Info: https://docs.indymedia.org/view/Devel/ImcDrupalDev
>> Imc-drupal-dev at lists.indymedia.org
>> http://lists.indymedia.org/mailman/listinfo/imc-drupal-dev
>>
>>
>
> _______________________________________________
> Imc-drupal-dev mailing list
> Info: https://docs.indymedia.org/view/Devel/ImcDrupalDev
> Imc-drupal-dev at lists.indymedia.org
> http://lists.indymedia.org/mailman/listinfo/imc-drupal-dev
>