Re: [seul-edu] criteria: was site tools for schoolforge

[Michael Hall <admin@openlearningcommunity.org>]

Other criteria should include ease of application code maintenance, because as
we know people come and go. I think that a PHP based application is the
way to go ... the server set up easier and understood by many more people,
and the language is easier and understood by many more people. Sure, it
can't do everything like Python tries to, but it does what it does do (the
web) very well. I've never really gotten into Perl but I understand that
Perl can be messy and difficult to maintain (again, with people turnover
in mind).

I'm not suggesting PHP for everything, but for web-based communication
it's hard to beat in my opinion.

There are lots of choices:

phpWeblog, phpNuke, postNuke, Midguard, phpgroupware, Phorum, etc

Michael

On Fri, 30 Nov 2001, David M. Bucknell wrote:

> As my previous post was lengthy (though I hope someone will read it as I tried
> to put the following in context), I'm going to cut to the chase here. 
> 
> Proposed criteria for schoolforge, First Step:
> 
> The tool we want should:
> 1.allow the formation of projects for either software or curriculum (in which,
> for now, I'll include lessons, units, assessment, whole courses and entire
> school k-? plans)
> 2. provide bulletin board communication among project members/users
> 3. an optional tie-in to mailman
> 4. cvs for apps 
> 5. a version of cvs for texts and multimedia lessons (so that we can apply
> diff for example)
> 6. a front end that makes searching AND browsing of all projects possible AND
> EASY
> 
> Participation in projects should NOT REQUIRE comfort with anything other than
> a browser.
> 
> David
> 
> 
> 

-- 
################################
Michael Hall
admin@openlearningcommunity.org
m.hall@latis.net.au
http://openlearningcommunity.org