Forum OpenACS Development: Re: Use of Naviserver

If OpenACS moved to NaviServer, not only would it give the project a boost, it would also force some stability and improve the documentation, just by having a much larger community behind it.

I've witnessed the AOLserver thread with horror (at both sides, frankly) but it does seem like with the organizational support collapsing in AOL we might be better off putting our money on a horse with some momentum behind it.

Granted, this is assuming that the NS community would react well to the sudden influx (and certainly loud input) from the OpenACS community. Anyone (especially apart from the inherently biased project leaders) care to comment on how functional the NS development process is with respect to (mostly user) community input?

That should be discussed on naviserver mailing list, we've established pretty simple rules how development goes i the project, basic principle to be not to break things for others and discuss things that may have impact of the existing codebase. New features are welcome and as it turned out historically, first introduced later new features may be re-done by others to fit them more perfectly into the overall architecture.