From e987624a333bb843ebae6051a9ebccbd1c153b2f Mon Sep 17 00:00:00 2001 From: Melissa Wen Date: Tue, 1 Aug 2017 10:16:11 -0400 Subject: [PATCH] [i3eSW] small fix on intro --- ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md index a9e0c37..bf245b6 100644 --- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md +++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md @@ -11,7 +11,7 @@ competitive benefits. In our experience, it was much more: it was a survival technique. This article presents how we applied CD in a Brazilian Government project for the development of a Collaborative Development Environment (CDE), sharing its unconventional challenges and the strategies used to overcome them. -This report from the trench of the Brazilian Federal Government can help +This report can help practitioners to understand how important CD adoption is to their projects. ## Introduction and Context @@ -23,10 +23,10 @@ team from the University of Brasília (UnB) and the University of São Paulo Portuguese acronym) Portal from 2014 to 2016. The SPB Portal (www.softwarepublico.gov.br) evolved to a Collaborative Development Environment [1] and this evolution brought important benefits not just to the Brazilian -government, but also to society as a whole. For the government, the bureaucracy -of using the same software across governmental agencies and the cost of -developing similar software projects were all reduced. The society gained a -transparent and collaborative mechanism, since anyone can check the government +government, but also to society as a whole. The government could reduce both +the bureaucracy of using the same software in government agencies and the cost +of developing similar software projects. The society gained a mechanism of +transparency and collaboration, since anyone can check the government expenses on software and contribute to project communities. To achieve these goals, rather than writing everything from scratch, we decided to integrate 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, which were influenced most of the time by the uncertainties of the project's continuity. We believed we would keep the project alive, even in a politically unstable and technically complex scenario. For this reason, we focused on -automating automate the deploy process; for instance, one of our senior +automating the deploy process; for instance, one of our senior developers created a Chef-Server (www.chef.io/chef) front-end tool called Chake (www.gitlab.com/terceiro/chake) to help us manage the multiple hosts needed for the project. We also formed a specific team dedicated to the deployment -- libgit2 0.21.2