Code Forking, Governance, and Sustainability in Open Source Software
Open accessAbstract
IntroductionThis article addresses the question of how the right to fork open source projects – to use the source code of an existing program to start a new, independent version – works as a governance mechanism to provide sustainability in open source software. The concept of sustainability is under debate, with numerous rubrics against which the sustainability of a product
AI snapshot
Written from the paper’s full text.
TL;DR
This conceptual article argues that the right to fork open source code functions as a governance mechanism that helps ensure sustainability at the software, community, and ecosystem levels. It illustrates how forking counters planned obsolescence, gives communities an escape from unfavourable control, and enables innovation and commercialization.
Key findings
- The right to fork is intrinsic to open source licensing and affects governance and sustainability on three levels: software, community, and business ecosystem.
- On the software level, the right to fork makes planned obsolescence, versioning, vendor lock-in, and end-of-support issues “all but impossible” in open source; abandoned projects can also be revived, and of almost 400 forks studied by Nyman and Mikkonen (2011), 7% involved reviving an abandoned project.
- On the community level, forking provides an escape hatch against hijacking or unfavourable corporate/project-leader actions, as illustrated by MySQL leading to MariaDB and OpenOffice leading to LibreOffice; a cited analysis of LibreOffice indicates a sustainable community with no signs of stagnation.
- On the ecosystem level, forking acts as natural selection and a catalyst for innovation, enabling new distributions and business opportunities, such as Red Hat’s billion-dollar revenue and the many Linux distributions built from forked programs, or Jolla reviving MeeGo as Sailfish OS.
Methods
- Conceptual/analytical article, not an empirical study; it synthesizes literature and examples to examine how code forking affects governance and sustainability across three levels.
- Draws on secondary evidence and illustrative cases, including Nyman and Mikkonen’s (2011) dataset of almost 400 forks, MySQL/MariaDB, OpenOffice/LibreOffice, MeeGo/Sailfish OS, Red Hat, and Linux distributions.
- No formal sampling, primary data collection, or statistical analysis is described.
Limitations
- Stated: the authors simplified the categorization of forking for clarity; in actuality, the software, community, and ecosystem levels overlap.
- Evident: there is no dedicated limitations section, and the conceptual synthesis relies on selected examples and secondary sources rather than a systematic empirical test or generalizable sample.
- Evident: the examples are mostly high-profile projects, and the only quantitative fork outcome reported is the cited 7% revival figure from Nyman and Mikkonen (2011).
Model-written summary. Check it against the paper before relying on it.
Integrity signals
Registry
Cites
Statistics
Claims the paper makes
0 of 29 cited sources checked · 0 supported · 0 flagged
- Premisecitation
The LibreOffice fork has resulted in a sustainable community with no signs of stagnation.
“A recent analysis of the LibreOffice project indicates that this fork has resulted in a sustainable community with no signs of stagnation (Gamalielsson and Lundell, 2012; tinyurl.com/a9ev4hu).”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites Gamalielsson and Lundell, 2012
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- Interpretationreasoning
Forking, and even the mere possibility of forking code, affects the governance and sustainability of open source initiatives on three distinct levels: software, community, and ecosystem.
“Forking, and even the mere possibility of forking code, affects the governance and sustainability of open source initiatives on three distinct levels: software, community, and ecosystem.”
Quote in the paperNot a substantial claim - Premisecitation
The openness combined with the granular composition of the software offer new ways of governance.
“The openness combined with the granular composition of the software offer new ways of governance (Benkler, 2006;tinyurl.com/6ftot3).”
Quote in the paperSubstantial claim0 of 1 sources checked- cites Benkler, 2006
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- Interpretationcitation
Forking allows innovators to introduce new functionalities into the market.
“Forking lays the building blocks for innovators to introduce new functionalities into the market”
Quote in the paperNot a substantial claim - Interpretationcitation
The practice of forking allows for the development of a robust, responsive software ecosystem that is able to meet an abundance of demands.
“Hence, the practice of forking allows for the development of a robust, responsive software ecosystem that is able to meet an abundance of demands (Nyman et al., 2012;tinyurl.com/acg3fp2).”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites Nyman et al., 2012
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- Premisecitation§ Code Forking, Governance, and Sustainability in Open Source Software
In a study of almost 400 forks, 7% involved reviving an abandoned project.
“of the almost 400 forks studied by Nyman and Mikkonen (2011; tinyurl.com/arntyur),7% involved the reviving of an abandoned project.”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites Nyman and Mikkonen (2011)
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- Interpretationnone given
On a software level, code forking serves as a governance mechanism for sustainability by offering a way to overcome planned obsolescence and decay, as well as versioning, lock-in, and related concerns.
“On a software level, code forking serves as a governance mechanism for sustainability by offering a way to overcome planned obsolescence and decay, as well as versioning, lock-in, and related concerns.”
Quote in the paperNot a substantial claim - Premisecitation
The most common reason projects are forked is the desire to modify the original program to better address a specific need.
“While there are many reasons why projects are forked, the most common reason is the desire to modify the original program to better address a specific need”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites Nyman and Mikkonen, 2011
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- Interpretationreasoning
Code forking bolsters program sustainability.
“In addition to bolstering program sustainability, code forking directly affects the governance of open source initiatives.”
Quote in the paperSubstantial claim - Interpretationreasoning
The ability to change and evolve is a key component of software sustainability.
“Therefore, the ability to change and evolve is a key component of software sustainability.”
Quote in the paperSubstantial claim - Interpretationnone given
The right to fork means that any company can duplicate any competitor's open source software distributions.
“However, the right to fork means that any company can duplicate any competitor's open source software distributions”
Quote in the paperNot a substantial claim- Rests on an assumption: The shared ownership of open source projects allows anyone to fork a project at any time.
- Interpretationcitation
Forking is the 'invisible hand of sustainability' in open source software.
“we have previously described forking as the “invisible hand of sustainability” in open source software (Nyman et al., 2011; tinyurl.com/b8bzorg).”
Quote in the paperSubstantial claim0 of 1 sources checked- cites Nyman et al., 2011
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- Interpretationreasoning
Software is prone to being changed, repaired, and updated rather than remaining fixed from the early stages of the design process.
“These characteristics dictate that software is prone to being changed, repaired, and updated rather than remaining fixed from the early stages of the design process.”
Quote in the paperSubstantial claim - Interpretationreasoning
Forking provides the community that supports an open source project with a way to spin off their own version of the project in case of an acquisition.
“Forking provides the community that supports an open source project with a way to spin off their own version of the project in case of such an acquisition.”
Quote in the paperSubstantial claim- Rests on an assumption: The shared ownership of open source projects allows anyone to fork a project at any time.
- Rests on an assumption: The 2008 acquisition of MySQL by Sun Microsystems and subsequent acquisition of Sun by Oracle occurred and involved community concern over potential hijacking.
- Interpretationreasoning
Any program with the support of the open source community can enjoy assured relevance rather than planned obsolescence.
“The result of this constant collaborative improvement in open source systems is that any program with the support of the open source community can enjoy assured relevance rather than planned obsolescence.”
Quote in the paperSubstantial claim- The authors state this as an assumption: The open source definition includes the rights to improve a program, to combine many programs, and to make a program compatible with other programs and versions.
- Interpretationreasoning
Forking allows rapid adaptation to the needs of end users.
“allowing for the rapid adaptation to the needs of end users.”
Quote in the paperNot a substantial claim - Interpretationreasoning
When forks address disparate community needs, different versions can prosper.
“When they address disparate community needs, different versions can prosper.”
Quote in the paperSubstantial claim - Premisecitation
In 2010, community concerns regarding governance led to a forking of the OpenOffice project, with The Document Foundation forking the OO code to begin LibreOffice.
“in 2010, community concerns regarding gov- ernance led to a forking of the OpenOffice (OO; open office.org) project. The Document Foundation, which in-cluded a team of long-term contributors to OO, forked the OO code to begin LibreOffice”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites The Document Foundation
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- Interpretationreasoning
Competitive advantage in open source cannot depend on the quality of the code alone.
“thus, competitive advantage cannot depend on the quality of the code alone.”
Quote in the paperSubstantial claim - Premisecitation
Hundreds of different Linux distributions are all made possible by forking existing products and repackaging them as a new release.
“This phenomenon of combining forked programs is not unique to Red Hat: the hundreds of different Linux distributions (tinyurl.com/85r9o)are all made possible by the forking of existing products and repackaging them as a new release.”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites tinyurl.com/85r9o
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- Interpretationreasoning
Open source companies can and do thrive despite the right to fork.
“While the right to fork may seem to make for a harsh business environment, open source companies can and do thrive.”
Quote in the paperNot a substantial claim- Rests on an assumption: Red Hat's programs are largely based on forks of programs by other developers.
- Interpretationnone given
Code forking directly affects the governance of open source initiatives.
“In addition to bolstering program sustainability, code forking directly affects the governance of open source initiatives.”
Quote in the paperNot a substantial claim - Interpretationcitation
Programs must continue to evolve in order to remain useful and relevant.
“They must continue to evolve in order to remain useful and relevant.”
Quote in the paperSubstantial claim- Rests on an assumption: The nature of the industry dictates that programs cannot maintain a stable steady state for an extended period of time.
- Interpretationreasoning
No one person or group has a 'magical hold' over an open source project.
“Therefore, no one person or group has a “magical hold” over the project (Fogel, 2006;tinyurl.com/ahbh8nt).”
Quote in the paperSubstantial claim0 of 1 sources checked- cites Fogel, 2006
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- Rests on an assumption: The shared ownership of open source projects allows anyone to fork a project at any time.
- Interpretationreasoning
The possibility to fork is central to the governance of any open source community.
“The possibility to fork is central to the governance of any open source community.”
Quote in the paperSubstantial claim- Rests on an assumption: The shared ownership of open source projects allows anyone to fork a project at any time.
- Interpretationreasoning
The right to fork a commercially successful program with the intention of competing for the same customer base still leaves the would-be competitor with issues regarding trademarks, brand value and recognition, as well as the existing developer and user base.
“The right to fork a commercially successful program with the intention of competing for the same customer base still leaves the would-be competitor with issues regarding trademarks, brand value and recognition, as well as the existing developer and user base”
Quote in the paperNot a substantial claim - Interpretationreasoning
The right to fork code makes implementing planned obsolescence elements impracticable in open source.
“The right to fork code makes implementing such elements impracticable in open source.”
Quote in the paperNot a substantial claim- The authors state this as an assumption: The open source definition includes the rights to improve a program, to combine many programs, and to make a program compatible with other programs and versions.
- Premisecitation
All open source licenses grant the right to fork their code.
“All open source licenses grant the right to fork their code, that is to start a new development effort using an existing code as its base.”
Quote in the paperSubstantial claim0 of 2 sources checked- cites OSI
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- cites FSD
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- Premisecitation
Without continual adaptation, a program will progressively become less satisfactory.
“Without continual adaptation, a program will progressively become less satisfactory (Lehman, 1980;tinyurl.com/b2mpkw3).”
Quote in the paperSubstantial claim0 of 1 sources checked- cites Lehman, 1980
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- Premisecitation
Truly successful software is able to adapt and even out-live the hardware for which it was originally written.
“Conversely, truly successful software is able to adapt and even out-live the hardware for which it was originally written (Brooks, 1975;tinyurl.com/awg3rrw).”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites Brooks, 1975
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- Premisecitation
Jolla announced it would create a business around reviving the abandoned MeeGo project, made possible by forking the original code.
“Soon after Nokia's abandonment of the MeeGo project in 2011 (press release: tinyurl.com/ad5lh6b; MeeGo summary: tinyurl.com/9u4xrno), the Finnish com-pany Jolla announced that it would create a business around its revival, made possible by forking the original code (press release: tinyurl.com/7bzbo9h).”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites tinyurl.com/7bzbo9h
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- Classified as probably not a substantial claim. 33
- May combine two claims. 13
Probably not a substantial claim: may not pass S2 (checkable). May combine two claims.
InterpretationreasoningIt is the right to fork that moulds the governance of open source projects and provides the dynamic vigour found in open source computing today.
“It is the right to fork that moulds the governance of open source projects and provides the dynamic vigour found in open source computing today.”
Quote in the paperNot a substantial claim- Rests on an assumption: The right to fork code is intrinsic to open source software and is guaranteed by all open source licenses.
Probably not a substantial claim: may not pass S4 (based).
Interpretationreasoning§ Code Forking, Governance, and Sustainability in Open Source SoftwareAs long as there is sufficient community interest in a project, forking can allow for constant improvement in software functionality.
“As long as there is sufficient community interest in a project, forking can allow for constant improvement in software functionality.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S4 (based). May combine two claims.
Interpretationnone givenBoth a poorly handled community and an abandoned project can spawn a business ecosystem competitor.
“Both a poorly handled community and an abandoned project can spawn a business ecosystem competitor.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S2 (checkable), S3 (load-bearing).
PremisecitationIn recent years, the term forking has come to be used in a much broader context, encompassing all cases in which one takes an existing code base and implements it in a separate project.
“has come to be used in a much broader context, encompassing all cases in which one takes an existing code base and implements it in a separate project (see, for instance, GitHub: tinyurl.com/7uc94sk).”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites GitHub
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
Probably not a substantial claim: may not pass S3 (load-bearing).
PremisecitationThe potential to fork a program is 'the indispensable ingredient that binds developers together'.
“Fogel notes that the potential to fork a program is “the indispensable ingredient that binds developers together”.”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites Fogel, 2006
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
Probably not a substantial claim: may not pass S3 (load-bearing).
InterpretationreasoningThe right to fork code is built into the very definition of what it means to be an open source program.
“The right to fork code is built into the very definition of what it means to be an open source program.”
Quote in the paperNot a substantial claimClassified as probably not a substantial claim. May combine two claims.
InterpretationreasoningForking helps keep open source initiatives relevant and presents opportunities for the development and commercialization of current and abandoned programs.
“Thus, forking helps keep open source initiatives relevant and presents opportunities for the development and commercialization of current and abandoned programs.”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S4 (based).
Interpretationnone givenForking cannot be prevented by business models or governance systems.
“Forking cannot be prevented by business models or governance systems.”
Quote in the paperNot a substantial claim- Rests on an assumption: The shared ownership of open source projects allows anyone to fork a project at any time.
Classified as probably not a substantial claim. May combine two claims.
PremisecitationOpen source companies can be bought, but open source communities cannot.
“Moody (2009; tinyurl.com/ cbrq7g) noted that, while open source companies can be bought, open source communities cannot.”
Quote in the paperSubstantial claim0 of 1 sources checked- cites Moody, 2009
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
May combine two claims.
PremisecitationThe rights to improve a program, to combine many programs, and to make a program compatible with other programs and versions are often exercised in open source.
“Research has shown these rights are often exercised (Fitzgerald, 2006; tinyurl.com/al995aj).”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites Fitzgerald, 2006
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Interpretationnone givenBetter software can more easily attract a bigger community.
“better software can more easily attract a bigger community.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S4 (based).
Interpretationnone givenThe potential of forking in open source software, particularly when coupled with a strong community, provides opportunities to avoid versioning and vendor lock-in to one provider.
“When acquiring systems, the potential of forking in open source software -in particular when coupled with a strong community -provides opportunities to avoid versioning and vendor lock-in to one provider of a product or system.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
InterpretationreasoningOne does not need to be an open source business to benefit from the right to fork.
“However, one does not need to be an open source business to benefit from the right to fork.”
Quote in the paperNot a substantial claimClassified as probably not a substantial claim.
Interpretationnone givenCurrent projects can be forked.
“Current projects can be forked”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Interpretationnone givenAn abandoned project can become a business opportunity.
“An abandoned project can become a business opportunity.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S2 (checkable), S4 (based).
Interpretationnone givenOn a community level, code forking ensures sustainability by providing the community with an escape hatch: the right to start a new version of the program.
“On a community level, code forking ensures sustainability by providing the community with an escape hatch: the right to start a new version of the program.”
Quote in the paperNot a substantial claimMay combine two claims.
PremisecitationThis governance is not tied to over-appropriating a natural resource, but rather related to ways in which a group of developers, following institutional rules, collectively produce a public good.
“This governance is not tied to over-appropriating a natural resource (Ostrom, 1991; tinyurl.com/b8rc2pu),but rather related to ways in which a group of developers, following institutional rules, collectively produce a public good (Schweik et al., 2010;tinyurl.com/aqxy2jp).”
Quote in the paperSubstantial claim0 of 2 sources checked- cites Ostrom, 1991
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- cites Schweik et al., 2010
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
Classified as probably not a substantial claim.
PremisecitationUntil recently, the term fork was mainly used to describe a situation in which a developer community had split into competing camps, each continuing work on their own, incompatible version of the software.
“Until recently, the term fork was mainly used to describe a situation in which a developer community had split into competing camps, each continuing work on their own, incompatible version of the software”
Quote in the paperSubstantial claim0 of 2 sources checked- cites Raymond, 1999
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- cites Fogel, 2006
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
Probably not a substantial claim: may not pass S3 (load-bearing).
InterpretationreasoningForking can aid companies who choose to use an existing program, or develop it for personal use.
“Forking can also aid companies who choose to use an existing program, or develop it for personal use.”
Quote in the paperNot a substantial claimMay combine two claims.
PremisecitationMichael Widenius forked the MySQL code and started MariaDB due to concerns regarding the governance and future openness of the MySQL code.
“The original MySQL developer, Michael (“Monty”) Widenius, forked the MySQL code and started a new version under a different name, MariaDB, due to concerns regarding the governance and future openness of the MySQL code”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites Widenius' blog
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
Probably not a substantial claim: may not pass S2 (checkable), S4 (based). May combine two claims.
InterpretationreasoningOn an ecosystem level, forking serves as a core component of natural selection and as a catalyst for innovation.
“Finally, on an ecosystem level, forking serves as a core component of natural selection and as a catalyst for innovation.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S4 (based).
InterpretationreasoningThe right to fork open source code is at the core of open source licensing.
“The right to fork open source code is at the core of open source licensing.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing). May combine two claims.
PremisecitationJolla announced a contract with D. Phone on July 16, 2012, and launched Sailfish OS on November 21.
“On July 16, 2012, Jolla announced a contract with D. Phone, one of the largest cell phone retailers in China, and on November 21 they launched Sailfish OS (tinyurl.com/a4yot8h).”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites tinyurl.com/a4yot8h
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
May combine two claims.
InterpretationreasoningAbandoned projects can be revived and commercialized.
“abandoned projects can be revived and commercialized”
Quote in the paperSubstantial claimProbably not a substantial claim: may not pass S2 (checkable), S4 (based). May combine two claims.
Interpretationnone givenThis right to fork has a significant effect on governance and helps ensure the sustainability of open source software.
“This right to fork has a significant effect on governance and helps ensure the sustainability of open source software.”
Quote in the paperNot a substantial claim- Rests on an assumption: The right to fork code is intrinsic to open source software and is guaranteed by all open source licenses.
Probably not a substantial claim: may not pass S2 (checkable), S4 (based).
InterpretationreasoningThe possibility of forking any project affects the governance and sustainability of all open source programs.
“The possibility of forking any project affects the governance and sustainability of all open source programs.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
PremisecitationThe third criteria of the Open Source Initiative's (OSI) definition of open source states that the license must allow modifications and derived works.
“The third criteria of the Open Source Initiative's (OSI; opensource.org/osd.html)definition of open source states that the license”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites OSI
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
Probably not a substantial claim: may not pass S3 (load-bearing).
InterpretationcitationAll spinoff initiatives can be considered forks as they are modified or derived (OSI) or copied, changed and improved.
“All spinoff initiatives can be considered forks as they are”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites OSI
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
Probably not a substantial claim: may not pass S3 (load-bearing).
PremisecitationIn open source software, natural selection acts as a culling force, constantly choosing only the fittest code to survive.
“Within the dynamic world of open source software, natural selection acts as a culling force, constantly choosing only the fittest code to survive (Torvalds, 2001; tinyurl.com/aaxqux7).”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites Torvalds, 2001
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
Probably not a substantial claim: may not pass S4 (based).
Interpretationnone givenNeither business models nor governance systems can completely prevent forking.
“Neither business models nor governance systems can completely prevent forking.”
Quote in the paperNot a substantial claim- Rests on an assumption: The right to fork code is intrinsic to open source software and is guaranteed by all open source licenses.
Probably not a substantial claim: may not pass S3 (load-bearing), S4 (based).
Interpretationnone givenOn the community level, forking impacts both sustainability and governance through the power it grants the community to safeguard against unfavourable actions by corporations or project leaders.
“On the community level, forking impacts both sustainability and governance through the power it grants the community to safeguard against unfavourable actions by corporations or project leaders.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S2 (checkable), S3 (load-bearing), S4 (based). May combine two claims.
Interpretationnone givenOn the business-ecosystem level forking can serve as a catalyst for innovation while simultaneously promoting better quality software through natural selection.
“On the business-ecosystem level forking can serve as a catalyst for innovation while simultaneously promoting better quality software through natural selection.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
InterpretationreasoningThe negative tone found in discussions of forking has been related to concerns regarding the hindered progress, wasted resources, and potential demise of one or both of the projects.
“Hence, the negative tone found in discussions of forking has been related to concerns regarding the hindered progress, wasted resources, and potential demise of one or both of the projects.”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S2 (checkable), S4 (based).
Interpretationnone givenA strong community offers better insurance of sustainability of the software level.
“a strong community offers better insurance of sustainability of the software level”
Quote in the paperNot a substantial claimProbably not a substantial claim: may not pass S3 (load-bearing).
PremisecitationOpen source software is increasingly developed and supported for commercial gains.
“Open source software is free, but it is also increasingly developed and supported for commercial gains (Wheeler, 2009: timreview.ca/article/229).”
Quote in the paperNot a substantial claim0 of 1 sources checked- cites Wheeler, 2009
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
Classified as probably not a substantial claim. May combine two claims.
PremisecitationSoftware is editable, interactive, reprogrammable, distributed, and open.
“Software is editable, interactive, reprogrammable, distributed, and open (Kallinikos et al., 2010;tinyurl.com/4zn6cun).”
Quote in the paperSubstantial claim0 of 1 sources checked- cites Kallinikos et al., 2010
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
Probably not a substantial claim: may not pass S2 (checkable), S3 (load-bearing), S4 (based).
InterpretationreasoningPrograms can be combined in novel ways to better meet the needs of both the developers and end users.
“programs can be combined in novel ways to better meet the needs of both the developers and end users.”
Quote in the paperNot a substantial claim
The paper relies on this without support.
The nature of the industry dictates that programs cannot maintain a stable steady state for an extended period of time.
“The nature of the industry dictates that programs cannot maintain a stable steady state for an extended period of time.”
The paper relies on this without support.
Obsolescence need not creep into a project over time; it is often a design feature.
“Although stagnation may be a precursor to obsolescence, obsolescence need not creep into a project over time; it is often a design feature.”
The paper relies on this without support.
The shared ownership of open source projects allows anyone to fork a project at any time.
“The shared ownership of open source projects allows anyone to fork a project at any time.”
The authors state this as an assumption.
The open source definition includes the rights to improve a program, to combine many programs, and to make a program compatible with other programs and versions.
“The right to improve a program, the right to combine many programs, and the right to make a program compatible with other programs and versions are all fundamental rights that are built into the very definition of open source.”
The paper relies on this without support.
The 2008 acquisition of MySQL by Sun Microsystems and subsequent acquisition of Sun by Oracle occurred and involved community concern over potential hijacking.
“The 2008 acquisition of MySQL (mysql.com),an open source relational database management system, by Sun Microsystems and subsequent acquisition of Sun by Oracle is an example of a case involving community concern over potential hijacking.”
The paper relies on this without support.
The right to fork code is intrinsic to open source software and is guaranteed by all open source licenses.
“The right to fork code is intrinsic to open source software and is guaranteed by all open source licenses.”
The paper relies on this without support.
The requirement in open source to share one's source code is linked with distribution, not modification, so one can fork and modify a program for in-house use without having to supply the code to others.
“The requirement in open source to share one's source code is linked with distribution, not modification, which means that one can fork a program and modify it for in-house use without having to supply the code to others.”
“Keep in mind that it is distribution, not modification, that obligates the sharing of the source code.”
The paper relies on this without support.
There are thousands of open source programs already in existence, which can be forked.
“There are thousands of open source programs already in existence, which can be forked.”
The paper relies on this without support.
Online forges have hundreds of thousands of programs available for forking and reuse.
“the plethora of online forges have hundreds of thousands of programs available for forking and reuse in any new, creative way the user can imagine”
“Online forges offer a plethora of publically available programs that can serve as the building blocks of a new creation.”
The paper relies on this without support.
Red Hat's programs are largely based on forks of programs by other developers.
“Red Hat's programs themselves are largely based on forks of programs by other developers.”
Cited by
Sorted by citations
The invisible politics of Bitcoin: governance crisis of a decentralised infrastructure
De Filippi, P., & Loveluck, B. (2016) · Internet Policy Review · doi:10.14763/2016.3.427 · Cited by 298 · see citing works
Karhu, K., Gustafsson, R., & Lyytinen, K. (2018) · Information Systems Research · doi:10.1287/isre.2018.0786 · Cited by 286 · see citing works
Defining Blockchain Governance: A Framework for Analysis and Comparison
van Pelt, R., Jansen, S., Baars, D., & Overbeek, S. (2020) · Information systems management · doi:10.1080/10580530.2020.1720046 · Cited by 164 · see citing works
Digital sustainability: basic conditions for sustainable digital artifacts and their ecosystems
Stuermer, M., Abu-Tayeh, G., & Myrach, T. (2016) · Sustainability Science · doi:10.1007/s11625-016-0412-2 · Cited by 163 · see citing works
Gamalielsson, J., & Lundell, B. (2014) · Journal of Systems and Software · doi:10.1016/j.jss.2013.11.1077 · Cited by 125 · see citing works
Why and how developers fork what from whom in GitHub
Jiang, J., Lo, D., He, J., et al. (2016) · Empirical Software Engineering · doi:10.1007/s10664-016-9436-6 · Cited by 122 · see citing works
BornAgain : software for simulating and fitting grazing-incidence small-angle scattering
Pospelov, G., Herck, W. V., Burle, J., Loaiza, J. M. C., Durniak, C., Fisher, J. M., Ganeva, M., Yurov, D., & Wuttke, J. (2020) · Journal of Applied Crystallography · doi:10.1107/s1600576719016789 · Cited by 123 · see citing works
Faqir-Rhazoui, Y., Arroyo, J., & Hassan, S. (2021) · Journal of Internet Services and Applications · doi:10.1186/s13174-021-00139-6 · Cited by 128 · see citing works
Now the code runs itself: On-chain and off-chain governance of blockchain technologies
Reijers, W., Wuisman, I., Mannan, M., De Filippi, P., Wray, C., Rae-Looi, V., Cubillos Vélez, A., & Orgad, L. (2021) · Topoi · doi:10.1007/s11245-018-9626-5 · Cited by 165 · see citing works
Bogusz, C. I., Laurell, C., & Sandström, C. G. (2020) · IEEE Transactions on Engineering Management · doi:10.1109/tem.2020.2984032 · Cited by 78 · see citing works
Design choices for next-generation IIoT-connected MES/MOM: An empirical study on smart factories
Mantravadi, S., Møller, C., Chen, L. I., & Schnyder, R. (2021) · Robotics and Computer-Integrated Manufacturing · doi:10.1016/j.rcim.2021.102225 · Cited by 70 · see citing works
Andersen, J. V., & Bogusz, C. I. (2019) · Journal of the Association for Information Systems · doi:10.17705/1jais.00566 · Cited by 64 · see citing works
Reuse and maintenance practices among divergent forks in three software ecosystems
Businge, J., Openja, M., Nadi, S., & Berger, T. (2022) · Empirical Software Engineering · doi:10.1007/s10664-021-10078-2 · Cited by 39 · see citing works
Sustaining platforms as commons: perspectives on participation, infrastructure, and governance
Poderi, G. (2019) · CoDesign · doi:10.1080/15710882.2019.1631351 · Cited by 35 · see citing works
Islam, N., Mäntymäki, M., & Turunen, M. (2019) · Proceedings of the Annual Hawaii International Conference on System Sciences · doi:10.24251/hicss.2019.556 · Cited by 24 · see citing works
Governance of decentralized autonomous organizations that produce open source software
van Vulpen, P., Siu, J., & Jansen, S. (2023) · Blockchain: Research and Applications · doi:10.1016/j.bcra.2023.100166 · Cited by 9 · see citing works
Open Source Community Health: Analytical Metrics and Their Corresponding Narratives
Goggins, S., Lumbard, K., & Germonprez, M. (2021) · International Workshop on Software Health · doi:10.1109/soheal52568.2021.00010 · Cited by 36 · see citing works
Designing a 6G Testbed for Location: Use Cases, Challenges, Enablers and Requirements
Khatib, E. J., Alvarez-Merino, C. S., Luo-Chen, H. Q., & Barco, R. (2023) · IEEE Access · doi:10.1109/access.2023.3240775 · Cited by 18 · see citing works
Creative evolution in economics
Devereaux, A. N., Koppl, R. G., & Kauffman, S. A. (2024) · Journal of Evolutionary Economics · doi:10.1007/s00191-024-00855-9 · Cited by 18 · see citing works
Corporate Governance for Complex Cryptocurrencies?
Hacker, P. (2019) · doi:10.1093/oso/9780198842187.003.0008 · Cited by 17 · see citing works
Nyman, L. (2014) · International Symposium on Open Collaboration · doi:10.1145/2641580.2641590 · Cited by 16 · see citing works
Self-citationFrom archive to analysis: accessing web archives at scale through a cloud-based interface
Ruest, N., Fritz, S., Deschamps, R., Lin, J., & Milligan, I. (2021) · International Journal of Digital Humanities · doi:10.1007/s42803-020-00029-6 · Cited by 15 · see citing works
Linåker, J., Regnell, B., & Damian, D. (2019) · Information and Software Technology · doi:10.1016/j.infsof.2019.04.010 · Cited by 14 · see citing works
Musiani, F., & Ermoshina, K. (2022) · Mattering Press eBooks · doi:10.28938/9781912729227 · Cited by 19 · see citing works
(De)centralization in the governance of blockchain systems: cryptocurrency cases
Heo, K., & Yi, S. (2023) · Journal of Organization Design · doi:10.1007/s41469-023-00138-w · Cited by 14 · see citing works
Good modelling software practices
Lemmen, C., & Sommer, P. S. (2024) · Ecological Modelling · doi:10.1016/j.ecolmodel.2024.110890 · Cited by 10 · see citing works
Nyman, L. (2015) · Työväentutkimus Vuosikirja · doi:10.13140/rg.2.1.3878.4089 · Cited by 10 · see citing works
Self-citationGermonprez, M., Kendall, J. E., Kendall, K. E., & Young, B. (2014) · International Journal of Information Systems and Management · doi:10.1504/ijisam.2014.062290 · Cited by 10 · see citing works
Understanding the Archived Projects on GitHub
Xia, X., Zhao, S., Zhang, X., et al. (2023) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner56733.2023.00012 · Cited by 9 · see citing works
Ye, Y., Barapatre, S., Davis, M. K., et al. (2021) · Journal of Medical Internet Research · doi:10.2196/20028 · Cited by 9 · see citing works
AI Development and the ‘Fuzzy Logic' of Chinese Cyber Security and Data Laws
Parasol, M. (2021) · Cambridge University Press eBooks · doi:10.1017/9781009064804 · Cited by 8 · see citing works
An empirical investigation of social comparison and open source community health
Lumbard, K., Germonprez, M., & Goggins, S. (2023) · Information Systems Journal · doi:10.1111/isj.12485 · Cited by 7 · see citing works
Zimmermann, T. (2020) · doi:10.1145/3387940.3392209 · Cited by 7 · see citing works
SarkinTudu, S. M., Wahab, A. A., & Ibrahim, H. (2022) · Interdisciplinary Journal of Information Knowledge and Management · doi:10.28945/5022 · Cited by 7 · see citing works
Variant Forks - Motivations and Impediments
Businge, J., Zerouali, A., Decan, A., Mens, T., Demeyer, S., & De Roover, C. (2022) · 2022 IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner53432.2022.00105 · Cited by 7 · see citing works
Free Software, the Internet, and Global Communities of Resistance
Schoonmaker, S. (2018) · doi:10.4324/9781315672786 · Cited by 6 · see citing works
A regulatory control framework for decentrally governed DLT systems: Action design research
Benedict, G., & Gill, A. (2021) · Information Manager (The) · doi:10.1016/j.im.2021.103555 · Cited by 5 · see citing works
Fathoming Software Evangelists with the D-Index
Borreguero, F., Nitto, E. D., Stebliuk, D., Tamburri, D. A., & Zheng, C. (2015) · International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE) · doi:10.1109/chase.2015.26 · Cited by 5 · see citing works
Digital Preservation through Digital Sustainability
Stuermer, M., & Abu-Tayeh, G. (2017) · Bern Open Repository and Information System (University of Bern) · doi:10.7892/boris.98845 · Cited by 5 · see citing works
Autonocoin: A Proof-of-Belief Cryptocurrency
Abramowicz, M. (2016) · Ledger · doi:10.5195/ledger.2016.37 · Cited by 5 · see citing works
Ikuine, F., & FUJITA, H. (2014) · Annals of Business Administrative Science · doi:10.7880/abas.13.283 · Cited by 4 · see citing works
The sustainability of quality in free and open source software
Alami, A. (2020) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/3377812.3381402 · Cited by 4 · see citing works
Desarrollo Floss y gobernanza de pares: el caso del entorno de escritorio Gnome
Zanotti, A., & Vélez, J. G. (2020) · International Journal of Innovation · doi:10.5585/iji.v8i3.17114 · Cited by 3 · see citing works
Sustainability Forecasting for Deep Learning Packages
Han, J., Wang, Y., Liu, Z., et al. (2024) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner60148.2024.00106 · Cited by 3 · see citing works
Toward Governance Best Practices for Open Educational Resources
Daly, D., Schneider, N., & Ahmad, H. (2024) · Proceedings of the ALISE Annual Conference · doi:10.21900/j.alise.2024.1749 · Cited by 2 · see citing works
Lovett, M., & Thomas, L. (2021) · First Monday · doi:10.5210/fm.v26i11.12357 · Cited by 2 · see citing works
Wikipedia y la gobernanza de pares
Zanotti, A. (2022) · Hipertextos · doi:10.24215/23143924e056 · Cited by 2 · see citing works
Beyond Microsoft and Monsanto: Denaturing the Monoculture Metaphor in Computing
Tanfield-Taylor, J., Mirizio, A., Greene, B., & Ensmenger, N. L. (2026) · CHI Conference on Human Factors in Computing Systems · doi:10.1145/3772318.3790769 · Cited by 1 · see citing works
An Empirical Investigation of Forks as Variants in the npm Package Distribution.
Businge, J., Decan, A., Zerouali, A., et al. (2020) · ORBi UMONS · Cited by 2 · see citing works
Freedom and forking in open source software: the MariaDB story
Nyman, L. (2013) · Työväentutkimus Vuosikirja · Cited by 2 · see citing works
Self-citationBogusz, C. I., & Andersen, J. V. (2021) · Hawaii International Conference on System Sciences (HICSS) · doi:10.24251/hicss.2021.770 · Cited by 2 · see citing works
Impact on Artificial Intelligence
Parasol, M. (2021) · Cambridge University Press eBooks · doi:10.1017/9781009064804.008 · Cited by 2 · see citing works
Forking From the Future: How an Interorganizational Network Learned Its Way to New Software Business
Järvenpää, S. L., & Välikangas, L. (2022) · IEEE Transactions on Engineering Management · doi:10.1109/tem.2022.3193959 · Cited by 1 · see citing works
Motivations, Development Challenges and Project Desertion in Public Blockchain: A Pilot Study
Wahab, A. A., SarkinTudu, S. M., & Ibrahim, H. (2023) · Lecture notes on data engineering and communications technologies · doi:10.1007/978-3-031-36258-3_23 · Cited by 1 · see citing works
Open source digital sovereignty: the case for a Canadian national Linux distribution
Pearce, J. M. (2026) · Digital Policy Regulation and Governance · doi:10.1108/dprg-06-2026-0347 · Cited by 1 · see citing works
Analyzing Variant Forks of Software Repositories from Social Coding Platforms
Businge, J., Abdi, M., & Demeyer, S. (2023) · Software Ecosystems · doi:10.1007/978-3-031-36060-2_6 · Cited by 1 · see citing works
Fathoming software evangelists with the D-index
Borreguero, F., Nitto, E. D., Stebliuk, D., Tamburri, D. A., & Zheng, C. (2015) · doi:10.5555/2819321.2819337
Competitive Strategy of Proprietary Software Firms in an Open Source EnvironmentPreprint
Baranes, E., Vuong, C. H., & Zéroukhi, M. (2020) · SSRN Electronic Journal
An Empirical Study of Technical Debt Management as a Motivation for Forking.
Njima, M. N., Businge, J., & Demeyer, S. (2020)
China’s Data Security Policies Leading to the Cyber Security Law
Parasol, M. (2021) · Cambridge University Press eBooks · doi:10.1017/9781009064804.006
Historical and Doctrinal Background
Parasol, M. (2021) · Cambridge University Press eBooks · doi:10.1017/9781009064804.002
Parasol, M. (2021) · Cambridge University Press eBooks · doi:10.1017/9781009064804.015
Parasol, M. (2021) · Cambridge University Press eBooks · doi:10.1017/9781009064804.001
Data Protection but Not Data Privacy
Parasol, M. (2021) · Cambridge University Press eBooks · doi:10.1017/9781009064804.010
Parasol, M. (2021) · Cambridge University Press eBooks · doi:10.1017/9781009064804.007
Parasol, M. (2021) · Cambridge University Press eBooks · doi:10.1017/9781009064804.013
Parasol, M. (2021) · Cambridge University Press eBooks · doi:10.1017/9781009064804.004
The Impacts of Data Localisation on Globalised Ecosystems and Chinese Tech
Parasol, M. (2021) · Cambridge University Press eBooks · doi:10.1017/9781009064804.009
The Current State of AI Research Is Perfectly Suited to China’s Fuzzy Logic System
Parasol, M. (2021) · Cambridge University Press eBooks · doi:10.1017/9781009064804.011
Parasol, M. (2021) · Cambridge University Press eBooks · doi:10.1017/9781009064804.005
Open-Source AI Platforms and the Cyber Security Law
Parasol, M. (2021) · Cambridge University Press eBooks · doi:10.1017/9781009064804.012
(2021) · Cambridge University Press eBooks · doi:10.1017/9781009064804.014
Innovating in China’s Entrepreneurial Ecosystem
Parasol, M. (2021) · Cambridge University Press eBooks · doi:10.1017/9781009064804.003
Synthesis of a Governance Framework for Blockchain Technology: A Meta-synthesis
Damon, A., & Roodt, S. (2023) · Communications in computer and information science · doi:10.1007/978-3-031-39652-6_7
An Empirical Study of the Apache Voting Process on Open Source Community Governance
Ji-sheng, W., Bao, L., & Ni, C. (2023) · Asia-Pacific Symposium on Internetware · doi:10.1145/3609437.3609454
Wahab, A. A., Ibrahim, H., SarkinTudu, S. M., & Romo, B. A. (2024) · Communications in computer and information science · doi:10.1007/978-981-99-9589-9_22
La blockchain en support aux communs
Malafosse, M. (2022) · theses.fr (ABES) · doi:10.70675/9de2a76bz881fz44d7zb6cdz6d2b0abb23f4
Strategic Opacity: The Paradox of Open Source AI Governance in DeepSeek and OpenAI
Dodds, T., & Chengyuan, L. (2026) · The Information Society · doi:10.1080/01972243.2026.2680886
Effective voice: Beyond exit and affect in online communities
Frey, S., & Schneider, N. (2023) · New Media & Society · doi:10.1177/14614448211044025 · Cited by 18 · see citing works
- Authors
- Nyman, L., & Lindman, J.
- Affiliations
- Hanken School of Economics (FI)
- Venue
- Technology Innovation Management Review
- Publisher
- Carleton University
- Published
- 2013-01-14
- Volume
- 3
- Issue
- 1
- Pages
- 7-12
- ISSN
- 1913-6102 (ISSN-L)
- 1927-0321
- OpenAlex
- W2155569311
- Cited by
- 81
- References
- 0
- Citations by year
- 2026: 3 · 2024: 5 · 2023: 9 · 2022: 9 · 2021: 25 · 2020: 9 · 2019: 6 · 2018: 3 · 2016: 4 · 2015: 3 · 2014: 3 · 2013: 2
- FWCI
- 6.06
- Type
- journal article
- Language
- en
- Open access
- diamond
- doi.org
- Licence
- cc-by
- Locations
- Technology Innovation Management Review (publishedVersion, cc-by)
- Työväentutkimus Vuosikirja (submittedVersion)
- Topics
- Physical Sciences › Computer Science › Computer Science Applications › Open Source Software Innovations
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Social Sciences › Business, Management and Accounting › Strategy and Management › Digital Platforms and Economics
- Keywords
- open source software, software governance, sustainability, open source communities
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Claims read by deepseek-v4.1-flash under definition version 3 (extract-v3) on 2026-10-27.
Classified by jev-1.13-20260917 (gold-guideline-v0.2) on 2026-10-27.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review