I have been getting to grips with OACS at home and have even managed an install on the office intranet to provide some basic services. We now have a commercial project coming up which requires access through various means to a Postgres DB for historical sales analysis etc.
One of the required access methods is a web interface and although the db will not be part of OACS my boss has agreed that we can use OACS to provide the authentication, authorisation and to make use of the templates and other nifty features of OACS.
I'd like to create our bits and pieces as a package as this keeps everything neat. However, the question has arisen as to whether we are required to release our package under the GPL if it makes use of the features of the OACS framework but doesn't change them. In other words would this be viewed as a derived work?
I have searched the forums over the question of the GPL and there are plenty of threads. This thread (http://openacs.org/forums/message-view?message_id=25558) would seem to imply that the considered opinion is that packages do not have to be GPL'd but it is encouraged. I guess what I'm looking for is a decision from the OACS community as to the GPL cut-off point for package development (if there is one). It would be useful to have the official position in a FAQ or on the license page so that we all know where we stand.
By the way, the search for 'gpl' grenades at the bottom of the forth page :( although you can go back to the third then select 5 from the page list - just thougght you'd like to know.