LICENSE upgrade to (L)GPLv3+

[GitMensch]

Is there a reason for you to keep the license at the current version? It would be easier to share sources between this project and GnuCOBOL if the license would be identical; otherwise GC can integrate changes from this project, but not the other way around.

[ytr-sakamoto]

Thank you for your suggestion.
We are considering upgrading the license to (L)GPLv3 in the next update.

[ytr-sakamoto]

Yesterday we updated opensource COBOL 4j but the license was not changed.
We will update the license in the near future.

[GitMensch]

Thank you for the note. Do you consider the same for opensourcecobol and the esql preprocessor?

[ytr-sakamoto]

We will update the license of opensource COBOL to GPL3 in the next version.
We consider the same for Open-COBOL-ESQL.

[GitMensch]

@ytr-sakamoto wrote:

We are considering upgrading the license to (L)GPLv3 in the next update.

That was yesterday, but its still on(L)GPLv2 :-( If you are fine with that I suggest:

• I do the "work" for the license update in ocesql (because that's "stale") and drop a PR
• You merge it in
• I then do the same either here or (because there's a lot going on in this repo currently) in opensource COBOL
• you merge, and I finally do the same to the last of the three repos

What do you think?

[ytr-sakamoto]

We upgraded the license to GPL3 in v1.0.2.

[GitMensch]

Thank you! Note: It seems that without intend the FDL and LGPL were deleted, too.
The files so far under FDL can likely be dropped altogether (#30), otherwise you may likely want to add the FDL back.
The files in libcobj still say LGPL so it is likely reasonable to include the LGPLv3 as lgpl-3.0.md or LICENSE.LIB or COPYING.LIB or LGPLv3 in this repo.

[GitMensch]

Last open points fixed with 1451d43 and 143e01c.