Forum OpenACS Q&A: Re: OpenACS assessment...

Collapse
3: Re: OpenACS assessment... (response to 1)
Posted by Torben Brosten on 03/15/04 01:24 PM
(hey, still have some battery power left..)

A. How sustainable is the existence of OpenACS?

The software is forkable, customizable, sustained, maintained, and improved upon by a community of developers. Try that with proprietary software.

A snapshot of the project (taken at any time) could be viewed as a loose international joint-venture of individuals, consultants and companies with collectively overlapping goals.

For marketing purposes, a situation analysis should be made of the openacs system, before its strengths, weaknesses etc are identified and assessed for applicability to any purpose. Some of your questions seem more specific to the latter...

Collapse
4: Re: OpenACS assessment... (response to 3)
Posted by Jeff Davis on 03/15/04 01:48 PM
Torben mentioned forking. One thing that is useful to point out relative to *Nuke's is that there seem to be as many forks as there are developers and while google will return an order of magnatude more hits for phpnuke it's not clear that if what you want is to know what is changing, what the release status is, or where to report or track a bug that that is at all a benefit.

With OpenACS we have an architecture that is modular and flexible enough and a community which is inclusive enough that we have never forked. Not having forked means there is no duplicated effort and no risk of being stranded on a fork which loses support to another version.