Provide license file

[proinsias]

I'm working on submitting this package to conda-forge – see my PR. As part of this, I would like to include a license file for this project.

Could you please add one to the project and to the MANIFEST.in file?

[fgregg]

I was pretty sloppy here, because I the upstream work by @slacy doesn't have a clear license. I'm happy to add a license for my work (the cython code), but we also need him to provide a license for his work, the c++ code. https://github.com/slacy/double-metaphone/

[proinsias]

Thanks for filing the issue!

[sarimak]

The underlying C++ library's license seems to be Perl license which means either GPL 1+ or Artistic license (liberal, allows commercial re-distribution).

Since the referenced request to the author of the C++ library is unsolved for many years, could this wrapper select the Artistic license in good faith based on the available knowledge and notify the author of the C++ library so he can disagree?

If this sounds like a safe move, could you please add https://choosealicense.com/licenses/artistic-2.0/ as LICENSE.txt to this repo's root and add the license metadata to the PIP package?

It would be great to first publish a new version of the package still without an explicit license but with a deprecation warning indicating that the license of the package will be clarified - then increasing the major version of the package and publishing the explicitly-licensed version. So people pinning to a major version will have a chance to choose whether to stay pinned to the current state or to go with the flow and use the "new" license.

[fgregg]

Sounds good. Can you make a PR?