For those new to this forum, you may want to check out | this page | which lays out the overall approach for creating the Transition Software Platform.
A formal team will be assembling to tackle this portion of the project. They will set the protocol for posting to this forum.
Further information concerning this project can be obtained by contacting the Transition Network on "info[AT]transitionnetwork[DOT]org".
Having looked at your desired time frame and read the proposed feature set etc. I VERY strongly suggest 1 of 3 options:
1. Drupal
2. Plone
3. Some other web developement framework (e.g. Ruby on Rail, Django, TurboGears, Grok/Zope 3)
I think we should essentially be looking at either 1. or 2. unless someone very keen and talented from within the network steps forward with an amazing proposal for 3.
I've read LOTS and LOTS about the pros and cons of drupal vs. plone. Its a tough call although I (currently) personally lean towards plone (mainly because it is written in python as opposed to php).
The main think against plone is that it is generally more resource intensive than drupal. Drupal also has a larger community with lots more modules (although the quality of plone productes tends to be higher).
Anyways, technically there are lots of reasons to go with either one or the other. I think ultimately the decision needs to come from whoever steps forward to do the implementation work (I'm more requirements and evaluation person myself because I don't have the skills to take on the implementation of a large project like this).
Choosing the software based on the person stepping up to cover the implementation phase is the wrong way around IMO.
First we need to work on requirements.
Second we evaluate solutions based on those requirements.
Third we make recommendations.
Fourth we make a decision based on the recommendations and the resource constraints at that time.
Fifth we get someone to do implement the solution that's been decided upon.
So in fact, now's probably not the time to get into a geek debate about Plone vs Drupal vs Moodle vs Jabberwocky.
Hi Ben,
I think you've misinterpreted what I meant.
What I meant is that assuming, for example that a decision is made in your step 4 above that plone is going to be used, unless an implementation team steps forward with plone expertise, then the decision is fairly meaningless. Especially considering the resource constraints.
"Fifth we get someone to do implement the solution that's been decided upon. " sounds nice and simple, but doesn't tend to be how technical projects pan out. In my experience talented coders are more like artists and poets than people can simply say "implement this" to.
Also, while steps 1-3 are very important and very much need to be done (as people have mentioned elsewhere, people in Transition Network need to feel some ownership over the process) I have seen so many groups go through this process that I'd be very surprised if 2 of the recommendations are not drupal and plone. Indeed, I'd be mildly concerned if they weren't (because so many great minds have done this already and ended up with that conclusion). The requirements discussed so far are far from unique (indeed, they are fairly ubiquitous desires/wants).
Perhaps it would help if I were to write up a comparison of drupal and plone and their pros/cons? (based on the many existing ones out there, but bringing them up to date and adding my own perspective)
I am not sure it is a geek debate.
For techy v tetchy
"...Transition thrives because it enables & supports people to do what they are passionate and called to do"
though i do understand that people are straying wildly and wantonly from the immediate question and being generally 'chaotic, inefficient and frustrating', this is a forum afte all, and the topic is 'potential solutions'...
Hey Millymop - I laughed out loud re your "chaotic..." comment. I need to chill a bit...
x
You must log in to post.