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

[mark burdett]

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.  meanwhile, install 
profiles will soon be available for download as tarballs which include
all required modules.
it seems ideal to use (and contribute to) drupal.org infrastructure 
rather than building parallel systems.

--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