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

[Bruno De Bondt]

http://groups.drupal.org/indymedia ?

IMHO it would be nice to do it there, to 'integrate' with wider Drupal
development, to show to the Drupal community what we're doing, to get 
(non-Indy) people to join in, ... I even has wiki pages :)

-- bruno

ekes wrote:
> jonhattan wrote:
>   
>>> 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.
>>>       
>
> Can I just second this.
>
> It's a shame that docs.indy was flakey when lots of the Drupal Dev
> started. Now it's up and seems to be more stable it's ideal. Somewhere
> else could also be cool. Working on a *.drupal.org location would be ok
> too, but really we should agree on one place rather than the wide
> selection we presently have. Personal preference is to a wiki for that
> sort of documentation/organisation though.
>
> mark burdett wrote:
>   
>> the update_status module will tell you if your 
>> modules are out of date, and prompt you to upgrade. 
>>     
>
> This could be a really useful module. It's nice to know when modules
> have upgrades. Generally it's most important is know when they are
> security issues and the best way for that is to be on the security
> announcements list/feed. These upgrades are important.
> Within contrib there has to be a caution statement for update_status -
> sorry if this is obvious - it's called test first! Just updating when
> update_status notices 'there is a new release' can cause problems. This
> is because some projects (and I can point if it's needed, a non-small
> one springs immediately to mind) are not so clear about making really
> good stable releases, and even if they are stable they may break as
> there are no real version dependencies with other modules.
>
> and mark talked about:
>   
>> install 
>> profiles will soon be available for download as tarballs which include
>> all required modules.
>>     
>
> This is something that just should happen! At a base level it can be
> done from any of us just making an install profile - and someone who
> just has the time to do it should! Realistically the way to organise it
> after that is to have a wiki/documentation/list discussion to feed into
> what should feed be the 'best' profile...
>
> jonhattan also wrote (about code generally I believe):
>   
>>> 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.
>>>       
> mark replied
>   
>> it seems ideal to use (and contribute to) drupal.org infrastructure 
>> rather than building parallel systems.
>>     
>
> Yep. Absolutely! I can't see there is any reason not to use the
> drupal.org systems for this... despite my moans about tagging (above)
> the whole thing works well!
>
> ekes
>
>
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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
>   

-- 

Bruno De Bondt
Web/tech Indymedia.be

bruno at indymedia.be
http://www.indymedia.be

PGP key: http://brunodbo.be/files/docs/brunoatindymediabe_pubkey.asc
ID: D48B28E2
Fingerprint: C25C 3B90 4A10 FBBC 3B22 4C7D 3AFB AD2C D48B 28E2