Download as
Browse Code »

Commit d11961e3a4d7da9b224df83ee107932986013696

Authored by Rodrigo Siqueira de Melo
2 parents 68eb237c c550f847
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

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

Showing 1 changed file with 6 additions and 6 deletions   Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
  Diff comments   View file @d11961e
@@ -12,7 +12,7 @@ competitive benefits. In our experience, it was much more: it was a survival @@ -12,7 +12,7 @@ competitive benefits. In our experience, it was much more: it was a survival
12 technique. This article presents how we applied CD in a Brazilian Government 12 technique. This article presents how we applied CD in a Brazilian Government
13 project for the development of a Collaborative Development Environment (CDE), 13 project for the development of a Collaborative Development Environment (CDE),
14 sharing its unconventional challenges and the strategies used to overcome them. 14 sharing its unconventional challenges and the strategies used to overcome them.
15 -This report from the trench of the Brazilian Federal Government can help 15 +This report can help
16 practitioners to understand how important CD adoption is to their projects. 16 practitioners to understand how important CD adoption is to their projects.
17 17
18 ## Introduction and Context 18 ## Introduction and Context
@@ -24,10 +24,10 @@ team from the University of Brasília (UnB) and the University of São Paulo @@ -24,10 +24,10 @@ team from the University of Brasília (UnB) and the University of São Paulo
24 Portuguese acronym) Portal from 2014 to 2016. The SPB Portal 24 Portuguese acronym) Portal from 2014 to 2016. The SPB Portal
25 (www.softwarepublico.gov.br) evolved to a Collaborative Development Environment 25 (www.softwarepublico.gov.br) evolved to a Collaborative Development Environment
26 [1] and this evolution brought important benefits not just to the Brazilian 26 [1] and this evolution brought important benefits not just to the Brazilian
27 -government, but also to society as a whole. For the government, the bureaucracy  
28 -of using the same software across governmental agencies and the cost of  
29 -developing similar software projects were all reduced. The society gained a  
30 -transparent and collaborative mechanism, since anyone can check the government 27 +government, but also to society as a whole. The government could reduce both
  28 +the bureaucracy of using the same software in government agencies and the cost
  29 +of developing similar software projects. The society gained a mechanism of
  30 +transparency and collaboration, since anyone can check the government
31 expenses on software and contribute to project communities. To achieve these 31 expenses on software and contribute to project communities. To achieve these
32 goals, rather than writing everything from scratch, we decided to integrate 32 goals, rather than writing everything from scratch, we decided to integrate
33 several free software tools such as Noosfero (www.noosfero.org), Gitlab 33 several free software tools such as Noosfero (www.noosfero.org), Gitlab
@@ -83,7 +83,7 @@ the government expectations and to provide quick response to their requests, @@ -83,7 +83,7 @@ the government expectations and to provide quick response to their requests,
83 which were influenced most of the time by the uncertainties of the project's 83 which were influenced most of the time by the uncertainties of the project's
84 continuity. We believed we would keep the project alive, even in a politically 84 continuity. We believed we would keep the project alive, even in a politically
85 unstable and technically complex scenario. For this reason, we focused on 85 unstable and technically complex scenario. For this reason, we focused on
86 -automating automate the deploy process; for instance, one of our senior 86 +automating the deploy process; for instance, one of our senior
87 developers created a Chef-Server (www.chef.io/chef) front-end tool called Chake 87 developers created a Chef-Server (www.chef.io/chef) front-end tool called Chake
88 (www.gitlab.com/terceiro/chake) to help us manage the multiple hosts needed for 88 (www.gitlab.com/terceiro/chake) to help us manage the multiple hosts needed for
89 the project. We also formed a specific team dedicated to the deployment 89 the project. We also formed a specific team dedicated to the deployment