[Imc-alternatives] current code situation (was: Open Forum edit)

[lancaster-imc at riseup.net]

We're feeling the same anx here in Lancaster, PA; we want the site up,
have been dragging our feet while we listen to the tech chatter, and
basically have decided to build our cms (already in the works) with
drupal, based probably in part on the great work done by phillyimc, plus
whatever Dylan has done, and figure on somehow integrating crabgrass into
our cms. We also want to be in on the universal code, but we really need
to build and launch, and migrate to whatever the imc-cms group decides on.
I think a virtual conference between techs and non-techs is in order.
Perhaps this could resolve this simple yet important question?

Now, so far as Drupal is concerned, Dylan and our newest tech Ben are both
well versed in Drupal, and Dylan has built a bare-bones site in cakephp. I
find myself wishing the new Indymedia universal code was ruby on rails,
given what crabgrass is destined to be, and that fact that it seems many
of the tools we might need for indymedia are within ruby on rails already.
I hear a lot of good things about ruby on rails.

So, how do we arrange a global tech/nontech imc-cms virtual/physical meetup?

> Michael and everyone,
>
> At 2/23/2008, lancaster-imc at riseup.net wrote:
>>Hey, I just wanted to let everyone know I updated the wiki for IMC-Alt by
>>adding the top horizontal menu to all the pages for easier navigation.
>>Also, I  noticed on the tech page (I think) that it talks about Drupal as
>>the first install. From what I have gathered things have changed and now
>>php cake is the cms language of choice--Someone with the direct line on
>>the specific tech plan should probably update that page.
>>
>>Michael
>
> It's confusing.  Over the last few months I've been enthusiastic
> about our going with whatever backend code the imc-cms group decides
> upon.  However, as time goes on with no clear CMS choice, I've become
> less enthusiastic.
>
> I honestly am not sure what I think now.  There is still a lot of
> positive drupal energy in this group, but we haven't had anyone step
> forward and say "we're going to make this site work in drupal,
> darnit, so let's go!"  I like the arguments Ryan has for CakePHP, and
> am intrigued by the possible choice to go that direction.
>
> I really don't want our project to wait indefinitely to get ourselves
> going just so we can line up with the general indy code.  However,
> the benefits of being part of the overall network push toward a
> unified code are really appealing.
>
> What do other people think about this?  Should we continue to
> wait?  Or should we redouble our efforts to build something based on
> the PhillyIMC drupal code, as we agreed upon a long while ago?
>
> Jay
>
>
> _______________________________________________
> Imc-alternatives mailing list
> Imc-alternatives at lists.indymedia.org
> http://lists.indymedia.org/mailman/listinfo/imc-alternatives
>