Download as
Browse Code »

Commit 31a7b521e8fc6ad0494ee32ea78e37e56efb7a29

Authored by Antonio Terceiro
1 parent 361d9e5a
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

content/02-spb.tex: review

Showing 1 changed file with 22 additions and 20 deletions   Show diff stats
opensym2017/content/02-spb.tex
  Diff comments   View file @31a7b52
... ... @@ -2,9 +2,9 @@
2 2 \label{sec:spb}
3 3  
4 4 FOSS is a phenomenon that has gained notoriety in recent years and has been
5   -attarcting the interest of academia. However, since the beginning of computing
  5 +attracting the interest of academia. However, since the beginning of computing
6 6 the majority of developers worked in the way that we now identify as free
7   -software, that is, sharing code openly. This feature makes the code available
  7 +software, that is, sharing code openly. This openness makes the code available
8 8 for inspection, modification, and use by any person or organization
9 9 \cite{hippel2003,kon2012}.
10 10  
... ... @@ -16,7 +16,7 @@ and its development is based on open collaboration and development practices
16 16 \cite{meirelles2013}.
17 17  
18 18 From the economic point of view, unlike what happens with proprietary software,
19   -FOSS promotes the establishment of several suppliers that compete with each
  19 +FOSS promotes the establishment of several suppliers that can compete with each
20 20 other based on the same software. This stronger competition among suppliers
21 21 brings benefits to users because it gives better assurances regarding the
22 22 evolution of the system and induces a reduction in prices \cite{kon2012}. These
... ... @@ -31,14 +31,15 @@ study, adapt, and improve the software. Example of common FOSS licenses are
31 31 the \textit{GPL (GNU General Public License)}, the Apache license, the MIT
32 32 license, and the BSD license.
33 33  
34   -The SPB portal has been designed in 2005 and released in 2007. In a practical
35   -view, it is a web system that has consolidated itself as a software project
36   -sharing environment. It provides a space (community) for each software.
37   -Therefore, the current platform for SPB was designed to include tools that
38   -promote collaboration and interaction in communities (by managers, users, and
39   -developers) of the projects, according to the practices used in FOSS
40   -communities. This includes e-mail lists, discussion forums, issue trackers,
41   -version control systems, and social networking environments.
  34 +The original incarnation of SPB portal has been designed in 2005 and
  35 +released in 2007. From a practical point of view, it is a web system
  36 +that has consolidated itself as an environment for sharing software
  37 +projects. It provides a space (community) for each software.
  38 +Therefore, it was designed to include tools that promote collaboration
  39 +and interaction in communities (by managers, users, and developers) of
  40 +the projects, according to the practices used in FOSS communities. This
  41 +includes mailing lists, discussion forums, issue trackers, version
  42 +control systems, and social networking environments.
42 43  
43 44 Initially, the purpose of the portal was only to share the software developed
44 45 in the Brazilian government, to reduce the costs of hiring software. However,
... ... @@ -48,13 +49,14 @@ results obtained through the use of those solutions. In this way, some software
48 49 development cooperatives and private companies have shown an interest in making
49 50 their software available on the SPB platform.
50 51  
51   -The concept of Brazilian Public Software goes beyond FOSS. In addition to being
52   -licensed under a FOSS license, a SPB needs to have explicit guarantees that it
53   -is a public good, and that project must be available in the SPB portal. Being a
54   -true public good assumes requirements that can not be met solely by means of
55   -FOSS licensing. For example, there must be a relaxed trademark usage policy by
56   -the original vendor that do not stop eventual competitors from adversiting
57   -services for that same software. Inclusion in the SPB project also has extra
58   -requirements, such as having a public version control system, installation
59   -manual, and hardware requirements specification.
  52 +The concept of Brazilian Public Software goes beyond FOSS. In addition
  53 +to being licensed under a FOSS license, a SPB needs to have explicit
  54 +guarantees that it is a public good, and that project must be available
  55 +in the SPB portal. Being a true public good assumes requirements that
  56 +can not be met solely by means of FOSS licensing. For example, there
  57 +must be a relaxed trademark usage policy by the original vendor that
  58 +does not stop eventual competitors from advertising services for that
  59 +same software. Inclusion in the SPB Portal also has extra requirements,
  60 +such as having a public version control system, installation manual, and
  61 +hardware requirements specification.
60 62  
... ...