Verifying source code licensing Options

[nosoop]

It looks like I'm obligated to make a second post.

It's been pointed out to me that the SVN has both GPLv2 and GPLv2+ licenses (the latter being present in every code file), and the official github repository license file was changed from GPLv3 to AGPLv3 with this commit.

As far as I can tell the GPLv2-only license file should be invalidated due to the other files that are GPLv2+ that were present in that same commit, so I'd just like to make sure that the project in its entirety is indeed supposed to be licensed as AGPLv3 now, if it's licensed under GPLv3 as the previous license was, or still GPLv2+.

My understanding is that all the source files created prior is still under GPLv2+ and cannot be modified with the stipulation of the AGPL, so the AGPL is only applied to the output of the whole, if anything (as no new code units are Affero-licensed).

Not a lawyer though; just a developer that hates being obligatorily concerned about licensing.

I don't have any problems with either license; just making sure if the change in license was properly acknowledged (since it looks like it snuck through a pull request).

[Cheeseh]

Not a lawyer though; just a developer that hates being obligatorily concerned about licensing.

me neither / me too

I don't have any problems with either license; just making sure if the change in license was properly acknowledged (since it looks like it snuck through a pull request).

The change was approved by myself on the source code's move to GIT. I would use the GIT version now anyway as it is up to date. Particularly Robocop's version/fork.

[nosoop]

The change was approved by myself on the source code's move to GIT. I would use the GIT version now anyway as it is up to date. Particularly Robocop's version/fork.

Got it; thanks for the input.

I've forked the repo based on yours prior to the licensing issue being brought up; will see if there's any changes that I'd like to pull down.