Contributor Agreement?

[Former user]

Do you have a contributor agreement in place? I wish to release a dialect, but my company's preferred license is GPL. Do contributions have to be licensed under MIT?

[Mike Bayer]

its probably not appropriate for GPL code to be present in SQLAlchemy core, since to my knowledge its not compatible with the MIT license, however dialects don't need to be present in core. You can maintain your dialect as an external package on Pypi - SQLAlchemy accesses it using setuptools entrypoints. This is how IBM's DB2 dialect works. You'd register your driver's name, such as "postgresql+xyzdriver", under the "sqlalchemy.dialects" entrypoint. We haven't tested the "entrypoint" system with 0.6's naming convention, so let me know if it needs any adjustments - the lookup is in sqlalchemy.engine.url.URL.get_dialect()

[Former user]

The entrypoint system is working fine for me in 0.6. See http://stackoverflow.com/questions/1674841/how-do-i-write-an-external-dialect-for-sqlalchemy

I doubt you have more than one +xyzdriver, I'd just register the database name by itself

[Mike Bayer]

You can do what you want, but you might want to register both dbname and dbname+xyz since name+driver is going to be the standard style in 0.6.