[Imc-communication] [EN] [ES] [FR] introducing IMC-ALTERNATIVES and invitation to join (fwd)

[boud]

hi imc-communication, imc-alternatives,

(français en bas)

(en)

> ---------- Forwarded message ----------
> Date: Wed, 01 Nov 2006 03:52:37 -0600
> From: Jay <jay...
> To: imc-communication at lists.indymedia.org
> Subject: [Imc-communication] [EN] [ES] [FR] introducing IMC-ALTERNATIVES and
>     invitation to join

> SUMMARY:
> The "imc-alternatives" working group invites you to join us in the
> formation of a global "Alternatives IMC!" The "Alternatives IMC" will be a
> "next generation" Indymedia website that will both gather content about all
  ...

The idea is great :).   However, it seems that some communication is
missing regarding codebases, that's why i'm cc-ing to imc-communication...

> 2) To develop the Alternatives Indymedia site to be a "next-generation" IMC
> site. This will include offering both traditional IMC features (open
> publishing newswire, central feature column) as well as collaborative
> editing (aka open editing) and wiki work-pages, integrated forums and
> project-oriented mailing lists, blogs, RSS feeds, and other advances that
> will inspire active participation in the site.  To accomplish this, we want
> to work with visionary techies and innovative coders (maybe YOU??) to
> pioneer new versions of code (perhaps using Drupal, perhaps using Plone),

i would suggest that imc-alternatives might want to work together with
indymedia techies (and supporters) - who are going through a
systematic process of looking at 14 different codebases (CMSes) in
order to decide which would be most useful/realistic for us to support
in the long term. plone and drupal are just two of these among many.

Reports on the different CMSes are expected to be finished by the end
of November, and then a shortlist will be made by the end of December.
The method of deciding hasn't been decided upon, so presumably it will
be rough consensus on irc + wiki.

If the imc-alternatives group wants to have general support from 
indymedia techies, it might be a good idea to work together with imc-cms
(most activity and de facto decision-making happens in irc on #cms and/or
on the sarava wiki, not on the mailing list):

http://lists.indymedia.org/mailman/listinfo/imc-cms
http://techmeet.sarava.org/English/CMSSurveyList

The process of selecting one (or more) "favoured" CMS(es) will have
many practical effects and consequences, so it may not be a good idea
to claim that two of these are already favoured when we are two months
away from even choosing a shortlist...



(fr)

> ---------- Forwarded message ----------
> Date: Wed, 01 Nov 2006 03:52:37 -0600
> From: Jay <jay...
> To: imc-communication at lists.indymedia.org
> Subject: [Imc-communication] [EN] [ES] [FR] introducing IMC-ALTERNATIVES and
>     invitation to join

> SUMMARY:
> The "imc-alternatives" working group invites you to join us in the
> formation of a global "Alternatives IMC!" The "Alternatives IMC" will be a
> "next generation" Indymedia website that will both gather content about all
  ...

L'idée est bonne :). Pourtant, il me semble qu'il y a de la communication
qui manque concernant le choix de code, c'est pourquoi je fais cc à 
imc-communication...

> 2) To develop the Alternatives Indymedia site to be a "next-generation" IMC
> site. This will include offering both traditional IMC features (open
> publishing newswire, central feature column) as well as collaborative
> editing (aka open editing) and wiki work-pages, integrated forums and
> project-oriented mailing lists, blogs, RSS feeds, and other advances that
> will inspire active participation in the site.  To accomplish this, we want
> to work with visionary techies and innovative coders (maybe YOU??) to
> pioneer new versions of code (perhaps using Drupal, perhaps using Plone),

Je suggérerais que imc-alternatives puisse vouloir travailler ensemble
avec les techies indymedia (et d'autres) - qui sont en train de
systématiquement étudier 14 codes (CMS) différents afin de décider
lequel(s) serai(en)t le(s) plus utile(s)/réaliste(s) que nous pourrions
soutenir sur le long terme. plone et drupal ne sont que deux choix 
parmi plusieurs.

Des analyses des CMS différents sont attendues jusqu'en fin novembre, 
et une liste courte serait établie vers fin décembre. La méthode de 
prise de décision n'a pas encore été décidée, mais on pourrait imaginer
que ce soit le consensus approximatif sur irc + wiki.

Si le groupe imc-alternatives souhaiterait d'avoir un soutien large
des techies indymédia, il pourrait être avantageux de travailler ensemble
avec imc-cms (la plupart de l'activité se passe sur l'irc sur #cms et/ou
sur le wiki sarava, et très peu sur la liste de discussion) :

http://lists.indymedia.org/mailman/listinfo/imc-cms
http://techmeet.sarava.org/English/CMSSurveyList

Le processus de sélection d'un (ou plus) CMS « favorisés » va avoir 
plusieurs effets et conséquences pratiques, il ne serait pas forcément
une bonne idée de suggérer que deux parmi eux sont déjà favorisés lorsque
nous sommes encore deux mois du choix d'une liste courte...


solidarity
boud