Commit 9b9fd450f871868fac7f14cd1768e5020c0356e9

Authored by Hilmer Rodrigues Neri
2 parents be8381c6 09a272a1

Merge branch 'master' of softwarepublico.gov.br:softwarepublico/articles

opensym2017/content/01-introduction.tex
@@ -46,5 +46,5 @@ changes in the team). @@ -46,5 +46,5 @@ changes in the team).
46 Figure \ref{fig:spb} shows the home page of this integrated platform. 46 Figure \ref{fig:spb} shows the home page of this integrated platform.
47 The development tried to be as faithful as possible to FOSS development. 47 The development tried to be as faithful as possible to FOSS development.
48 All development was done in the open, and the changes we needed in the 48 All development was done in the open, and the changes we needed in the
49 -tools user were contributed back to their communities. 49 +tools were contributed back to their communities.
50 50
opensym2017/content/02-spb.tex
1 -\section{Brazilian Public Software versus Free/Open Source Software} 1 +\section{Free/Open Source Software and Brazilian Public Software}
2 \label{sec:spb} 2 \label{sec:spb}
3 3
4 -FOSS is considered a recent phenomenon that has gained notoriety in recent years and has been arousing a interest of observation by the academy. However, since the beginning of computing the majority of developers worked in the way that we now identify as free software, that is, sharing code openly. This feature makes the code available for inspection, modification, and use by any person or organization \cite{kon2012}, \cite{hippel2003}. 4 +FOSS is a phenomenon that has gained notoriety in recent years and has been attarcting the interest of academia. However, since the beginning of computing the majority of developers worked in the way that we now identify as free software, that is, sharing code openly. This feature makes the code available for inspection, modification, and use by any person or organization \cite{kon2012}, \cite{hippel2003}.
5 5
6 The elements that distinguish FOSS from other types of software are the reasoning about the development process, the economic context, the relationship between developers and users, as well as the ethical and legal characteristics that relate to the software. In the context of free software, user freedom is promoted and its development is based on open collaboration and development practices \cite{meirelles2013}. 6 The elements that distinguish FOSS from other types of software are the reasoning about the development process, the economic context, the relationship between developers and users, as well as the ethical and legal characteristics that relate to the software. In the context of free software, user freedom is promoted and its development is based on open collaboration and development practices \cite{meirelles2013}.
7 7
8 -From the economic point of view, unlike what happens with proprietary, restricted software, FOSS promotes the establishment of several suppliers that compete with each other based on the same software. This stronger competition among suppliers brings benefits to users because it gives better assurances regarding the evolution of the system and induces a reduction in prices. These freedoms and assurances on software are guaranteed in Brazil by Law 9610/98, copyright law. Most of the time, this protection from the law complies the terms conferred by a contract related to certain software. This contract is called `` license ''. The license of a software determines a list of rights and duties that are projected on a user of the software. In particular, what differentiates FOSS from proprietary software is just the way of licensing\cite{sabino2009}. The FOSS licenses are the ones that guarantee the right to execute, study, adapt, and improve the software, such as the \textit{GPL (GNU General Public License)} licenses accepted for projects hosted in the SPB. 8 +From the economic point of view, unlike what happens with proprietary software, FOSS promotes the establishment of several suppliers that compete with each other based on the same software. This stronger competition among suppliers brings benefits to users because it gives better assurances regarding the evolution of the system and induces a reduction in prices. These freedoms and assurances on software are guaranteed in Brazil by Law 9610/98, copyright law. Most of the time, this protection from the law complies with the terms conferred by a contract related to certain software. This contract is called ``license''. The license of a software determines a list of rights that are given to, and duties that are imposed on a user of the software. In particular, what differentiates FOSS from proprietary software is just the way they are licensed\cite{sabino2009}. The FOSS licenses guarantee the right to execute, study, adapt, and improve the software. Example of common FOSS licenses are the \textit{GPL (GNU General Public License)}, the Apache license, the MIT license, and the BSD license.
9 9
10 The SPB has been released in 2007. In a practical view, is a web system that has consolidated itself as a software project sharing environment. It provides a space (community) for each software. Therefore, the current platform for SPB was designed to include tools that promote collaboration and interaction in communities (by managers, users and 10 The SPB has been released in 2007. In a practical view, is a web system that has consolidated itself as a software project sharing environment. It provides a space (community) for each software. Therefore, the current platform for SPB was designed to include tools that promote collaboration and interaction in communities (by managers, users and
11 developers) of the projects, according to the practices used in FOSS communities. This includes e-mail lists, discussion forums, issue trackers, version control systems, and social networking environments. 11 developers) of the projects, according to the practices used in FOSS communities. This includes e-mail lists, discussion forums, issue trackers, version control systems, and social networking environments.
12 12
13 Initially, the purpose of the portal was only to share the software developed in the brazilian government, in order to reduce the costs of hiring software. However it was observed that when the software were released, communities were formed around those software with several people collaborating and sharing the results obtained through the use of those solutions. In this way, some software development cooperatives and private companies have shown an interest in making their software available on the SPB platform. 13 Initially, the purpose of the portal was only to share the software developed in the brazilian government, in order to reduce the costs of hiring software. However it was observed that when the software were released, communities were formed around those software with several people collaborating and sharing the results obtained through the use of those solutions. In this way, some software development cooperatives and private companies have shown an interest in making their software available on the SPB platform.
14 14
15 -The concept of brazilian public software differs from FOSS in some aspects highlighting the attribution of public good to software and the obligation of the software to be in the SPB. Although there are some differences between what is FOSS and brazilian public software, there are common principles, such as the tendency for decentralization in decision-making, the intense sharing of information and feedback processes resulting from the use of artifacts produced. On the one hand, FOSS presents itself as an already consolidated and viable model in an increasing number of applications and environments. On the other hand, legal and economic uncertainties remain. Some of these challenges are associated to the barriers created by the proprietary software model and culture \cite{kon2012}. Besides these, there are also difficulties for the entry and permanence of new contributors in the projects. In SPB context probably due to the organizational structure and bureaucratic processes of the Brazilian Federal Government.  
16 -  
17 -% TODO  
18 -% Criar uma seção de related works 15 +The concept of Brazilian Public Software goes beyond FOSS. In addition to being licensed under a FOSS license, a Brazilian Public Software needs to have explicit guarantees that it is a public good, and that project must be available in the SPB. Being a true public good assumes requirements that can't be met solely by means of FOSS licensing. For example, there must be a relaxed trademark usage policy by the original vendor that don't stop eventual competitors from adversiting services for that same software. Inclusion in the SPB also has extra requirements, such as having a public version control system, installation manual, hardware requirements specification, etc.
opensym2017/content/03-requirements.tex
@@ -11,7 +11,7 @@ By preparing the evolution project described in this paper, the Brazilian @@ -11,7 +11,7 @@ By preparing the evolution project described in this paper, the Brazilian
11 government promote 3 events to collect the requirements, in particular from 11 government promote 3 events to collect the requirements, in particular from
12 society point of view: (i) an online form to collect general ideas; (ii) a 12 society point of view: (i) an online form to collect general ideas; (ii) a
13 face-to-face meeting with society in general; (iii) a workshop to review the 13 face-to-face meeting with society in general; (iii) a workshop to review the
14 -SPB concepts and requirements with IT stockholders from the Brazilian 14 +SPB concepts and requirements with IT stakeholders from the Brazilian
15 government and public organizations. 15 government and public organizations.
16 16
17 After these 3 rounds discussing the new SPB platform, the Brazilian government listed 17 After these 3 rounds discussing the new SPB platform, the Brazilian government listed
@@ -91,7 +91,7 @@ Also, there are two initiatives in Europe: OSOR and OW2. The Open Source @@ -91,7 +91,7 @@ Also, there are two initiatives in Europe: OSOR and OW2. The Open Source
91 Observatory (OSOR) is a community hosted in the JoinUp platform powereded by 91 Observatory (OSOR) is a community hosted in the JoinUp platform powereded by
92 the European Commission. OSOR aims exchanging information, experiences and best 92 the European Commission. OSOR aims exchanging information, experiences and best
93 practices around FOSS solutions for use in public administrations. Summarily, 93 practices around FOSS solutions for use in public administrations. Summarily,
94 -it helps to find an FOSS made available by other public administrations, 94 +it helps to find a FOSS made available by other public administrations,
95 providing access to information such as news, events, studies and solutions 95 providing access to information such as news, events, studies and solutions
96 related to implementation of open source software. It also offers forum 96 related to implementation of open source software. It also offers forum
97 discussions and community mailing lists, but it does not have an integrated 97 discussions and community mailing lists, but it does not have an integrated
@@ -107,7 +107,7 @@ related development and management tools. @@ -107,7 +107,7 @@ related development and management tools.
107 Moreover, from the European Commission in 2007 until 20011, there were the 107 Moreover, from the European Commission in 2007 until 20011, there were the
108 QualiPSo project that aims to provide to FOSS users, developers, and consumers, 108 QualiPSo project that aims to provide to FOSS users, developers, and consumers,
109 quality resources and expertise on the various topics related to FOSS. The 109 quality resources and expertise on the various topics related to FOSS. The
110 -QualiPSo project also have plained to develop a platform called QualiPSo 110 +QualiPSo project also had planned to develop a platform called QualiPSo
111 Factory but it was not fully completed. 111 Factory but it was not fully completed.
112 112
113 In Latin American has an initiative based on the SPB project called Software 113 In Latin American has an initiative based on the SPB project called Software
opensym2017/content/08-contributions.tex
@@ -26,7 +26,7 @@ version was made (web framework used by Colab). Moreover, we worked on RevProxy @@ -26,7 +26,7 @@ version was made (web framework used by Colab). Moreover, we worked on RevProxy
26 Gitlab was the tool that we made the least number of modifications. We 26 Gitlab was the tool that we made the least number of modifications. We
27 contributed with some improvements related with configuration files and we 27 contributed with some improvements related with configuration files and we
28 developed a new omniauth plugin, which enables the user authentication in 28 developed a new omniauth plugin, which enables the user authentication in
29 -Gitlab via remote\_user HTTP header. This omniauth plugin was needed because 29 +Gitlab via REMOTE\_USER HTTP header. This omniauth plugin was needed because
30 Colab uses this mechanism to manage the authentication. 30 Colab uses this mechanism to manage the authentication.
31 31
32 Noosfero was the tool that contemplated several functional requirements, 32 Noosfero was the tool that contemplated several functional requirements,