Consistent license

[Integralist]

Seems the Alephant gem has a license of GPLv3 (GNU GENERAL PUBLIC LICENSE), where some of the other Alephant gems are MIT

This needs to be consistent across all gems.

The difference (as far as I'm aware) is that with the MIT license you're letting all users know that they can modify the code and redistribute it as long as the original authors information is included in that distribution.

I'm not sure if the GNU license enforces a similar principle or not?

[Integralist]

@kenoir @stevenjack

[kenoir]

@Integralist think it should be GPLv3 as that's what alephant started with.

[stevenjack]

@Integralist @kenoir I'm just finishing off the support gem, I've copied the alephant license and there's a section in there that hasn't been filled out:

{project}  Copyright (C) {year}  {fullname}

Shall I assume it should look like this:

alephant-support  Copyright (C) 2014  BBC News

Should the full name be 'BBC News' or just the dev who created the repo?

[kenoir]

@stevenjack BBC News

[stevenjack]

@kenoir ok cool I've done that for support. I've got to add the support gem into alephant so I'll update the license placeholders in there too.