Lately there have been a flurry of AOLserver modules committed to the
AOLserver CVS: ns_imapc (imap client), ns_snmp, ns_cache got adopted,
ns_xml 1.5 released, ns_encrypt (strong encryption, horray!), ns_image
(for identifying image).
This is all great news, but even better news is that Scott Goodwin
seems to have become the (un)official community liason wrt the
AOLserver tree. He is importing these modules into the AOLserver CVS,
and giving commit rights to their maintainers.
He is explicitely asking for us (OpenACS) to move the latest
PostgreSQL driver to the tree, and he will give the maintainer commit
right to that module.
"The biggest problem is: will the OpenACS crew let me take the OpenACS
postgres module, refactor it and then use that refactored copy,
maintaining it at SourceForge? I realize OpenACS has a terrific SDM,
but I think the AOLserver C modules should be maintained and
distributed from a central location, and that would be SourceForge. If
the OpenACS folks continue with their version of postgres.so, that's
fine, but I hate to see two separate modules whose only real
differences may be cosmetic."
I for one, would prefer if we could just tell people "Go to
AOLserver.com and you can grab everything you need AOLserver-wise", as
long as we have commit privs to the PostgreSQL driver.
What do others think? Who would be the maintainer (one with commit privs)?