Suitable licence for schema components
I’ve started on extracting some of the DB backed tables and stored procedures I’ve developed for use behind my jpigd helper (https://gitlab.quatermass.co.uk/jpig/jpigd <https://gitlab.quatermass.co.uk/jpig/jpigd>) and was wondering what informed folks here felt as to the most appropriate licence for releasing frameworks that live in their own schemas. The most obvious ones that come to mind would be GPLV3+ or the PostgreSQL License <http://www.opensource.org/licenses/postgresql> and I was wondering about the applicability of GPLV3 if the framework essentially constitutes a library and it possible pollution of the using project. Regarding the frameworks themselves, they’re not tied to the daemon itself but are designed to provide specific elements of backend functionality that I’ve needed as part of some ongoing development. * An application password test/encode framework that knows about a lot of common formats but can automatically upgrade to a default (leaving only the unused accounts in old formats. * A JSON-RPC decode/dispatch framework (bi-mode handles a direct DB connection doing JSON-RPC calls and also a similar mech behind jpigd with web session cookie management). I expect to get the first drop of these beasts in a week or two once I’ve cleanly extricated them from the original project and got some form of test-case stuff in place. So, what does everybody feel about the suitable licences for this ? — Bernard Quatermass.
Looking for feedback and contributions
Apologies if this isn’t the right place for this. I have created a helper daemon “jpigd”, FastCGI JSON Postgresql Gateway A tool to aid the elimination of CGI scripts on web servers and moving all the business functionality into the database server along with the rest the business storage logic. It is a fast-cgi handler that simply calls an SQL function with POST data as the first parameter and JSON encoded version of the CGI environment as the second parameter. A more thorough description can be found in the project README at https://gitlab.quatermass.co.uk/toolsmith/jpigd/blob/master/README.md <https://gitlab.quatermass.co.uk/toolsmith/jpigd/blob/master/README.md> The idea being that there is a whole class of applications that are primarily database interaction only and where traditional middleware (php/perl/java/node) is redundant. At this point I’m just looking for thoughts, comments, suggestions, possible sample apps (or suggestions for same), help with documenting the locked-down user approach. Thank you in advance for any feedback you can give. — Bernard Quatermass - The Toolsmith.
