Txopi

Euskaraz hitz egiten dut. (Basque language: I speak Basque)

Spanish is also my mother tongue. As you can see, I also speak English.

That's a personal decision. You could list the pros and cons and then take a decission.

I think you can use Gregorio for your daily life (probably you already do that) and sometimes, when you have to do a legal operation, be patient as until now.

I'm a 100% Spanish person and I have the same difficulties as you! Mi name and surname are Basque (a language spoken in Spain, but different to Castilian Spanish; there are millions of Spanish people with Catalan names too + all the people from Europe, etc.).

Every time I have to spell my name or my surname (or both), I do it. And personally I have no intention to change them. My name and my language, as my family and my history, are important parts of my identity, and I'm proud of them. I'd recomend you to do the same, here in Spain and in any other place of the world. Also to speak Polish to your childs if you ever have any.

But as I said before, it's a personal decision and if the legal stuff you have to do sometimes are a real problem for you, change your name. Just be sure that you will not regret later for giving up a part of your identity.

It look great!

What Drone does, synchronize your Gitea with GutHub? The opposite?

In case the free version and the proprietary version of the software can be slightly different (the free version's source code is on a public repository, but the proprietary one is in another place and some files are different), you must ensure that the contributor really understands there is another version of the software and his/her contribution is going to be added to that version too. And perhaps in the proprietary version you will need to merge the contribution in a different way, and in the future remove or extend that part. How can the contributor agree now or in the future what you do and how you do if he/she can't even see that software? It's weird and probably that's way people use to recommend to give the copyright to the proprietary version owner. Actually, I'm not sure.

Anyway, in your case, if the repository is unique and public (and will be in the future), and both licenses are clearly referenced (LICENSE files, README file and source files), I think contributors don't need to give you the copyright and can contribute just normally. Note that you don't want to say that both license apply, but that one of them apply in a given moment. You can't use SPDX in your case because one of the licenses will not be free, but I'm talking about something equivalent to the OR operator of this specification.

I have been thinking about this subject and my opinion about dual licensing for this case has changed. Let me explain:

The dual licensing requires you to create a non free license different to the other LGPLv3 license. I think it's complex to write a good and clear license with the requirements you want: dynamic and static linking, authorship recognition... In case you need to modify the license in the future, you need to write it in a way that the contributions of the past automatically will accept the new license. Finally, you could end writing the whole LGPL license again just changing the linking part!

For that reason, perhaps the most simple and secure way to do what you want to do is just use the LGPLv3 license with the linking exception just the same way other projects already do (follow the link to see 3 examples). This is what @octt@feddit.it mentioned at first. Basically you create a LICENSE file containing the LGPLv3 license (as many libraries and software projects do) and above the license you include the exception:

All files in this repository are licensed as follows. If you contribute to this repository, it is assumed that you license your contribution under the same license unless you state otherwise.

This software is licensed under the LGPLv3, included below.

As a special exception to the GNU Lesser General Public License version 3 ("LGPL3"), the copyright holders of this Library give you permission to convey to a third party a Combined Work that links statically or dynamically to this Library without providing any Minimal Corresponding Source or Minimal Application Code as set out in 4d or providing the installation information set out in section 4e, provided that you comply with the other provisions of LGPL3 and provided that you meet, for the Application the terms and conditions of the license(s) which apply to the Application.

Except as stated in this special exception, the provisions of LGPL3 will continue to comply in full to this Library. If you modify this Library, you may apply this exception to your version of this Library, but you are not obliged to do so. If you do not wish to do so, delete this exception statement from your version. This exception does not (and cannot) modify any license terms which apply to the Application, with which you must still comply.

As far as I know, this will make the software to become not free according to GNU, but at least you will get what you want in a quite reliable way.

LGPL is the license that fits more to your requirements but as some responses already pointed out, only dynamic linking would be allowed, not static linking too as you want. Perhaps you could create a new (non free) license based on LGPL license, but I don't recommend you to do that.

In your case, you can weight up the dual licensing. If you publish the code under LGPLv3 license AND copyright license, like MySQL does, people will understand that it's a free software project; they can choose the LGPL version for dynamic linking and the other version when they need to link statically.

To avoid further problems and keep a unique software project, you would ask software contributors (if any) to assign the copyright of the modification to you, so you can keep both version of the software (the LGPLed and the copyrighted one) always exactly the same.

For a big project this is risky, because someone could say no and create a fork of the LGPLed version of your project with his/her modifications, but if it's a little project and you explain that the copyrighted version is just to allow static linking for those developers they need it, I don't think you will have problems.

NOTE: in the copyright license you will need to explain that the software can't be modified (at least that exact version), that can be used, copied and distributed freely without previous permission, that dynamic and static linking is explicitly allowed, that you require authorship recognition this way, and that for all the usages not requiring static linking you recommend the LGPL licensed version of the library. This is just a proposal.

Very good and accurate explanation! More info at GNU's FAQ.

I updated the Spanish subtitles based on your improvements. Thank you very much for your help!

Here it is: https://cryptpad.fr/pad/#/2/pad/edit/TzMSPVLi5xyPE0X3dFCRsFiu/

Thank you for fixing English translation! More translations welcome :-)

I think intellectual property does not exist and copyright is based on a lie. You can watch this short video on Peertube: https://kolektiva.media/w/fYv5ELRxj1MtQvT5viTCes?subtitle=en

I don't want to ruin your joke but MIT is both, free and open at the same time.

MIT licensed software is free/libre software according to GNU and is "open source" according to OSI.