Topic: Well, are we changing to LGPL2.1+?

Edit: Added some requested clarifications.

This has been up for discussion before, but we never got around to do anything about it.
I think LGPL2.1+ is a good choice and would make OOFEM more commercially friendly, and there has more-or-less been a consensus on that already. I've been contacted on developing code from a commercial company, and LGPL would make things easier. I think with LGPL we could expect more payed work on OOFEM, which I think is of interest of most developers.

To be clear:
I, Mikael Öhman, agree that my existing and future contributions* may be licensed under: "LGPL2.1 or any later version"**

* Contributions sent to oofem.org or github.com/Micket/oofem

** By any newer version it means you would allow LGPL2.1 and newer versions of the license (at the option of users). (As we do right now but for GPL, see any header file). This addendum is a must, as we would otherwise risk becoming incompatible with other open source software.

Could the other developers please respond and post whether or not they agree with the statement above? (If you agree, just copy the line and post it).

You can read more about the license
http://www.gnu.org/licenses/lgpl-2.1.html
where we can see the exact statement that will be in every file (like now)

This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) any later version.

This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
Lesser General Public License for more details.

You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA

Re: Well, are we changing to LGPL2.1+?

I, Jim Brouzoulis, agree that my existing and future contributions* may be licensed under: "LGPL2.1 or any later version"**

3

Re: Well, are we changing to LGPL2.1+?

I, Borek Patzak, agree that my existing and future contributions* may be licensed under: "LGPL2.1 or any later version"**
* Contributions sent to oofem.org or github.com/Micket/oofem
** By any newer version it means you would allow LGPL2.1 and newer versions of the license (at the option of users). (As we do right now but for GPL, see any header file). This addendum is a must, as we would otherwise risk becoming incompatible with other open source software.

Re: Well, are we changing to LGPL2.1+?

I, Vit Smilauer, agree that my existing and future contributions* may be licensed under: "LGPL2.1 or any later version"**
* Contributions sent to oofem.org or github.com/Micket/oofem
** By any newer version it means you would allow LGPL2.1 and newer versions of the license (at the option of users). (As we do right now but for GPL, see any header file). This addendum is a must, as we would otherwise risk becoming incompatible with other open source software.

5

Re: Well, are we changing to LGPL2.1+?

I, Daniel Rypl, agree that my existing and future contributions* may be licensed under: "LGPL2.1 or any later version"**
* Contributions sent to oofem.org or github.com/Micket/oofem
** By any newer version it means you would allow LGPL2.1 and newer versions of the license (at the option of users). (As we do right now but for GPL, see any header file). This addendum is a must, as we would otherwise risk becoming incompatible with other open source software.

Re: Well, are we changing to LGPL2.1+?

I, Milan Jirásek, agree that my existing and future contributions sent to oofem.org or github.com/Micket/oofem may be licensed under LGPL2.1 or any later version.

Re: Well, are we changing to LGPL2.1+?

I, Jan Stránský, agree that my existing and future contributions sent to oofem.org or github.com/Micket/oofem may be licensed under LGPL2.1 or any later version.

Re: Well, are we changing to LGPL2.1+?

I, Petr Havlásek, agree that my existing and future contributions* may be licensed under: "LGPL2.1 or any later version"**
* Contributions sent to oofem.org or github.com/Micket/oofem
** By any newer version it means you would allow LGPL2.1 and newer versions of the license (at the option of users). (As we do right now but for GPL, see any header file). This addendum is a must, as we would otherwise risk becoming incompatible with other open source software.

Re: Well, are we changing to LGPL2.1+?

I, Filip Kolařík, agree that my existing and future contributions* may be licensed under: "LGPL2.1 or any later version"**

* Contributions sent to oofem.org or github.com/Micket/oofem

** By any newer version it means you would allow LGPL2.1 and newer versions of the license (at the option of users). (As we do right now but for GPL, see any header file). This addendum is a must, as we would otherwise risk becoming incompatible with other open source software.

Re: Well, are we changing to LGPL2.1+?

I, Peter Grassl, agree that my existing and future contributions sent to oofem.org or github.com/Micket/oofem may be licensed under LGPL2.1 or any later version.

Re: Well, are we changing to LGPL2.1+?

I, Ladislav Svoboda, agree that my existing and future contributions* may be licensed under: "LGPL2.1 or any later version"**

* Contributions sent to oofem.org or github.com/Micket/oofem

** By any newer version it means you would allow LGPL2.1 and newer versions of the license (at the option of users). (As we do right now but for GPL, see any header file). This addendum is a must, as we would otherwise risk becoming incompatible with other open source software.

Re: Well, are we changing to LGPL2.1+?

I, Carl Sandström, agree that my existing and future contributions* may be licensed under: "LGPL2.1 or any later version"**

Re: Well, are we changing to LGPL2.1+?

I, Jose Roman, agree that my existing and future contributions* may be licensed under: "LGPL2.1 or any later version"**
* Contributions sent to oofem.org or github.com/Micket/oofem
** By any newer version it means you would allow LGPL2.1 and newer versions of the license (at the option of users). (As we do right now but for GPL, see any header file). This addendum is a must, as we would otherwise risk becoming incompatible with other open source software.

Re: Well, are we changing to LGPL2.1+?

I, Andreas Feymark, agree that my existing and future contributions* may be licensed under: "LGPL2.1 or any later version"**
* Contributions sent to oofem.org or github.com/Micket/oofem
** By any newer version it means you would allow LGPL2.1 and newer versions of the license (at the option of users). (As we do right now but for GPL, see any header file). This addendum is a must, as we would otherwise risk becoming incompatible with other open source software.

Re: Well, are we changing to LGPL2.1+?

Borek,
I know I'm missing at least 1 signature still (he's away on vacation) from Chalmers, but how is the state of older contributions that you have received? From the comments in the code I know of at least:
Chamrova,
Simon Rolshoven,
Tomas Kerici,
Ian Stranskv
Richard Vondracek

Re: Well, are we changing to LGPL2.1+?

I, Martin Horak, agree that my existing and future contributions* may be licensed under: "LGPL2.1 or any later version"**
* Contributions sent to oofem.org or github.com/Micket/oofem
** By any newer version it means you would allow LGPL2.1 and newer versions of the license (at the option of users). (As we do right now but for GPL, see any header file). This addendum is a must, as we would otherwise risk becoming incompatible with other open source software.

Re: Well, are we changing to LGPL2.1+?

I, Erik Svenning, agree that my existing and future contributions sent to oofem.org or github.com/Micket/oofem may be licensed under: "LGPL2.1 or any later version"

Re: Well, are we changing to LGPL2.1+?

I, Ruzena Chamrova, agree that my existing and future contributions* may be licensed under: "LGPL2.1 or any later version"**
* Contributions sent to oofem.org or github.com/Micket/oofem
** By any newer version it means you would allow LGPL2.1 and newer versions of the license (at the option of users).

Re: Well, are we changing to LGPL2.1+?

I, Ruzena Chamrova, agree that my existing and future contributions sent to oofem.org or github.com/Micket/oofem may be licensed under: "LGPL2.1 or any later version".

Re: Well, are we changing to LGPL2.1+?

I, Richard Vondráček, agree that my existing and future contributions* may be licensed under: "LGPL2.1 or any later version"**

Re: Well, are we changing to LGPL2.1+?

I wanted to bump up this thread again. We're still missing (at least):
Tomas Kerjci (worked on hydrating concrete material). I sent an email to Tomas so he is aware of the thread.
Simon Rolshoven (worked on DruckerPragerPlasticity). I didn't find any realiable contact information.

But there are possible others who I might have missed or who never even entered their name.
If anyone happen to know of some other past author, please let them know about this thread.

Re: Well, are we changing to LGPL2.1+?

I, Simon Rolshoven, agree that my existing and future contributions* may be licensed under: "LGPL2.1 or any later version"**

Re: Well, are we changing to LGPL2.1+?

I, Kristoffer Carlsson, agree that my existing and future contributions* may be licensed under: "LGPL2.1 or any later version"**
* Contributions sent to oofem.org or github.com/Micket/oofem
** By any newer version it means you would allow LGPL2.1 and newer versions of the license (at the option of users).

Re: Well, are we changing to LGPL2.1+?

I, Martin Fagerström, agree that my existing and future contributions* may be licensed under: "LGPL2.1 or any later version"**

Re: Well, are we changing to LGPL2.1+?

We're still missing (at least) signatures from Tomas Krejci, and Alper Cesur.

I've tried contacting them several times (through email in the past 2 months), but I haven't gotten any response.

Edit: Alper is waiting for the forum registration approval, but said he would agree to the new license.