[development] Microsoft SQL Server
earnest.berry at gmail.com
Tue May 23 15:27:44 UTC 2006
Yes, I believe that has to do with the GPL license that Drupal currently
uses. "Interpretations" vary, but for the most part it comes down to
anything that touches Drupal directly, the source must free and the
"product" must be free, however the "service" is billable (man I love
lawyers). So, with regards to MS-SQL, database.inc sits in the middle and is
freely available and open, yet MS-SQL is in indirect contact with Drupal, so
the license will still hold water. With regards to your module, it is in
direct contact with Drupal; you would have to make your module a "driver" to
your "proprietary" code to hold true to GPL.
This is how I understand it though. Anyone correct me if I'm wrong.
Hmm...upon rereading your message, seems your module was just a driver to a
3rd party commercial product. Do you have a link to the thread about your
From: development-bounces at drupal.org [mailto:development-bounces at drupal.org]
On Behalf Of AjK
Sent: Tuesday, May 23, 2006 11:16 AM
To: development at drupal.org
Subject: RE: [development] Microsoft SQL Server
> I'm interested in resuming support for MS SQL Server.
I was recently "knocked back" from submitting a module
because it had a connection with a "commercial product"
The reason given was that a recent decision was
made that Drupal stuff wouldn't concern itself with
Having said that, in another recent email it was noted
that this policy needs to be reviewed again.
My module is just a kind of simple "stats for your website" product.
Wouldn't bolting on MS-SQL represent a much larger association
with a commercial product?
I'm not bothered by the exclusion of my module one bit btw, just
thought that if there's a time and a place for a policy review then
bolting MS-SQL is a good kick off point as MS-SQL is about as
commercial a product you're likely to see ;)
More information about the development