Download as
Browse Code »

Commit e987624a333bb843ebae6051a9ebccbd1c153b2f

Authored by Melissa Wen
1 parent 5a28462a
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

[i3eSW] small fix on intro

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