Transition Towns Forum » Websites for Transition Initiatives » TransitionWebProject

Collaborative approach: comments invited

(31 posts)
  • Started 1 year ago by benbrangwyn
  • Latest reply from jdaviescoates
  1. Re solutions - I'm inclined to agree (with Tomma and Gary) that a combination of ready-made open-source solutions might be the way to go if the project is to go ahead in the timeframe and at a low-cost.

    I've been involved in building a community network from scratch (http://ki-work.com) and it's a full-time job for a few people. Far better to start small to test out uptake, then build up from there.

    One open-source solution may come from http://elgg.org - I'm in the process of reviewing their platform for a separate project so will feedback how customizable it is later.

    A really quick and easy start for a working prototype can be done for free with Ning (http://ning.com). This way we could get real feedback from a cross-section of TT users. As was mentioned on the requirements forum, usability will be a key issue as members will be all ages and levels of computer literacy. It's easy to get carried away with solutions that are pioneering and world-changing, forgetting who is actually going to use it.

    Jim

    Posted 1 year ago #
  2. I spend a lot of time evaluating options for platforms like this and to me there are only really two serious players, drupal and plone.

    I asked some of the many coders I know what they thought would be best in this case, considering the requirements and key projects outlined.

    Sam Rose (who is currently building a Social Media Collaboration platform for Howard Rheingold using drupal) said:

    "Probably you are on the right track with Zope in this case, looking at some of what they want to add. Python will make your life easier."

    For those that don't know plone is built on top of Zope.

    Just thought I'd share that :)

    Posted 1 year ago #
  3. I asked Sam to elaborate.

    He said:

    "I think, if you have the choice, that python is a better programming language to deal with than php, and zope more flexible in capable hands than Drupal (that being said, I often choose drupal)

    If you are just trying to do stuff that Drupal does well, go with Drupal. If you are trying to do stuff that requires lots of customization, go with something where you can use object oriented programming practices, like zope/plone, ruby on rails, django project, etc

    it seemed like the ambition of your project was more towards the latter (needing to go in the direction of lots of custom code)"

    Josef.

    Posted 1 year ago #
  4. I picked up a vibe that we shouldn't pick the CMS before we established the requirements. My take is that we do both. A keep revisiting each as more clarity emerges. It's important to know what CMS the people on this forum use/like. This is because we are the support system. The more people that know the CMS the more free support the project will get.

    I run a non-profit organisation (Kendra Initiative). A few years ago I asked members what CMS they preferred. The almost unanimous response was Drupal. Since then I have been tracking Drupal and, with funding recently received, we are only now embarking on the implementation.

    I've just returned from my second Drupal conference. The people (a mix of developers and end-users) are great fun to be with. Drupal draws eco-warriors and record labels alike. So, there's a big community and that means great free support from peers. There's a real sense on commitment behind the Drupal platform from it's developers. And there are many businesses designing for Drupal - many said they were having to turn work away. All this makes me feel warm inside. And that's important when embarking on any large project.

    Of course Josef feels the same way about Plone. And that's cool. So, whatever platform we choose we should take into account what members of this forum already know, use and like.

    Cheers Daniel

    Posted 1 year ago #
  5. In fact, what we need to strongly consider doing is creating plugins for as many CMSs and other systems as we can. Obviously, we can't create all of these so we need to create a messaging specification (based on current open standards) and then build some reference implementations.

    Rather than creating another monolithic install we need to create plugins that people can plug in to their existing set ups. Be they Plone, Drupal, or whatever.

    Just before you say this is all too much I must say this. Of course we start small. But unless we aim big we'll stay small. We must aim for the stars and have many steps along the way. At each step we need to produce working and usable systems. Lots of small steps. Lots of working systems. Not wait for some big bang product at the end. Hence my comments on prototyping - we never stop prototyping - but always they are usable.

    Cheers Daniel

    Posted 1 year ago #
  6. Hi Daniel, nice to see you here :)

    I just wanted to point out that, between plone and drupal, drupal does, without doubt, have the edge on size of active community. And its a really great community as you highlight.

    Plone's community is large, but nothing compared to drupal. And much more technical and so a higher barrier to entry.

    However, technically, proper object oriented programming stuff (e.g. zope/plone) has the edge, without doubt.

    I like where you're going with plugins though. If systems are built using open standards then it should be possible to have drupal/ plone applications working in simple but quite powerful ways.

    In fact, the DiSo project is working to build plugin for wordpress that do just that http://diso-project.org/

    I don't think anyone should be dictating what system Transition Initiatives go for individually, but its does help if they all choose for a small selection of a very good bunch.

    For the more long-term "Key Projects" outlined on http://transitiontowns.org/TransitionNetwork/TransitionSoftwarePlatform (community currency systems, etc) the technical edge of zope 3/ plone 3 will make all the difference.

    But in the immediate to short term I see no reason why small groups that are just starting out shouldn't use other great open source solutions like drupal, wordpress or http://www.cmsmadesimple.org/ for their "online presence" (or even simply use a commercial platform like Ning - very good at what it does and very useful networking and sharing too, but almost certainly not going to evolve into what we really want).

    Josef.

    Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.