[Imc-alternatives] a note for non-geeks on the current code situation

[strypey at riseup.net]

Kia ora koutou

lancaster-imc at riseup.net wrote:
>> So, now I think we're back to vagueness.  We have the Drupal, Plone,
>> Indycore, Cake-Php options....but you're right, the talk could go on
>> forever if we don't finally make (or remake) a decision.

Just to clarify, Indycore is an indy-specific cms built on Plone. So our
immediate options are (in no particular order):
1) Drupal
2) Indycore (plone)

Correct me if I'm wrong but I don't think there is a ready-to-use CakePHP
package yet?

>> Is there anyone out
>> there (or, again, more than one anyone) who would take that plunge
>> and say, "I will help make the Drupal version of the Alternatives
>> site come together?"  We now have the PhillyIMC site as a jumping-off
>> point, which is something we didn't have before, so maybe we're closer.

Good question Jay. Unless we get some volunteers for this (preferably 2 or
more), it seems sensible to take up Dimitri's offer to build on Indycore.

I wonder, would it be possible to have more than one alternatives front-end,
plugged into the same database (and based on the same 'look and feel' design),
at least initially? That way we could make it a build-off, whoever reckons they
can present the best site in their preferred language/ software could build one,
and we'll see which one we like best? This would provide a practical way to
demonstrate the pros and cons of each codebase, which could be helpful to both
the imc-cms discussion and to other imc collectives finding it hard to choose a
cms for urgent migrations.

Thoughts?
Strypes