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

[lancaster-imc at riseup.net]

Buildoff? If I were a programmer I would be tempted by that, for sure.
LPIMC techs have been building the LPIMC site on drupal 6 modules for a
while now, and the vision of our site is in line with the vision of
imc-alternatives. I emailed the lead tech about continuing what has been
done, but making it in line with imc-alternatives, which would actually
benefit lpimc, imc-alternatives, and so far as I know DC-IMC would like to
upgrade but has no active tech collective to draw from at this point, so
they are watching too. Basically, Dylan can keep what he is already doing,
but get help from others on the list who have drupal experience. Since it
does not really change what he is doing, I think he will be in agreement,

So, the build-off could in fact already by on......

Michaelv

> 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
> _______________________________________________
> Imc-alternatives mailing list
> Imc-alternatives at lists.indymedia.org
> http://lists.indymedia.org/mailman/listinfo/imc-alternatives
>