Inter-American Development Bank
facebook
twitter
youtube
linkedin
instagram
Abierto al públicoBeyond BordersCaribbean Development TrendsCiudades SosteniblesEnergía para el FuturoEnfoque EducaciónFactor TrabajoGente SaludableGestión fiscalGobernarteIdeas MatterIdeas que CuentanIdeaçãoImpactoIndustrias CreativasLa Maleta AbiertaMoviliblogMás Allá de las FronterasNegocios SosteniblesPrimeros PasosPuntos sobre la iSeguridad CiudadanaSostenibilidadVolvamos a la fuente¿Y si hablamos de igualdad?Home
Citizen Security and Justice Creative Industries Development Effectiveness Early Childhood Development Education Energy Envirnment. Climate Change and Safeguards Fiscal policy and management Gender and Diversity Health Labor and pensions Open Knowledge Public management Science, Technology and Innovation  Trade and Regional Integration Urban Development and Housing Water and Sanitation
  • Skip to main content
  • Skip to secondary menu
  • Skip to primary sidebar
  • Skip to footer

Abierto al público

  • HOME
    • About this blog 
    • Editorial guidelines
  • CATEGORIES
    • Knowledge Management
    • Open Data
    • Open Learning
    • Open Source
    • Open Systems
  • Authors
  • English
    • Español

Free software? Open source? We answer your questions

June 5, 2018 by Jesenia Rodríguez Leave a Comment


What is open-source software? Is it different than Free Software? And can we trust something “open” to support public services? In our experience promoting the IDB’s Code for Development initiative, we have heard these and similar questions. The dynamic and collaborative nature of the technological ecosystem sometimes contributes to confusion.

That is why we seek to clarify some of the most frequently asked questions about open-source software, and highlight the numerous opportunities for impact this movement brings to the public.

First, what is the difference between free and open source software? Are they the same?

They’re not the same. There is much debate on this topic, so much so that it can turn into a philosophical conversation. While open-source software stemmed from free software, both agree on the openness of software source code and collaborative work to solve problems and improve or adapt the code. The subtle differences between free software and open-source software can be best understood by criteria defined by the organizations in charge.

“Free software” is defined by the Free Software Foundation (FSF) through its four essential freedoms. Some characterize these freedoms as an ethical manifesto to preserve the user’s rights over any other interest. This Foundation has a list of licenses considered free software.

On the other hand, the concept of “open-source” is defined by 10 criteria from the Open Source Initiative (OSI). These incorporate certain adjustments to the free software standards, allowing adaptation for commercial purposes, thus facilitating its reutilization. OSI also provides a list of licenses considered suitable for open-source criteria.

How does software become open-source?

Making the code open means having the source code of the digital tool publicly available. The most common practice is to publish the code on a collaborative platform specialized in software management, known as code repositories. Some of the most well-known ones include GitHub, GitLab, BitBucket, and Sourceforge. At the IDB, we use GitHub to share the open-source code developed in our projects.

The use of these platforms benefits from good practices that promote accessible and reusable code, accompanied by supporting documentation and an appropriate license. We have created a guide of best practices for publishing open-source software that you can access.

Is it dangerous to have the code exposed?

The security of your software is very important. However, in most cases, it shouldn’t be a limiting factor for opening the code. It’s also important to realize that having the code closed doesn’t provide a robust and complete security measure to protect sensitive information.

The United Kingdom, for example, has defined some very clear guidelines in its Digital Services Manual to help decide when to keep code open or closed. According to this guide, the only cases in which the code should remain closed are the following:

  • Keys and credentials within the code
  • Algorithms used to detect fraud
  • Unpublished policy or policy in the process of official publication

The guide offers some additional security considerations when working with open code.

Are governments promoting open-source code?

Yes. The creation and use of open-source software is a trend among governments because of the real impact it is generating. The Data team at the Ministry of Modernization of Argentina has shared some concrete examples of why it is important for them to work with open-source code. Additionally, a very large community can be seen on GitHub and other collaborative platforms where public entities at many levels around the world have shared their code.

In Latin America, there is broad participation in the Gealc Network, which promotes the development of public software, open-source software created for and by governments. These are examples of governments indexing the open-source code of their digital solutions:

  • Brazil
  • Colombia
  • Ecuador
  • United States
  • Peru
  • Uruguay
  • European Union

Is maintaining open-source code expensive?

First, it’s important to understand that maintaining open-source code is not the same as providing support and maintenance.

To maintain open-source code, GitHub repositories and most collaborative code platforms are free, as long as the repository you maintain is public. If you want private repositories, you will have to pay for them.

Once the code is public on a collaborative platform, you should start thinking about its lifecycle, that is, providing support and maintenance. The evolution of software will depend on many factors, such as the external collaboration it might receive once public and version management as functionalities are added. It is advisable to have someone lead the support management, preferably the person who developed the solution.

A useful way to get others to contribute to the maintenance of your software is by improving its documentation. You can review our software publishing guide in the documentation section.

Should I ask my technology provider to open the code?

Yes. You should ask your provider for the source code, except in cases where proprietary licensed tools have been used in development that prevent distribution.

It is possible to develop high-quality, commercially valuable software using open-source code. This happens when the business model is based on providing services as opposed to just providing a product, leveraging the flexibility offered by open-source technologies.

In conclusion

Code for development’s  vision is that the reuse of open-source software presents great opportunities for digital transformation in the region. It’s important to remember that when you create new open-source software, other developers (including those outside your organization) can:

  • benefit from your work and build upon it
  • learn from your experience, and
  • find uses for your code that you haven’t found yet.

Do you have more questions about open source? Write them in the comments!

By Jesenia Rodríguez Paredes, Knowledge Management and Open-Source Technology Consultant at the IDB 


Filed Under: Open Source Tagged With: Code for Development, Key Concepts

Jesenia Rodríguez

Jesenia Rodríguez é graduada em Administração de Empresas. Após terminar a faculdade, colaborou em atividades de voluntariado relacionadas à gestão de projetos com enfoque educacional. Em 2016, entrou no bootcamp de código para mulheres, Laboratoria, e mais tarde trabalhou como desenvolvedor front-end na IBM. Atualmente trabalha como consultora para a Divisão de Gestão do Conhecimento do Banco Interamericano de Desenvolvimento (BID), apoiando diretamente a iniciativa do Código de Desenvolvimento.

Reader Interactions

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Primary Sidebar

Follow Us

Subscribe

About this blog

Open knowledge can be described as information that is usable, reusable, and shareable without restrictions due to its legal and technological attributes, enabling access for anyone, anywhere, and at any time worldwide.

In the blog 'Abierto al Público,' we explore a wide range of topics, resources, and initiatives related to open knowledge on a global scale, with a specific focus on its impact on economic and social development in the Latin American and Caribbean region. Additionally, we highlight the Inter-American Development Bank's efforts to consistently disseminate actionable open knowledge generated by the organization.

Search

Topics

Access to Information Actionable Resources Artificial Intelligence BIDAcademy Big Data Citizen Participation Climate Change Code for Development Coronavirus Creative Commons Crowdsourcing Data Analysis Data Journalism Data Privacy Data Visualization Development projects Digital Badges Digital Economy Digital Inclusion Entrepreneurship Events Gender and Diversity Geospatial Data Hackathons How to Instructional Design Key Concepts Knowledge Products Lessons Learned Methodologies MOOC Most Read Natural Language Processing Numbers for Development Open Access Open Government Open Innovation Open Knowledge Open Science Solidarity Sustainable Development Goals Taxonomy Teamwork Text Analytics The Publication Station

Similar Posts

  • Getting the most out of your open source software initiative
  • Open-Source technology: concepts and applications
  • Learn the Basics of Open Source from Four Initiatives Driving the Movement
  • Code for Development: celebrating two years of opening software to the public
  • The IDB is committed to the open source model for development

Footer

Banco Interamericano de Desarrollo
facebook
twitter
youtube
youtube
youtube

    Blog posts written by Bank employees:

    Copyright © Inter-American Development Bank ("IDB"). This work is licensed under a Creative Commons IGO 3.0 Attribution-NonCommercial-NoDerivatives. (CC-IGO 3.0 BY-NC-ND) license and may be reproduced with attribution to the IDB and for any non-commercial purpose. No derivative work is allowed. Any dispute related to the use of the works of the IDB that cannot be settled amicably shall be submitted to arbitration pursuant to the UNCITRAL rules. The use of the IDB's name for any purpose other than for attribution, and the use of IDB's logo shall be subject to a separate written license agreement between the IDB and the user and is not authorized as part of this CC- IGO license. Note that link provided above includes additional terms and conditions of the license.


    For blogs written by external parties:

    For questions concerning copyright for authors that are not IADB employees please complete the contact form for this blog.

    The opinions expressed in this blog are those of the authors and do not necessarily reflect the views of the IDB, its Board of Directors, or the countries they represent.

    Attribution: in addition to giving attribution to the respective author and copyright owner, as appropriate, we would appreciate if you could include a link that remits back the IDB Blogs website.



    Privacy Policy

    Copyright © 2025 · Magazine Pro on Genesis Framework · WordPress · Log in

    Banco Interamericano de Desarrollo

    Aviso Legal

    Las opiniones expresadas en estos blogs son las de los autores y no necesariamente reflejan las opiniones del Banco Interamericano de Desarrollo, sus directivas, la Asamblea de Gobernadores o sus países miembros.

    facebook
    twitter
    youtube
    This site uses cookies to optimize functionality and give you the best possible experience. If you continue to navigate this website beyond this page, cookies will be placed on your browser.
    To learn more about cookies, click here
    x
    Manage consent

    Privacy Overview

    This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
    Necessary
    Always Enabled
    Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
    Non-necessary
    Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
    SAVE & ACCEPT