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 @firstname.lastname@example.org 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.
yewtu.be for me too, because is easy to remember and works well.
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 recommend you to read about consensus and decision making for grassroots. They are some cool books and websites. They are many local groups that coordinate on big social movements using this techniques (without anyone representing others to take decisions). They are slower, they take more time, but there is not power accumulation and are far more democatic.
I tried to answer this here: https://lemmy.ml/post/186957/comment/126842
A little clarification about the terminology I use: I use the term “free software” as RMS coined it (“free like in freedom”) and as GNU strictly defines on its website. They are some similar MIT licenses (the most common one is X11). Anyway they are very similar, free and GNU GPL compatible as you can read here: http://www.gnu.org/licenses/license-list.html#Expat http://www.gnu.org/licenses/license-list.html#X11License
MIT licenses and other ones (BSD…) are free but are not “copyleft”. They don’t require all modified and extended versions of the program to be free software as well. Perhaps, that’s what you mean when you say “!= free”!
Note that all the source code in the public domain is free and not copyleft too so I agree with RMS when he defines copyleft software as a subset of all the existing free software (now and in the future, when all tends to become public domain).
In fact, GNU distinguishes more kind of slightly different free licenses:
Note: free software != GPL compatible. EUPL 1.1 and 1.2 are free software but they are not compatible with GPL. http://www.gnu.org/licenses/license-list.html#EUPL-1.1
Sorry for this long comment. My English is quite poor so probably some parts are difficult to understand. If someone wants clarifications of this clarifications, just say it and I’ll try again 😅
Suppose you took a photo and publish it under CC BY license. If someone uses it on an article and references your photo properly, the article can have any license because it’s not an adaptation/remix of your photo, the article just has your photo inside. If you publish the photo under CC BY-SA license, the same applies (in this case, the reference to your pohoto in the article will be slightly different).
Now suppose that you publish your photo under CC BY license and someone makes and adaptation/remix of it. For example the new work is your photo cropped and with some filters applied. The author of the adaptation can add the NonCommertial clause to the derivative work. He/she can license its new work with CC BY-NC license or with CC BY-NC-SA, stopping any commertial use of the adaptation and if he/she wants getting paid for any commerdial use.
But if you publish your photo under CC BY-SA license, this is not possible. The adaptation of your photo must use the same license. The remix, the derivative work, must be CC BY-SA too! To make any other use, the adaptor needs your permission.
Did I explain myself?
You have more info in the Creative Commons FAQ:
The site home explains it is on “low maintenance mode”.
Here you can find some similar info (just basic indicators): https://fedidb.org/software/lemmy
To really know what solarpunk is I recommend you to read its manifesto: https://lemmy.ml/post/57382
You can follow that info and other related ones here: https://the-federation.info/lemmy
Note: in the past Lemmy’s API fixed the way to count users.
The option to list only the local communities in the Communities page.
This would be very appreciated by the instances other than lemmy.ml, specially the little ones where it’s difficult for local users to find the existing local communities. You can see an example here: https://lemmy.eus/communities
Perhaps the default value of this filter could be managed by the “subscribed | local | all” option on the settings, like the posts on the home page.
In English, for example lemmy.glasgow.social (it’s as big as the non English instance I participate on). I think this instance could be a good place to build and grow English speaking communities.
26 instances listed here: https://the-federation.info/lemmy
I agree with you some critics about the moderation on lemmy.ml, specially the north korean legitimation.
But I think you are mixing the (main) instance and the software. A more logical conclusion could be to decentralice Lemmy instances/comunities more. The software itself has not the problems you are talking about. Other free softwares are used by polemic/disgusting/troubling groups (WordPress, Linux, LibnreOffice, Firefox…) including fediverse ones (Matrix, Mastodon…) and we should not conclude that the software itself or the network is bad. Isn’t it?
Why don’t move to another instance? You have quite some interesting options already. Why don’t enforce other instances and comunities? Lemmy let’s you do that. All us agree on that!
I think that the fediverse has already taken off. It’s not mainstream -perhaps never will be-, but it reached a critical mass and that’s crucial. The content network effect of the commercial social networks is very strong, but don’t forget it also carries drawbacks. Something similar happens with cities: many people want to life there (services, jobs, cultural offer…) but doing so also leads to problems (road traffic congestion, air quality and many more!).
Fediverse has proven it’s viable, is getting more mature and it’s gaining impulse on many different niches. I think these are all good signs. ‘Cities’ are going to exist for a long time (the capital’s machine is very strong), ‘towns’ need to keep working and fitting the needs of the burned migrants (respecting privacy, respecting languages, avoiding harassment…) without repeating the ‘cities’ errors: monetization of free giant services --> tons of adds, massive profilation, lack of privacy, development of addiction thought algorithms…
Let’s see how much the fediverse can grow (technological sovereignty of grass roots, governments…) and where is the equilibrium with the big commercial social networks. I’m sure we are in the beginning of a long and interesting transformation :-)
We are not sure if it’s a good idea to federate on an instance speaking such a little language like Basque with all these English instances. We still have to discuss about it locally. Do you think it’s a good idea?
Why all the federated instances speak (mostly) English? Does anyone knows why instances speaking other languages don’t federate? Opinions will be very appreciated.
OK, thank you.