Download as
Browse Code »

Commit cda07a26a1e2206bcff660efff3db6fc348147cd

Authored by Paulo Meireles
1 parent 4aa1e8a2
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

[opensym] more space

Showing 2 changed files with 27 additions and 24 deletions   Show diff stats
opensym2017/content/01-introduction.tex
  Diff comments   View file @cda07a2
... ... @@ -3,25 +3,28 @@
3 3  
4 4 The Brazilian Government released in the year 2000 the Eletronic Government
5 5 program (eGov) aiming at democratizing information access and improving the
6   -public provision quality of service and information. In 2003, the Federal
7   -Government created a
8   -committee\footnote{\url{http://www.softwarelivre.gov.br/documentos-oficiais/
9   -DecretoComite}} for implementation of Free/Libre/Open Source Software
10   -(FLOSS\footnote{In this work, the acronym ``FLOSS'' is used as a representative
11   -for ``Free Software'', ``Open Source Software'' (OSS), and``Free/Open Source
12   -Software'' (FOSS).}) and thereafter a circular-letter was sent to all
13   -Ministries in which the recommendation to adopt FLOSS became a public
14   -policy\footnote{\url{http://www.softwarelivre.gov.br/documentos-oficiais/circulardoministro}}.
  6 +public provision quality of service and information.
  7 +%
  8 +In 2003, the Federal Government created a committee for implementation of
  9 +Free/Libre/Open Source Software (FLOSS\footnote{In this work, the acronym
  10 +``FLOSS'' is used as a representative for ``Free Software'', ``Open Source
  11 +Software'' (OSS), and``Free/Open Source Software'' (FOSS).}) and thereafter a
  12 +circular-letter was sent to all Ministries in which the recommendation to adopt
  13 +FLOSS became a public policy.
  14 +%
15 15 In 2007, the Brazilian Public Software Portal (\textit{Portal do Software
16 16 Público Brasileiro}, in Portuguese) was released with the goal of sharing FLOSS
17   -projects developed by, or for, the Brazilian Government. Additionally, the
18   -Brazilian legal instrument on software contracting (known as IN 04/2012)
19   -mandates that public agents must prioritize solutions available on the SPB
20   -Portal. The acquisition of a proprietary solution must be explicitly justified
21   -by demonstrating that there is no suitable alternative on the SPB Portal. In
22   -2013, the Brazilian Federal Court issued a ruling (\textit{Acórdão 2314/2013})
23   -about contracts between the public administration and suppliers using agile
24   -methodologies in software development.
  17 +projects developed by, or for, the Brazilian Government.
  18 +%
  19 +Additionally, the Brazilian legal instrument on software contracting (known as
  20 +IN 04/2012) mandates that public agents must prioritize solutions available on
  21 +the SPB Portal. The acquisition of a proprietary solution must be explicitly
  22 +justified by demonstrating that there is no suitable alternative on the SPB
  23 +Portal.
  24 +%
  25 +In 2013, the Brazilian Federal Court issued a ruling (\textit{Acórdão
  26 +2314/2013}) about contracts between the public administration and suppliers
  27 +using agile methodologies in software development.
25 28  
26 29 Despite of these legal advancements, in practice, Brazilian government agents
27 30 still do not practice, or even understand, collaborative and empirical software
... ... @@ -29,12 +32,12 @@ development methods, such as FLOSS or agile methodologies. Thus, hierarchical
29 32 and traditional processes and the lack of expertise of public agents in
30 33 real-world software development produce inefficiency in software development
31 34 contracts, besides unjustifiable expending of taxpayers money.
32   -
33   -For instance, since 2009 the SPB Portal has had several technical issues. The original
34   -codebase development has stopped. The system was a modified version of an existing
35   -FLOSS platform called OpenACS\footnote{\url{http://openacs.org}}, and the old
36   -SPB Portal did not receive updates from OpenACS releases. In this scenario,
37   -the portal maintenance has become increasingly difficult.
  35 +%
  36 +For instance, since 2009 the SPB Portal has had several technical issues. The
  37 +original codebase development has stopped. The system was a modified version of
  38 +an existing FLOSS platform called OpenACS\footnote{\url{http://openacs.org}},
  39 +and the old SPB Portal did not receive updates from OpenACS releases. In this
  40 +scenario, the portal maintenance has become increasingly difficult.
38 41  
39 42 After collecting requirements from the Federal Government and society, a new
40 43 platform for the SPB Portal was developed, between January 2014 and June 2016,
... ...
opensym2017/content/03-relatedworks.tex
  Diff comments   View file @cda07a2
... ... @@ -36,7 +36,7 @@ It provides a customized Gitlab instance to share
36 36 source code and documentation of projects developed by the involved countries.
37 37 %
38 38 Like Brazil, Chile has its own portal, called ``Repositorio Software
39   -Público''\footnote{\url{http://www.softwarepublico.gob.cl}}. In the communities of the portal,
  39 +Público''\footnote{\url{http://softwarepublico.gob.cl}}. In the communities of the portal,
40 40 users can create content such as news, documents, and wiki pages, but source code
41 41 repositories are available at the Bitbucket
42 42 platform\footnote{\url{https://bitbucket.org/softwarepublico}}.
... ...