Do you still intend to change the license?

[erlend_sh]

Continuing the discussion from Switching to Apache 2 license:

@spf13

There was a long discussion in the github issues around the request to switch to a more open license.

My understanding is that this is completely possible, but requires sign off from all contributors who have current contributions. The intent is to have this done so that the v0.13 release can be released under the Apache 2 license. This change would only apply forward. Existing versions of Hugo will remain released under the SimPL 2.0 license. (…)

Is this still ongoing? It just seems like the longer this is put off, the bigger a problem it will be, especially since you still aren’t using a Contributor License Agreement. Every commit you get from a new committer means another person you need a signoff from.

[bep]

Yea, we should maybe put the brake on merging in new contributions until we get a fix for this.

I’m no lawyer, but as I see it, Hugo is in a dual-license state at the moment. People who have signed off on the Apache 2 license and then contributed some work, and then the people who have contributed but not signed off on this license change.

I guess it is an option to continue with SimPL 2.0, but that would effectively be a git reset --hard v0.12 type of thing.

[erlend_sh]

Well, if you start using a CLA, at least you wouldn’t have to hold off on merging new contributions.

[nathany]

We may want to use something like https://www.clahub.com/ to get license sign-offs on future pull requests.