Hi everyone.
Disclaimer
1. I’d like to insert a brief comment that might highlight my point of view on open source development that might be of interest to this discussion. I think to help as many people here as possible about what open source is.
2. As I said before, my goal is to answer possible questions related to open source and not to start a personal attack. Given that, by: community, society, humanity, philosophy, conduct, norm: we must help each other and respect ideas that we do not agree.
3. I think this thread is very interesting, and has a lot of good and bad arguments about what open source is.
4. This text is going to be big, so I hope you all have the patience to read it and possibly point out criticisms, general problems later.
5. I don’t want to be right or wrong about any point of view, but always doubt so that it’s possible to think about different things.
6. I hope I helped, if I didn’t, I apologize.
7. I’m going to use the concept of “counter-argument” to enhance the discussion about software and community concerns.
8. I will be direct, frank and sincere in my views. Please do not think that my being direct, frank and sincere with you is the same as thinking that I am rude or disrespectful. I’m just pointing out criticism, general comments.
9. I am not a lawyer, law student, prosecutor or judge. If in doubt, consult your lawyer (I am not providing any legal advice).
I agree to disagree, because its definition of GNU GPL is not in accordance with the definition of the dictionary, the dictionary says something like: “preamble ¹: the introductory part of a statute or deed, stating its purpose, aims, and justification. preamble ²: a preliminary or preparatory statement; an introduction. preamble ³: “the main purpose” of a preamble is to introduce a text. Preambles can be part of novels, films, pieces of music, or legal documents.” That’s what I understood, and I found when researching the word “preamble” in the dictionary too. In other words, it is part of a “philosophy”, “rule”, “law”, “social contract” and “terms legal”.
Please, see this: “When we speak of free software, we are referring to freedom, not price.” This statement is philosophical and also an “legal term”. Because if a project or software is licensed as GPL and is contrary to GNU philosophy, in such cases, this “software”, “open project” or “closed project” should be processed. As in this case: “What should I do if I discover a possible violation of the GPL?”
I agree here.
I agree here. But this does not happen in practice, generally programs are licensed under GPL because of the GNU philosophy. Please, see this: “When we speak of free software, we are referring to freedom, not price.” This statement is philosophical and also an “legal term”.
It’s true, and this philosophical view is contained in the GPL software license. Please, see this: “When we speak of free software, we are referring to freedom, not price.” This statement is philosophical and also an “legal term”.
There are several software licenses with greater permissiveness: MIT, Apache, Unlicensed, BSD, Mozilla Public License, Microsoft Public License etc. Please, see this: “The MIT license is permissive, placing very few restrictions on how the software can be used, while the GPL license is restrictive, requiring that any changes made to the code be released under the same license, and any software that uses the code must also be released under the same license.”
The “proof that there are permissive licenses” is because the GPL license is restrictive. Therefore “software freedom is less” and greater in the permissive license. But it depends on what you consider freedom whether it is something restricted or something permissive.
Most of the libraries and frameworks on GitHub are MIT licensed and not gplv2, gplv3. Some famous projects like linux is licensed under gplv2, bitwarden is licensed under gplv3.
I think it would not be interesting to use the “utilitarian”, “practical” or “popular” argument. But in general, there are several good reasons not to use GPL: “The GPL attempts to force people and businesses to release their source code. There is nothing wrong with that, except I don’t think it qualifies as “free software”. I want anybody to be able to do anything they want with my programs and/or its source code. I have no reason to restrict their activities. A majority of companies have already decided that their products will be closed-source even before they start designing them. If a closed-source company decides it could use some open-source code in its product, and if the code is licensed under the GPL, the company will do one of two things: use the open-source code and not tell anybody, or write their own code from scratch.”
Another good reason is this: “While GPL licensed software can be modified and redistributed as long as it remains free, BSD licensed software can be modified and redistributed under another license (including those of closed code).”
Another good reason is this: “The GPL is a complex license so here are some rules of thumb when using the GPL […]”
In short, people do not use the GPL for philosophical reasons because they do not agree with the GNU philosophy, as well as for practical, utilitarian reasons and also for other philosophical reasons, for example, by restricting development freedom, it reduces user freedom, Bearing in mind that the user will only have the available options that the license allows.
Additionally, there is the “orphan software problem” that GPL doesn’t solve as well as BSD, MIT, Apache, etc. Any company can continue a proprietary product, if the license allows it, which differs, for example, from the restrictiveness of the GPL license.
This is not what happens in practice, why would the gnu philosophy make another software license or change its own philosophy? Why would they think they are wrong when they defend “open source or that they are right”?
For example, most open projects do not follow the gnu philosophy nor, in general, follow the GPL license. In fact, this criticism is still valid today, to what extent is something “open”? Until a person decides “what is open”?
Note that I’m not talking about a moral or immoral argument, I’m not saying that the gnu philosophy is good or bad or that the GPL software license is good or bad. I’m saying in general, the criticisms of which are still valid today.
The LGPL is not a license of its own, but an extension of the GPL. See this: “This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below.”
It is not true for the previous reasons I presented. GPL licenses only produce GPL software. This alienates many people and companies who do not understand the jurisdiction of the GPL license nor the GNU philosophy.
I could argue the same for Baserow: “Baserow is itself permissively-licensed free software that is usually delivered as proprietary versions to customers.” Even because Linux and Android are still “open systems” because of the software license, and not in the practical sense that many think it should be.
In this case, Linux, Android and Baserow are still “open source”, even with “something proprietary”. For example, the fact that you have a version that doesn’t have the features you want is not unethical or immoral.
For example, there are features in different Linux distributions, and this does not mean that each Linux distribution is “proprietary” or “non-open”. In fact, the set of features that one or more Linux distributions can have is generally “guaranteed” by the community in which it was created or is maintained.
The same happens at Baserow, there are community features and features for the business model. Therefore, there is no sense in saying that Baserow is “partially open source” or should be “fully open source”.
The same case is for Baserow, it continues an “copy-center”, even though it has a proprietary part. In fact, the Baserow version is delivered openly. But it has extra features that you may or may not pay for. In this case, you can create these features if you have the money to hire a programmer or have programming knowledge.
I can say the same of the permissively licensed projects like MIT, Apache, BSD. In the case of permissively licensed projects like MIT, Apache, BSD we call something like: “copycenter” - the idea is to increase the number of distributions, versions and modifications. So, Baserow is a very interesting program and is licensed by MIT license, you have the freedom to do whatever you want in it. “This proves that MIT licenses are also as good as copyleft,” although I don’t like the idea of copyleft (for various philosophical, social, practical, intellectual, academic, commercial, personal reasons).
Also, I must emphasize that the concept of “freedoms of free software” was inspired by an old term created by President Franklin Delano Roosevelt in 1941 and there is even a memorial in his name with these freedoms. “Free software has not even created something so new.”, “free software” has achieved some projection thanks to famous projects such as “android”, “linux”, “emacs”, “activism”.
But most existing technologies are not open code, let alone copyleft, the internet is an example of this, “copyfree movement” is also (although I don’t like the political idea of “copyfree” and prefer “copycenter”). But in addition, there are several license versions available that are conflicting or incompatible: agplv1, gplv2, gplv3 etc. This is problematic from the perspective of which software license to choose.
It depends on what you consider “successful” or “succeeded”. For example, I consider that a technology is successful when there is a “credibility or social confidence” in this technology or when people usually “recognize the work of independent programmers.” Or when a high number of companies, governments and communities that use open software. About this, copyleft doesn’t seem to me to be “such an interesting movement.” part of what we have is “copyfree”, “copycenter” or even shared rights as CC (Creative Commons).
Also, only “2%” of GitHub projects are licensed in GPL, so it is not as “successful” as it should have. Maybe this happens because of the difficulty in finding easy information about GPL, or maybe because programmers don’t want to use GPL.
From the point of view of “copycenter”, it is best to have the “open core” software, “multi-licensing” than just the proprietary software. Also, nothing in life is: “100% free”, “100% do not pay”, “100% Libre”, “100% honest”, “100% public”, “100% commercial”, “100% private” , “100% owner”, “100% idealist”. Everything in life costs “time”, “money”, “dream”, “social relations”, “recognition”. When I speak of “cost”, I do not say in the “strict and economy” sense, but in the sense of “philosophical value”, “utility” as a “starting point to understand certain points” if “we are free” with “open source”. In this sense, there are always “risks”, “benefits” and “damage” to “open source”.
And all this can change to the “better or worse”. In this sense, we should not think that there are things in reality that they are - “unrestricted” or “restricted”. But there is an “intermediate layer or intermediate freedom with software”, which is “permissive”, “deliberative” as we may or may not solve life or software problems. What I mean here is that there is no “better and worse” scenario in software or open software licenses, it depends on what you want.
I never said, for example, that I don’t think “copyleft has no merits in terms of marketing and publicity around open software”. However, my criticism of “copyleft (gnu, fsf or projects licensed with gpl etc.)” is that the software was being left aside and continues to be left aside. Just like I talked about the “programming language and software problem”, where people with “copyleft” were much more concerned about bureaucracy than the end result of something open. Somehow this became “copyleft, a certain authoritarian copyright board for open software.” Although they (GNU or people who license things with GPL) say otherwise.
An interesting proof about this is the “many incompatibilities between the licenses produced: agpl-v1, gplv2 etc.” If there is incompatibility between licenses produced by GNU, in theory, they should be “non -free licenses” by OSD (Open Source definition). However, this does not work in practice. Since most “organizations have their own interests regarding what is opened”.
In addition, the FSF (Free Software Foundation) community has a different view of OSD(Open Source Definition), so there is an interesting problem with “who to talk about the open software.” Also, this returns to the question of “language programming and software”. If OSD (Open Source Definition) has a different point of view from the FSF (Free Software Foundation), the software licensed by FSF (Free Software Foundation) or GNU, will be open?
If you believe that “open software/open source” is “open” when there is “decentralization”. Therefore, FSF (Free Software Foundation) and OSD (Open Source Definition) should not be used as an argument - because we should consider other open source communities to check if we have “open software”, right?
Also, for example, most programming languages are made in english, so most programmers have to write in english. Therefore, there is a greater “language restriction” and “programming language” in software production for some starting programmers. If the source code is written in English, are the freedoms of the software only for those who speak or write in english?
Also, there is a problem of formalizing what we want to solve computationally or even developing a specific software license for the biggest use case. These formal problems are contained in what some call “bureaucracy” or for a better term “principle and practice”. How can we have less bureaucracy? How can we have greater principles and practices with open software?
Part of these problems occur in my analysis when there is a “formal metaphysics or formal materiality in open source”. In other words, when the principles do not work in practice, or when the practice is contrary to the principles. In the same way that people say that to have free software you need open hardware. In this case, “open software” is no longer relevant. Which isn’t quite true. One thing does not depend on the other, for example, the GPL does not talk about “hardware freedom”, but software freedom.
Therefore, if there is an even greater restriction on open software, perhaps the license will also be left aside as it does not represent the philosophy for which it was created.
In addition, all freedoms of open software require programming knowledge, so it makes no sense gives freedoms to users, because freedom should initially be for developers. Despite most people justifying the opposite.
What I mean by all this is that there is always dissatisfaction from developers or users, and there is not always a balance in all of this.
true.
This is true ±, because generally the GNU has a “purist” view of open software. This differs from the permissive view of licenses like MIT, BSD, Apache, Unlicensed etc; with “GPL”.
This is not true, because generally the GNU has a “purist” view of open software. This differs from the permissive view of licenses like MIT, BSD, Apache, Unlicensed, etc.
This I agree, that’s why I don’t understand people using things like GPL to launch “open software”, and in practice there are freedoms that are out of software. In this sense, GPL remains a “restricted, fanciful license” because it does not fulfill what it promises.
I agree with you here. I am really not trying to convince it otherwise, but that is why an permissive license like Apache, Mit, BSD has a longer reach to get a GPL license. So much so that the “copyleft community (GNU etc)” created the LGPL version as “alternative to MIT license or BSD, Apache”. In the sense of being a middle ground.
For me, these topics make no sense, because in a practical way discuss aspects of economy and politics, make no sense. It is better to discuss the aspect of culture or society with open software.
For me “copyleft makes no sense”, so I prefer “copycenter”. This is an interesting topic, but it is different from what we are proposing or discussing here. But there is something you would like to add very interesting here: Copyfree is not so different from the vision of the “transcopyright” license. According to the vision of the “transcopyright” license, everything we have in the world was done by someone today, in the past or in the future. So everyone has the same rights, duties, obligations in the legal sense, social of the word.
In this sense, even “copyleft” is a “shared rights movement”, in the sense that it allows for anyone the continuous manifestation and extension of their right. For example, by letting everyone freely copy your work, you are allowing people to manifest such a right. What does not nullify the objective to which copyright was made, although companies and industries in the past or even today have taken the fundamental rights to which copyright is still present.
“Transcopyright license” understands that any published material on the Internet is the right of everyone, so people can do whatever they want with this material, from charging a fair, expensive or free amount. For this reason some say the truth of “open software” is that “open software is a shareware”, it is software with few resources to which people use.
“Proof of this fact” are the different Linux distributions with different types of features and different types of target audience. In this case, it is still possible to have a trademark right on open software, as long as open software is shared with everyone.
It’s the same as Baserow, anyone can keep this software with any feature you want, now if you don’t want to keep this by a cloud feature that is kept by the brand that initially created the code. The overall and ultimate aspect of this is the right to reparable, that is, how something is open anyone can charge the price they want to repair their software, hardware etc.
Some copyleft problems may be more or less known, but some that I can mention are these:
“Ideology”: One of the problems that people complain most about the copyleft movement is that it has become a “sect”, an “ideology”. What has distanced and still distances many people and programmers with the GPL license. In addition, it distanced many companies, because companies could not understand the legal aspect of GNU philosophy or the aspect of GPL license. What created an even narrower division of the users with developers, where users thought developers were “employed” from the users. The GNU was so concerned with open software that it stopped creating open software. So much so that there is a relevant discussion here: “What is the reason that GNU Hurd did not become more popular than Linux?”
“Copyleft movement”:" Another problem related to copyleft is that the “copyleft movement” stopped worrying about the software, and was more concerned with the economy, politics leaving the software aside. Because of this, there was not so much mass adoption of something really open. For many, the biggest problem was the concentration of certain political and economic activism, failing to build an open ecosystem. Furthermore, there were many controversies said by the Richard Stallman.
“Copyright”: Another recurring problem was his own philosophy, which stated “created”, “could create” open software. But in general, it has removed rights from developers, and most programs are done by programmers and not by users. In addition, it brought a lot of greater “bureaucracy as much as the owner software companies”. To prove this, see that the source code is 2% of the source code is used for the GPL. Furthermore, for many, the copyleft movement was actually a “copyright hack”, which did not abolish copyright as you mention.
“Problems never solved:” Another problem was that the software was open, when there was never such a possibility that the software was opened by restricting licenses. Such proof is the versions of AGPL, GPLV3. In general, the problem when licensing copyleft software is version incompatibility.