Open Source: Difference between revisions
No edit summary |
No edit summary |
||
(7 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{Chapter | {{Chapter | ||
| | |image=OpenSource.jpg | ||
| | |poc=Wilfred Pinfold | ||
| authors = Wilfred Pinfold | |authors=Wilfred Pinfold | ||
| | |blueprint=Data | ||
| email = wilfred.pinfold@urban.systems | |chapter=3800 | ||
| document = 20170824-City-Platform-Supercluster-Report-FINAL.pdf | |sectors=Data | ||
|summary=Open source refers to a type of software or technology whose source code is publicly available and can be modified and distributed by anyone. This means that the underlying code that makes the software or technology work is freely accessible to the public, and can be modified, improved, or distributed by anyone without the need for permission from the original creator. | |||
|email=wilfred.pinfold@urban.systems | |||
|document=20170824-City-Platform-Supercluster-Report-FINAL.pdf | |||
}} | }} | ||
Open source software is typically developed by a community of developers who work together to improve the software and share their modifications with the rest of the community. This collaborative approach to development allows for rapid innovation and can result in high-quality software that is widely used and widely supported. | |||
Open source is in contrast to proprietary software, which is developed and distributed by a company or individual who retains exclusive control over the software's source code and distribution. | |||
Open source is a fundamental concept in the software development field but has been extended to other areas such as education, research, and technology. Open-source hardware, Open-source content and Open-source drug discovery are some examples. | |||
Open source is a philosophy that encourages collaboration and sharing, which aims to foster innovation, creativity, and community development. | |||
==Best Practices== | |||
There are several best practices that are commonly followed in open-source development: | |||
#'''Use version control''': Using a version control system such as Git allows multiple developers to work on the same codebase simultaneously and helps track changes to the code over time. | |||
#'''Write clear and readable code''': Open-source code should be easy to read and understand by other developers, which helps to ensure that others can contribute to the project and that the code can be easily maintained. | |||
#'''Write documentation''': Well-written documentation helps others understand the project and how to contribute. | |||
#'''Write tests''': Writing automated tests helps to ensure that the code works as intended and that any changes made to the code do not break existing functionality. | |||
#'''Use a well accepted license''': Open-source projects should have an open-source license which clearly states the terms under which the code can be used, modified, and distributed. | |||
#'''Encourage community involvement''': Encouraging contributions from the community and fostering a welcoming environment helps to build a strong and active community around the project. | |||
#'''Continuously improve''': Continuously improve the codebase, fix bugs, and add new features to keep the project active and relevant. | |||
#'''Be inclusive''': Be inclusive and respectful of all contributors regardless of their background or experience. | |||
By following these best practices, open-source development teams can create high-quality, well-maintained, and widely adopted code that benefits the entire community. | |||
Continuously improve van be achieved from the outset by using Agile development methodologies. Agile software development emphasizes flexibility, collaboration, and customer satisfaction. It is often used in open-source software development to manage the collaborative process of developing and maintaining software. | |||
In Agile development, a software project is broken down into small, manageable chunks called iterations or sprints, usually lasting a few weeks. Each iteration or sprint is focused on delivering a working piece of software that contains a set of specific features or improvements. The team works closely with the stakeholders, such as users and customers, to prioritize and plan the work for each iteration. | |||
In an open-source software context, Agile development allows for a flexible and collaborative process where developers from different backgrounds, locations, and skill levels can work together to deliver a high-quality product. The stakeholders, such as the users and contributors, can provide feedback and suggestions at any point in the development process. | |||
Some of the key principles of Agile development in open-source software include: | |||
Working software is the primary measure of progress | |||
*Welcome changing requirements | |||
*Deliver working software frequently | |||
*Collaboration between developers and stakeholders | |||
*Continuous improvement | |||
The Agile development approach in open-source software can provide a transparent and flexible development process that allows for rapid innovation and customer satisfaction. | |||
==Barriers to Use== | |||
Two barriers currently exist to effective and powerful smart city solutions. First, many current smart city ICT deployments are based on custom systems that are not interoperable, portable across cities, extensible, or cost-effective. Second, a number of architectural design efforts are currently underway (e.g. ISO/IEC JTC1, IEC, IEEE, ITU and consortia) but have not yet converged, creating uncertainty among stakeholders. To reduce these barriers, NIST and its partners convened an international public working group to compare and distill from these architectural efforts and city stakeholders a consensus framework of common architectural features to enable smart city solutions that meet the needs of modern communities. | |||
<!-- Citations --> | |||
{{#scite: | |||
|reference=linåker2023op | |||
|type=journal-article | |||
|title=Open Source Software in the Public Sector: 25 Years and Still in Its Infancy | |||
|author=Johan Linåker;Gregorio Robles;Deborah Bryant;Sachiko Muto|+sep=; | |||
|journal=IEEE Software | |||
|publisher=Institute of Electrical and Electronics Engineers (IEEE) | |||
|year=2023 | |||
|volume=40 | |||
|issue=4 | |||
|pages=39-44 | |||
|doi=10.1109/ms.2023.3266105 | |||
|subject=Software | |||
|issn=0740-7459;1937-4194|+sep=; | |||
|retrieved-from=https://dx.doi.org/ | |||
|retrieved-on=2023-07-29 | |||
}} | |||
{{#scite: | |||
|reference=robles2019tw | |||
|type=journal-article | |||
|title=Twenty Years of Open Source Software: From Skepticism to Mainstream | |||
|author=Gregorio Robles;Igor Steinmacher;Paul Adams;Christoph Treude|+sep=; | |||
|journal=IEEE Software | |||
|publisher=Institute of Electrical and Electronics Engineers (IEEE) | |||
|year=2019 | |||
|volume=36 | |||
|issue=6 | |||
|pages=12-15 | |||
|doi=10.1109/ms.2019.2933672 | |||
|subject=Software | |||
|issn=0740-7459;1937-4194|+sep=; | |||
|retrieved-from=https://dx.doi.org/ | |||
|retrieved-on=2023-07-29 | |||
}} | |||
{{#scite: | |||
|reference=Blind2023 | |||
|type=report | |||
|author=K. Blind et al. | |||
|title=The impact of open source software and hardware on technological independence, competitiveness and innovation in the EU economy | |||
|publisher=European Commission, | |||
|location=Brussels Belgium | |||
|year=2021 | |||
|retrieved-on=2023-07-29 | |||
|file=https://opencommons.org/images/c/c1/The_impact_of_open_source_software_and_hardware_on-KK0421081ENN.pdf | |||
}} | |||
{{#scite: | |||
|reference=Nagle2019 | |||
|type=report | |||
|author=Frank Nagle | |||
|title=Government technology policy, social value, and national competitiveness | |||
|publisher=Harvard Business School Strategy Unit | |||
|location=Boston MA | |||
|issue=19–103 | |||
|year=2019 | |||
|retrieved-on=2023-07-29 | |||
|file=https://opencommons.org/images/8/87/19-103_70f212c8-c4fe-4989-ac99-e03cf8bbf02d.pdf | |||
}} | |||
{{#scite: | |||
|reference=linaker2020wh | |||
|type=journal-article | |||
|title=What to share, when, and where: balancing the objectives and complexities of open source software contributions | |||
|author=Johan Linåker;Björn Regnell|+sep=; | |||
|journal=Empirical Software Engineering | |||
|publisher=Springer Science and Business Media LLC | |||
|year=2020 | |||
|volume=25 | |||
|issue=5 | |||
|pages=3799-3840 | |||
|doi=10.1007/s10664-020-09855-2 | |||
|subject=Software | |||
|issn=1382-3256;1573-7616|+sep=; | |||
|retrieved-from=https://dx.doi.org/ | |||
|retrieved-on=2023-07-29 | |||
}} | |||
{{#scite: | |||
|reference=publiques2022 | |||
|type=report | |||
|title=Strasbourg declaration on the common values and challenges of European public administrations | |||
|publisher=Ministère de la Transformation et de la Fonction Publiques | |||
|location=Strasbourg France | |||
|year=2022 | |||
|retrieved-on=2023-07-29 | |||
|file=https://opencommons.org/images/9/9a/Declaration_common_values_challenges_european_public_administrations_1.pdf | |||
}} | |||
{{#scite: | |||
|reference=thinkopen2020 | |||
|type=report | |||
|title=Open source software strategy 2021-2023, think open | |||
|publisher=European Commission | |||
|location=Brussels Belgium | |||
|number=7149 | |||
|year=2020 | |||
|retrieved-on=2023-07-29 | |||
|file=https://opencommons.org/images/9/9d/En_ec_open_source_strategy_2020-2023.pdf | |||
}} | |||
{{#scite: | |||
|reference=thinkopen2020 | |||
|type=report | |||
|title=Open-source technologies for sustainable development | |||
|publisher=United Nations Economic and Social Council | |||
|location=New York NY | |||
|resolution E/RES/2021/30 | |||
|year=2021 | |||
|retrieved-on=2023-07-29 | |||
|file=https://opencommons.org/images/8/83/Ecosoc_res_2021d30_en.pdf | |||
}} | |||
{{#scite: | |||
|reference=lundell2021en | |||
|type=book-chapter | |||
|title=Enabling OSS Usage Through Procurement Projects: How Can Lock-in Effects Be Avoided? | |||
|author=Björn Lundell;Jonas Gamalielsson;Simon Butler;Christoffer Brax;Tomas Persson;Anders Mattsson;Tomas Gustavsson;Jonas Feist;Jonas Öberg|+sep=; | |||
|journal=IFIP Advances in Information and Communication Technology | |||
|publisher=Springer International Publishing | |||
|year=2021 | |||
|pages=16-27 | |||
|doi=10.1007/978-3-030-75251-4_2 | |||
|issn=1868-4238;1868-422X|+sep=; | |||
|retrieved-from=https://dx.doi.org/ | |||
|retrieved-on=2023-07-29 | |||
|url=https://link.springer.com/chapter/10.1007/978-3-030-75251-4_2 | |||
}} | |||
{{#scite: | |||
|reference=scanlon2019cr | |||
|type=journal-article | |||
|title=Critical Factors for Open Source Advancement in the U.S. Department of Defense | |||
|author=Thomas P. Scanlon | |||
|journal=IEEE Software | |||
|publisher=Institute of Electrical and Electronics Engineers (IEEE) | |||
|year=2019 | |||
|volume=36 | |||
|issue=6 | |||
|pages=29-33 | |||
|doi=10.1109/ms.2019.2933769 | |||
|subject=Software | |||
|issn=0740-7459;1937-4194|+sep=; | |||
|retrieved-from=https://dx.doi.org/ | |||
|retrieved-on=2023-07-29 | |||
|url=https://ieeexplore.ieee.org/document/8790750 | |||
}} | |||
{{#scite: | |||
|reference=robles2019se | |||
|type=book-chapter | |||
|title=Setting Up Government 3.0 Solutions Based on Open Source Software: The Case of X-Road | |||
|author=Gregorio Robles;Jonas Gamalielsson;Björn Lundell|+sep=; | |||
|journal=Lecture Notes in Computer Science | |||
|publisher=Springer International Publishing | |||
|year=2019 | |||
|pages=69-81 | |||
|doi=10.1007/978-3-030-27325-5_6 | |||
|issn=0302-9743;1611-3349|+sep=; | |||
|retrieved-from=https://dx.doi.org/ | |||
|retrieved-on=2023-07-29 | |||
|url=https://link.springer.com/chapter/10.1007/978-3-030-27325-5_6 | |||
}} | |||
{{#scite: | |||
|reference=kuechler2013mi | |||
|type=book-chapter | |||
|title=Misconceptions and Barriers to Adoption of FOSS in the U.S. Energy Industry | |||
|author=Victor Kuechler;Carlos Jensen;Deborah Bryant|+sep=; | |||
|journal=Open Source Software: Quality Verification | |||
|publisher=Springer Berlin Heidelberg | |||
|year=2013 | |||
|pages=232-244 | |||
|doi=10.1007/978-3-642-38928-3_17 | |||
|issn=1868-4238;1868-422X|+sep=; | |||
|retrieved-from=https://dx.doi.org/ | |||
|retrieved-on=2023-07-29 | |||
|url=https://link.springer.com/chapter/10.1007/978-3-642-38928-3_17 | |||
}} | |||
{{#scite: | |||
|reference=yenişen yavuz2022pr | |||
|type=journal-article | |||
|title=Problems, Solutions, and Success Factors in the openMDM User-Led Open Source Consortium | |||
|author=Elçin Yenişen Yavuz;;Ann Barcomb;Dirk Riehle;;|+sep=; | |||
|journal=Communications of the Association for Information Systems | |||
|publisher=Association for Information Systems | |||
|year=2022 | |||
|volume=51 | |||
|issue=1 | |||
|pages=509-542 | |||
|doi=10.17705/1cais.05122 | |||
|subject=Information Systems | |||
|issn=1529-3181 | |||
|retrieved-from=https://dx.doi.org/ | |||
|retrieved-on=2023-07-29 | |||
|url=https://aisel.aisnet.org/cais/vol51/iss1/13/ | |||
}} | |||
{{#scite: | |||
|reference=viseur2023co | |||
|type=journal-article | |||
|title=CommunesPlone: An Original Open Source Model of Resource Pooling in the Public Sector | |||
|author=Robert Viseur;Nicolas Jullien|+sep=; | |||
|journal=IEEE Software | |||
|publisher=Institute of Electrical and Electronics Engineers (IEEE) | |||
|year=2023 | |||
|volume=40 | |||
|issue=4 | |||
|pages=46-54 | |||
|doi=10.1109/ms.2023.3268352 | |||
|subject=Software | |||
|issn=0740-7459;1937-4194|+sep=; | |||
|retrieved-from=https://dx.doi.org/ | |||
|retrieved-on=2023-07-29 | |||
|url=https://ieeexplore.ieee.org/abstract/document/10176193 | |||
}} | |||
{{#scite: | |||
|reference=frey2023ho | |||
|type=journal-article | |||
|title=How We Lead Successful Open-Source Collaborations in the Danish Public Sector | |||
|author=Rasmus Frey | |||
|journal=IEEE Software | |||
|publisher=Institute of Electrical and Electronics Engineers (IEEE) | |||
|year=2023 | |||
|volume=40 | |||
|issue=4 | |||
|pages=19-24 | |||
|doi=10.1109/ms.2023.3268903 | |||
|subject=Software | |||
|issn=0740-7459;1937-4194|+sep=; | |||
|retrieved-from=https://dx.doi.org/ | |||
|retrieved-on=2023-07-29 | |||
}} | |||
{{#scite: | |||
|reference=favario2023to | |||
|type=journal-article | |||
|title=Toward a Free and Open Source-Driven Public Sector: An Italian Journey | |||
|author=Leonardo Favario | |||
|journal=IEEE Software | |||
|publisher=Institute of Electrical and Electronics Engineers (IEEE) | |||
|year=2023 | |||
|volume=40 | |||
|issue=4 | |||
|pages=55-61 | |||
|doi=10.1109/ms.2023.3266706 | |||
|subject=Software | |||
|issn=0740-7459;1937-4194|+sep=; | |||
|retrieved-from=https://dx.doi.org/ | |||
|retrieved-on=2023-07-29 | |||
|url=https://www.computer.org/csdl/magazine/so/2023/04/10176161/1OAJxGLzPsk | |||
}} | |||
{{#scite: | |||
|reference=rudmark2023be | |||
|type=journal-article | |||
|title=Beyond Procurement: How Entur Navigated the Open Source Journey to Advance Public Transport | |||
|author=Daniel Rudmark;Juho Lindman;Andreas Tryti;Brede Dammen|+sep=; | |||
|journal=IEEE Software | |||
|publisher=Institute of Electrical and Electronics Engineers (IEEE) | |||
|year=2023 | |||
|volume=40 | |||
|issue=4 | |||
|pages=62-70 | |||
|doi=10.1109/ms.2023.3266482 | |||
|subject=Software | |||
|issn=0740-7459;1937-4194|+sep=; | |||
|retrieved-from=https://dx.doi.org/ | |||
|retrieved-on=2023-07-29 | |||
|url=https://ieeexplore.ieee.org/abstract/document/10176195 | |||
}} | |||
{{#scite: | |||
|reference=holbrook2023cl | |||
|type=journal-article | |||
|title=Clarity About Transparency: Software Transparency and Open Source Software Licenses in the U.S. Public Sector | |||
|author=Luke D. Holbrook | |||
|journal=IEEE Software | |||
|publisher=Institute of Electrical and Electronics Engineers (IEEE) | |||
|year=2023 | |||
|volume=40 | |||
|issue=4 | |||
|pages=71-76 | |||
|doi=10.1109/ms.2023.3265889 | |||
|subject=Software | |||
|issn=0740-7459;1937-4194|+sep=; | |||
|retrieved-from=https://dx.doi.org/ | |||
|retrieved-on=2023-07-29 | |||
|url=https://ieeexplore.ieee.org/document/10176179 | |||
}} | |||
{{#scite:David Egts 2018 | |||
| date = 2018-12-20 | |||
| author = Tod Newcombe | |||
| publisher = GovTech Today | |||
| type= web | |||
| title = Four Myths About Open Source in Government | |||
| accessdate = 2019-10-27 | |||
| url = https://www.govtech.com/opinion/Four-Myths-About-Open-Source-in-Government-Contributed.html | |||
}} | |||
{{#scite: | |||
|reference=preis2014op | |||
|type=journal-article | |||
|title=openPDS: Protecting the Privacy of Metadata through SafeAnswers | |||
|author=Yves-Alexandre de Montjoye;Erez Shmueli;Samuel S. Wang;Alex Sandy Pentland|+sep=; | |||
|editor=Tobias Preis | |||
|journal=PLoS ONE | |||
|publisher=Public Library of Science (PLoS) | |||
|year=2014 | |||
|volume=9 | |||
|issue=7 | |||
|pages=e98790 | |||
|doi=10.1371/journal.pone.0098790 | |||
|subject=Multidisciplinary | |||
|issn=1932-6203 | |||
|retrieved-from=https://dx.doi.org/ | |||
|retrieved-on=2023-07-29 | |||
|file = https://opencommons.org/images/0/0e/OpenPDS.pdf | |||
|github = https://github.com/HumanDynamics/openPDS | |||
}} | |||
{{#scite:OL28341888M | |||
|title=Working in Public | |||
|type=book | |||
|subtitle=The Making and Maintenance of Open Source Software | |||
|author=Nadia Eghbal | |||
|publisher=Stripe Press | |||
|pubdate=Aug 04, 2020 | |||
|pages=256 | |||
|subject=Computer software | |||
|isbn=0578675862;9780578675862|+sep=; | |||
|url=https://openlibrary.org/books/OL28341888M/Working_in_Public | |||
|olid=OL28341888M | |||
|cover=https://covers.openlibrary.org/b/id/10290182-L.jpg | |||
|retrieved-from=https://openlibrary.org/ | |||
|retrieved-on=2023-07-30 | |||
}} |
Latest revision as of 00:05, July 30, 2023
Data | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Sectors | Data | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Contact | Wilfred Pinfold | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Topics | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Activities
Press
|
- Authors
Open source refers to a type of software or technology whose source code is publicly available and can be modified and distributed by anyone. This means that the underlying code that makes the software or technology work is freely accessible to the public, and can be modified, improved, or distributed by anyone without the need for permission from the original creator.
Open source software is typically developed by a community of developers who work together to improve the software and share their modifications with the rest of the community. This collaborative approach to development allows for rapid innovation and can result in high-quality software that is widely used and widely supported.
Open source is in contrast to proprietary software, which is developed and distributed by a company or individual who retains exclusive control over the software's source code and distribution.
Open source is a fundamental concept in the software development field but has been extended to other areas such as education, research, and technology. Open-source hardware, Open-source content and Open-source drug discovery are some examples.
Open source is a philosophy that encourages collaboration and sharing, which aims to foster innovation, creativity, and community development.
Best Practices
There are several best practices that are commonly followed in open-source development:
- Use version control: Using a version control system such as Git allows multiple developers to work on the same codebase simultaneously and helps track changes to the code over time.
- Write clear and readable code: Open-source code should be easy to read and understand by other developers, which helps to ensure that others can contribute to the project and that the code can be easily maintained.
- Write documentation: Well-written documentation helps others understand the project and how to contribute.
- Write tests: Writing automated tests helps to ensure that the code works as intended and that any changes made to the code do not break existing functionality.
- Use a well accepted license: Open-source projects should have an open-source license which clearly states the terms under which the code can be used, modified, and distributed.
- Encourage community involvement: Encouraging contributions from the community and fostering a welcoming environment helps to build a strong and active community around the project.
- Continuously improve: Continuously improve the codebase, fix bugs, and add new features to keep the project active and relevant.
- Be inclusive: Be inclusive and respectful of all contributors regardless of their background or experience.
By following these best practices, open-source development teams can create high-quality, well-maintained, and widely adopted code that benefits the entire community.
Continuously improve van be achieved from the outset by using Agile development methodologies. Agile software development emphasizes flexibility, collaboration, and customer satisfaction. It is often used in open-source software development to manage the collaborative process of developing and maintaining software.
In Agile development, a software project is broken down into small, manageable chunks called iterations or sprints, usually lasting a few weeks. Each iteration or sprint is focused on delivering a working piece of software that contains a set of specific features or improvements. The team works closely with the stakeholders, such as users and customers, to prioritize and plan the work for each iteration.
In an open-source software context, Agile development allows for a flexible and collaborative process where developers from different backgrounds, locations, and skill levels can work together to deliver a high-quality product. The stakeholders, such as the users and contributors, can provide feedback and suggestions at any point in the development process.
Some of the key principles of Agile development in open-source software include:
Working software is the primary measure of progress
- Welcome changing requirements
- Deliver working software frequently
- Collaboration between developers and stakeholders
- Continuous improvement
The Agile development approach in open-source software can provide a transparent and flexible development process that allows for rapid innovation and customer satisfaction.
Barriers to Use
Two barriers currently exist to effective and powerful smart city solutions. First, many current smart city ICT deployments are based on custom systems that are not interoperable, portable across cities, extensible, or cost-effective. Second, a number of architectural design efforts are currently underway (e.g. ISO/IEC JTC1, IEC, IEEE, ITU and consortia) but have not yet converged, creating uncertainty among stakeholders. To reduce these barriers, NIST and its partners convened an international public working group to compare and distill from these architectural efforts and city stakeholders a consensus framework of common architectural features to enable smart city solutions that meet the needs of modern communities.
{{#scite:
|reference=linåker2023op |type=journal-article |title=Open Source Software in the Public Sector: 25 Years and Still in Its Infancy |author=Johan Linåker;Gregorio Robles;Deborah Bryant;Sachiko Muto|+sep=; |journal=IEEE Software |publisher=Institute of Electrical and Electronics Engineers (IEEE) |year=2023 |volume=40 |issue=4 |pages=39-44 |doi=10.1109/ms.2023.3266105 |subject=Software |issn=0740-7459;1937-4194|+sep=; |retrieved-from=https://dx.doi.org/ |retrieved-on=2023-07-29
}}
{{#scite:
|reference=robles2019tw |type=journal-article |title=Twenty Years of Open Source Software: From Skepticism to Mainstream |author=Gregorio Robles;Igor Steinmacher;Paul Adams;Christoph Treude|+sep=; |journal=IEEE Software |publisher=Institute of Electrical and Electronics Engineers (IEEE) |year=2019 |volume=36 |issue=6 |pages=12-15 |doi=10.1109/ms.2019.2933672 |subject=Software |issn=0740-7459;1937-4194|+sep=; |retrieved-from=https://dx.doi.org/ |retrieved-on=2023-07-29
}}
{{#scite:
|reference=Blind2023 |type=report |author=K. Blind et al. |title=The impact of open source software and hardware on technological independence, competitiveness and innovation in the EU economy |publisher=European Commission, |location=Brussels Belgium |year=2021 |retrieved-on=2023-07-29 |file=https://opencommons.org/images/c/c1/The_impact_of_open_source_software_and_hardware_on-KK0421081ENN.pdf
}}
{{#scite:
|reference=Nagle2019 |type=report |author=Frank Nagle |title=Government technology policy, social value, and national competitiveness |publisher=Harvard Business School Strategy Unit |location=Boston MA |issue=19–103 |year=2019 |retrieved-on=2023-07-29 |file=https://opencommons.org/images/8/87/19-103_70f212c8-c4fe-4989-ac99-e03cf8bbf02d.pdf
}}
{{#scite:
|reference=linaker2020wh |type=journal-article |title=What to share, when, and where: balancing the objectives and complexities of open source software contributions |author=Johan Linåker;Björn Regnell|+sep=; |journal=Empirical Software Engineering |publisher=Springer Science and Business Media LLC |year=2020 |volume=25 |issue=5 |pages=3799-3840 |doi=10.1007/s10664-020-09855-2 |subject=Software |issn=1382-3256;1573-7616|+sep=; |retrieved-from=https://dx.doi.org/ |retrieved-on=2023-07-29
}}
{{#scite:
|reference=publiques2022 |type=report |title=Strasbourg declaration on the common values and challenges of European public administrations |publisher=Ministère de la Transformation et de la Fonction Publiques |location=Strasbourg France |year=2022 |retrieved-on=2023-07-29 |file=https://opencommons.org/images/9/9a/Declaration_common_values_challenges_european_public_administrations_1.pdf
}}
{{#scite:
|reference=thinkopen2020 |type=report |title=Open source software strategy 2021-2023, think open |publisher=European Commission |location=Brussels Belgium |number=7149 |year=2020 |retrieved-on=2023-07-29 |file=https://opencommons.org/images/9/9d/En_ec_open_source_strategy_2020-2023.pdf
}}
{{#scite:
|reference=thinkopen2020 |type=report |title=Open-source technologies for sustainable development |publisher=United Nations Economic and Social Council |location=New York NY |resolution E/RES/2021/30 |year=2021 |retrieved-on=2023-07-29 |file=https://opencommons.org/images/8/83/Ecosoc_res_2021d30_en.pdf
}}
{{#scite:
|reference=lundell2021en |type=book-chapter |title=Enabling OSS Usage Through Procurement Projects: How Can Lock-in Effects Be Avoided? |author=Björn Lundell;Jonas Gamalielsson;Simon Butler;Christoffer Brax;Tomas Persson;Anders Mattsson;Tomas Gustavsson;Jonas Feist;Jonas Öberg|+sep=; |journal=IFIP Advances in Information and Communication Technology |publisher=Springer International Publishing |year=2021 |pages=16-27 |doi=10.1007/978-3-030-75251-4_2 |issn=1868-4238;1868-422X|+sep=; |retrieved-from=https://dx.doi.org/ |retrieved-on=2023-07-29 |url=https://link.springer.com/chapter/10.1007/978-3-030-75251-4_2
}}
{{#scite:
|reference=scanlon2019cr |type=journal-article |title=Critical Factors for Open Source Advancement in the U.S. Department of Defense |author=Thomas P. Scanlon |journal=IEEE Software |publisher=Institute of Electrical and Electronics Engineers (IEEE) |year=2019 |volume=36 |issue=6 |pages=29-33 |doi=10.1109/ms.2019.2933769 |subject=Software |issn=0740-7459;1937-4194|+sep=; |retrieved-from=https://dx.doi.org/ |retrieved-on=2023-07-29 |url=https://ieeexplore.ieee.org/document/8790750
}}
{{#scite:
|reference=robles2019se |type=book-chapter |title=Setting Up Government 3.0 Solutions Based on Open Source Software: The Case of X-Road |author=Gregorio Robles;Jonas Gamalielsson;Björn Lundell|+sep=; |journal=Lecture Notes in Computer Science |publisher=Springer International Publishing |year=2019 |pages=69-81 |doi=10.1007/978-3-030-27325-5_6 |issn=0302-9743;1611-3349|+sep=; |retrieved-from=https://dx.doi.org/ |retrieved-on=2023-07-29 |url=https://link.springer.com/chapter/10.1007/978-3-030-27325-5_6
}}
{{#scite:
|reference=kuechler2013mi |type=book-chapter |title=Misconceptions and Barriers to Adoption of FOSS in the U.S. Energy Industry |author=Victor Kuechler;Carlos Jensen;Deborah Bryant|+sep=; |journal=Open Source Software: Quality Verification |publisher=Springer Berlin Heidelberg |year=2013 |pages=232-244 |doi=10.1007/978-3-642-38928-3_17 |issn=1868-4238;1868-422X|+sep=; |retrieved-from=https://dx.doi.org/ |retrieved-on=2023-07-29 |url=https://link.springer.com/chapter/10.1007/978-3-642-38928-3_17
}}
{{#scite:
|reference=yenişen yavuz2022pr |type=journal-article |title=Problems, Solutions, and Success Factors in the openMDM User-Led Open Source Consortium |author=Elçin Yenişen Yavuz;;Ann Barcomb;Dirk Riehle;;|+sep=; |journal=Communications of the Association for Information Systems |publisher=Association for Information Systems |year=2022 |volume=51 |issue=1 |pages=509-542 |doi=10.17705/1cais.05122 |subject=Information Systems |issn=1529-3181 |retrieved-from=https://dx.doi.org/ |retrieved-on=2023-07-29 |url=https://aisel.aisnet.org/cais/vol51/iss1/13/
}}
{{#scite:
|reference=viseur2023co |type=journal-article |title=CommunesPlone: An Original Open Source Model of Resource Pooling in the Public Sector |author=Robert Viseur;Nicolas Jullien|+sep=; |journal=IEEE Software |publisher=Institute of Electrical and Electronics Engineers (IEEE) |year=2023 |volume=40 |issue=4 |pages=46-54 |doi=10.1109/ms.2023.3268352 |subject=Software |issn=0740-7459;1937-4194|+sep=; |retrieved-from=https://dx.doi.org/ |retrieved-on=2023-07-29 |url=https://ieeexplore.ieee.org/abstract/document/10176193
}}
{{#scite:
|reference=frey2023ho |type=journal-article |title=How We Lead Successful Open-Source Collaborations in the Danish Public Sector |author=Rasmus Frey |journal=IEEE Software |publisher=Institute of Electrical and Electronics Engineers (IEEE) |year=2023 |volume=40 |issue=4 |pages=19-24 |doi=10.1109/ms.2023.3268903 |subject=Software |issn=0740-7459;1937-4194|+sep=; |retrieved-from=https://dx.doi.org/ |retrieved-on=2023-07-29
}}
{{#scite:
|reference=favario2023to |type=journal-article |title=Toward a Free and Open Source-Driven Public Sector: An Italian Journey |author=Leonardo Favario |journal=IEEE Software |publisher=Institute of Electrical and Electronics Engineers (IEEE) |year=2023 |volume=40 |issue=4 |pages=55-61 |doi=10.1109/ms.2023.3266706 |subject=Software |issn=0740-7459;1937-4194|+sep=; |retrieved-from=https://dx.doi.org/ |retrieved-on=2023-07-29 |url=https://www.computer.org/csdl/magazine/so/2023/04/10176161/1OAJxGLzPsk
}}
{{#scite:
|reference=rudmark2023be |type=journal-article |title=Beyond Procurement: How Entur Navigated the Open Source Journey to Advance Public Transport |author=Daniel Rudmark;Juho Lindman;Andreas Tryti;Brede Dammen|+sep=; |journal=IEEE Software |publisher=Institute of Electrical and Electronics Engineers (IEEE) |year=2023 |volume=40 |issue=4 |pages=62-70 |doi=10.1109/ms.2023.3266482 |subject=Software |issn=0740-7459;1937-4194|+sep=; |retrieved-from=https://dx.doi.org/ |retrieved-on=2023-07-29 |url=https://ieeexplore.ieee.org/abstract/document/10176195
}}
{{#scite:
|reference=holbrook2023cl |type=journal-article |title=Clarity About Transparency: Software Transparency and Open Source Software Licenses in the U.S. Public Sector |author=Luke D. Holbrook |journal=IEEE Software |publisher=Institute of Electrical and Electronics Engineers (IEEE) |year=2023 |volume=40 |issue=4 |pages=71-76 |doi=10.1109/ms.2023.3265889 |subject=Software |issn=0740-7459;1937-4194|+sep=; |retrieved-from=https://dx.doi.org/ |retrieved-on=2023-07-29 |url=https://ieeexplore.ieee.org/document/10176179
}}
{{#scite:David Egts 2018
| date = 2018-12-20 | author = Tod Newcombe | publisher = GovTech Today | type= web | title = Four Myths About Open Source in Government | accessdate = 2019-10-27 | url = https://www.govtech.com/opinion/Four-Myths-About-Open-Source-in-Government-Contributed.html
}}
{{#scite:
|reference=preis2014op |type=journal-article |title=openPDS: Protecting the Privacy of Metadata through SafeAnswers |author=Yves-Alexandre de Montjoye;Erez Shmueli;Samuel S. Wang;Alex Sandy Pentland|+sep=; |editor=Tobias Preis |journal=PLoS ONE |publisher=Public Library of Science (PLoS) |year=2014 |volume=9 |issue=7 |pages=e98790 |doi=10.1371/journal.pone.0098790 |subject=Multidisciplinary |issn=1932-6203 |retrieved-from=https://dx.doi.org/ |retrieved-on=2023-07-29 |file = https://opencommons.org/images/0/0e/OpenPDS.pdf |github = https://github.com/HumanDynamics/openPDS
}}
{{#scite:OL28341888M
|title=Working in Public |type=book |subtitle=The Making and Maintenance of Open Source Software |author=Nadia Eghbal |publisher=Stripe Press |pubdate=Aug 04, 2020 |pages=256 |subject=Computer software |isbn=0578675862;9780578675862|+sep=; |url=https://openlibrary.org/books/OL28341888M/Working_in_Public |olid=OL28341888M |cover=https://covers.openlibrary.org/b/id/10290182-L.jpg |retrieved-from=https://openlibrary.org/ |retrieved-on=2023-07-30
}}