Analysis of information sources in references of the Wikipedia article "Free and open-source software" in English language version.
FLOSS is an umbrella term covering a diversity of kinds of software and approaches to development [...] The distinction between free software and open-source software is sometimes controversial, and there are important differences between these two development communities [Kelty 2008]. However, our focus in this article is research on their development processes, which are acknowledged by participants to be largely similar [...], hence our use of this umbrella term.
The two predominant strains of FOSS licences are those that comply with the Open Source Initiative's 'Open Source Definition', and those that comply with the Free Software Foundation's 'Free Software Definition' [...] The list of 'open source' licences kept by the OSI, and of 'free' software licences kept by the FSF, are together called FOSS (free and open-source software) licences. All FOSS licences, because they meet the requirements of either OSI or FSF, should also meet our criteria for neutral voluntary licences and thus software licensed under them is part of the public domain.
While IBM's policy of withholding source code for selected software products has already marked its second anniversary, users are only now beginning to cope with the impact of that decision. But whether or not the advent of object-code-only products has affected their day-to-day DP operations, some users remain angry about IBM's decision. Announced in February 1983, IBM's object-code-only policy has been applied to a growing list of Big Blue system software products
The two predominant strains of FOSS licences are those that comply with the Open Source Initiative's 'Open Source Definition', and those that comply with the Free Software Foundation's 'Free Software Definition' [...] The list of 'open source' licences kept by the OSI, and of 'free' software licences kept by the FSF, are together called FOSS (free and open-source software) licences. All FOSS licences, because they meet the requirements of either OSI or FSF, should also meet our criteria for neutral voluntary licences and thus software licensed under them is part of the public domain.
FLOSS is an umbrella term covering a diversity of kinds of software and approaches to development [...] The distinction between free software and open-source software is sometimes controversial, and there are important differences between these two development communities [Kelty 2008]. However, our focus in this article is research on their development processes, which are acknowledged by participants to be largely similar [...], hence our use of this umbrella term.
The two predominant strains of FOSS licences are those that comply with the Open Source Initiative's 'Open Source Definition', and those that comply with the Free Software Foundation's 'Free Software Definition' [...] The list of 'open source' licences kept by the OSI, and of 'free' software licences kept by the FSF, are together called FOSS (free and open-source software) licences. All FOSS licences, because they meet the requirements of either OSI or FSF, should also meet our criteria for neutral voluntary licences and thus software licensed under them is part of the public domain.
The term "Free and Open Source Software" includes both, Free Software as defined by the Free Software Foundation and Open Source Software as defined by the Open Source Initiative. In the following article, the term Free and Open Source Software (FOSS) will be used.
"In some ways, Linux was the project that really made the split clear between what the FSF is pushing which is very different from what open source and Linux has always been about, which is more of a technical superiority instead of a -- this religious belief in freedom," Torvalds told Zemlin. "So, the GPL Version 3 reflects the FSF's goals and the GPL Version 2 pretty closely matches what I think a license should do and so right now, Version 2 is where the kernel is."
The Review does not endorse any one licensing model, focus or emphasis, but rather seeks, in an academically rigorous and objective manner, to increase the knowledge and understanding about the legal mechanisms used by all forms of Free and Open Source Software licences. It uses the term Free and Open Source Software to cover both Free Software and Open Source Software. FOSS is a term that can be used without particular bias towards either political approach.
Also note that the only valid version of the GPL as far as the kernel is concerned is _this_ particular version of the license (ie v2, not v2.2 or v3.x or whatever), unless explicitly otherwise stated.
[Blender's Toni Roosendaal:] "Blender is also still 'GPLv2 or later'. For the time being we stick to that, moving to GPL 3 has no evident benefits I know of."
Since BusyBox can be found in so many embedded systems, it finds itself at the core of the GPLv3 anti-DRM debate. [...]The real outcomes, however, are this: BusyBox will be GPLv2 only starting with the next release. It is generally accepted that stripping out the "or any later version" is legally defensible, and that the merging of other GPLv2-only code will force that issue in any case
Don't invent a straw man argument please. I consider licensing BusyBox under GPLv3 to be useless, unnecessary, overcomplicated, and confusing, and in addition to that it has actual downsides. 1) Useless: We're never dropping GPLv2.
Currently the decision to move from GPL v2 to GPL v3 is being hotly debated by many open source projects. According to Palamida, a provider of IP compliance software, there have been roughly 2489 open source projects that have moved from GPL v2 to later versions.
In 2001, VLC was released under the OSI-approved GNU General Public version 2, with the commonly-offered option to use "any later version" thereof (though there was not any such later version at the time). Following the release by the Free Software Foundation (FSF) of the new version 3 of its GNU General Public License (GPL) on the 29th of June 2007, contributors to the VLC media player, and other software projects hosted at videolan.org, debated the possibility of updating the licensing terms for future version of the VLC media player and other hosted projects, to version 3 of the GPL. [...] There is strong concern that these new additional requirements might not match the industrial and economic reality of our time, especially in the market of consumer electronics. It is our belief that changing our licensing terms to GPL version 3 would currently not be in the best interest of our community as a whole. Consequently, we plan to keep distributing future versions of VLC media player under the terms of the GPL version 2.
While IBM's policy of withholding source code for selected software products has already marked its second anniversary, users are only now beginning to cope with the impact of that decision. But whether or not the advent of object-code-only products has affected their day-to-day DP operations, some users remain angry about IBM's decision. Announced in February 1983, IBM's object-code-only policy has been applied to a growing list of Big Blue system software products
Currently the decision to move from GPL v2 to GPL v3 is being hotly debated by many open source projects. According to Palamida, a provider of IP compliance software, there have been roughly 2489 open source projects that have moved from GPL v2 to later versions.
Also note that the only valid version of the GPL as far as the kernel is concerned is _this_ particular version of the license (ie v2, not v2.2 or v3.x or whatever), unless explicitly otherwise stated.
"In some ways, Linux was the project that really made the split clear between what the FSF is pushing which is very different from what open source and Linux has always been about, which is more of a technical superiority instead of a -- this religious belief in freedom," Torvalds told Zemlin. "So, the GPL Version 3 reflects the FSF's goals and the GPL Version 2 pretty closely matches what I think a license should do and so right now, Version 2 is where the kernel is."
Since BusyBox can be found in so many embedded systems, it finds itself at the core of the GPLv3 anti-DRM debate. [...]The real outcomes, however, are this: BusyBox will be GPLv2 only starting with the next release. It is generally accepted that stripping out the "or any later version" is legally defensible, and that the merging of other GPLv2-only code will force that issue in any case
Don't invent a straw man argument please. I consider licensing BusyBox under GPLv3 to be useless, unnecessary, overcomplicated, and confusing, and in addition to that it has actual downsides. 1) Useless: We're never dropping GPLv2.
[Blender's Toni Roosendaal:] "Blender is also still 'GPLv2 or later'. For the time being we stick to that, moving to GPL 3 has no evident benefits I know of."
In 2001, VLC was released under the OSI-approved GNU General Public version 2, with the commonly-offered option to use "any later version" thereof (though there was not any such later version at the time). Following the release by the Free Software Foundation (FSF) of the new version 3 of its GNU General Public License (GPL) on the 29th of June 2007, contributors to the VLC media player, and other software projects hosted at videolan.org, debated the possibility of updating the licensing terms for future version of the VLC media player and other hosted projects, to version 3 of the GPL. [...] There is strong concern that these new additional requirements might not match the industrial and economic reality of our time, especially in the market of consumer electronics. It is our belief that changing our licensing terms to GPL version 3 would currently not be in the best interest of our community as a whole. Consequently, we plan to keep distributing future versions of VLC media player under the terms of the GPL version 2.
FLOSS is an umbrella term covering a diversity of kinds of software and approaches to development [...] The distinction between free software and open-source software is sometimes controversial, and there are important differences between these two development communities [Kelty 2008]. However, our focus in this article is research on their development processes, which are acknowledged by participants to be largely similar [...], hence our use of this umbrella term.
The Review does not endorse any one licensing model, focus or emphasis, but rather seeks, in an academically rigorous and objective manner, to increase the knowledge and understanding about the legal mechanisms used by all forms of Free and Open Source Software licences. It uses the term Free and Open Source Software to cover both Free Software and Open Source Software. FOSS is a term that can be used without particular bias towards either political approach.
The term "Free and Open Source Software" includes both, Free Software as defined by the Free Software Foundation and Open Source Software as defined by the Open Source Initiative. In the following article, the term Free and Open Source Software (FOSS) will be used.
