Choose license

[kynan]

@minrk, @mforbes, can we please decide on a license? I'd choose a permissive license like MIT.

[mforbes]

I am fine with any license.

[minrk]

MIT/BSD is always my preference. My original gist is Public Domain, so do whatever you prefer.

[mforbes]

The only issue I can imagine right now is that the best solution for using this mercurial might be as an extension, which would probably have to be compatible with GPLv2. This would preclude me from including an extension with this project, but I think that is reasonable. Such an extension should probably be distributed on its own anyway.

http://www.third-bit.com/2010/04/12/the-chilling-effect-of-the-gpl.html

[kynan]

Given that MIT (== X11) is GPLv2 compatible I'll go for that.

[mforbes]

It is not backwards compatible: i.e. one still cannot include a mercurial extension here, but as I said, I don't think that is a real problem. I have updated PR #2 to include the MIT license and some classifiers.

One issue: if you install this from PyPI, I don't think that the git filters will get installed. They probably need to be installed in a MANIFEST.in file. Also, do you have any good idea how to make these accessible to users when the package is installed from PyPI? In my project I added a script that can be sourced to set the users environmental variables. Do you have a better suggestion?

[kynan]

Git filters are per repository and they should not be installed globally when one installs nbstripout. So this is intended behaviour and I don't think there is an issue.

[mforbes]

I can never remember where things are, so like to be able to run or source a single command mmf_setup which does whatever needs to be done to install hooks etc. in a repository. Thus, I thought it might be useful to include the script in the manifest so it can be programmtically installed by a script from os.path.basename(nbstripout.__file__) for example.

[kynan]

I don't think I fully understand your use case @mforbes. For a Git repository you simply run nbstripout install to install the hook. I suppose we could augment this task to also work in Mercurial repositories (we're already testing whether we're inside a Git repository, so this could simply be extended).

[kynan]

We now have an MIT license (added by #2).

[mforbes]

Ah. Okay, I think I understand now. I will see if I can do something similar with mercurial.