diff --git a/opensym2017/content/12-conclusion.tex b/opensym2017/content/12-conclusion.tex index 6e8570d..cf45e00 100644 --- a/opensym2017/content/12-conclusion.tex +++ b/opensym2017/content/12-conclusion.tex @@ -1,48 +1,50 @@ \section{Conclusion} \label{sec:conclusion} -In this paper we present and discuss issues experienced during a government- -funded project, in partnership with University of Brasilia and University of -São Paulo, to evolve the Brazilian Public Software portal. - -The contributions of this paper are twofold. First, we present how an unprecedent -platform was developed and delivered to Brazilian government. This -platform - developed by an heterogenous team of professors, masters and -undergraduate students, IT professionals and governmental managers - provides -several modern features from the integration of more than 10 FLOSS systems. - -Second, the thirty-month long project in which the SPB platform was developed points -out that it is possible to mitigate issues seen as conflicting to the IT -development environment and between industry and academy. The team was engaged in +In this paper we presented and discussed issues experienced during a government-funded +project, in partnership with the University of Brasilia and the University of +São Paulo, to evolve the Brazilian Public Software Portal. + +The contributions of this paper are twofold. First, we presented how an unprecedented +platform was developed and delivered to the Brazilian government. This +platform - developed by a heterogeneous team of professors, masters and +undergraduate students, IT professionals, and governmental managers - provides +several modern features for the integration of more than 10 FLOSS systems. + +Second, the experience in the SPB Portal project pointed +out that it is possible to mitigate conflicts in the development environment +and to conciliate governmental and academy cultures. The team was engaged in providing a friendly working environment as well as in showing to governmental agents another way to interact with the FLOSS community and the university. In the paper, -we try to show that, as long as the institution can provide a healthy and challenging +we tried to show that, as long as the institution can provide a healthy and challenging environment to its students, one may conciliate studies and professional training in universities. After the end of the project, some students successfully -embraced opportunities in public and private sectos, within national borders -and abroad. Some others went further and started their own companies. +embraced opportunities in public and private sectors, within national borders +and abroad. Some other students went further and started their own companies. We also demonstrate that, with some adaptations/"translation processes", it is feasible to conciliate agile methodologies and FOSS practices in order to develop software to governmental organizations with functional hierarchical structures that use traditional development paradigm. -Future work should use the many data produced by the project to validate and evaluate +\leo{Padronziar uso FOSS vs FLOSS. Qual vcs preferem?} + +Future work should use data produced by the project to validate and evaluate how the used FLOSS and Agile practices have impacted the students and also the -governmental development process. For this, we would conduce a \textit{post-mortem} -analyse using the project open data and a survey targeted the involved actors. +governmental development process. For this, we would conduce a \textit{postmortem} +analysis using the project open data and a survey targeting the involved actors. The portal is available at \url{softwarepublico.gov.br}. All documentation, including detailed architecture and operation manuals are also available\footnote{\url{https://softwarepublico.gov.br/doc/} -(in Portuguese only at the moment)}). +(in Portuguese only at the moment)}. % All the integrated tools are FOSS and our contributions were published in open repositories, available on the SPB Portal itself. We also -contributed these features back to the respective communities: that -benefits those communities, as well as us since we can share future +contributed these features back to the respective communities, which +benefits both those communities and us, since we can share future development and maintenance effort with other organizations that -participate in their projects. +participate in these projects. %=========== % Conclusion diff --git a/opensym2017/spb.tex b/opensym2017/spb.tex index a1a2ae2..210986e 100644 --- a/opensym2017/spb.tex +++ b/opensym2017/spb.tex @@ -72,6 +72,13 @@ % by using the "\todo{...}" command. Make sure to disable the draft % option again before submitting your final document. \usepackage{todonotes} +\newcommand{\leo}[2][]{\todo[inline,color=yellow!70, #1]{\emph{Léo:} #2}} +\newcommand{\paulo}[2][]{\todo[inline,color=yellow!70, #1]{\emph{Paulo:} #2}} +\newcommand{\melissa}[2][]{\todo[inline,color=yellow!70, #1]{\emph{Melissa:} #2}} +\newcommand{\terceiro}[2][]{\todo[inline,color=yellow!70, #1]{\emph{Terceiro:} #2}} +\newcommand{\siqueira}[2][]{\todo[inline,color=yellow!70, #1]{\emph{Siqueira:} #2}} +\newcommand{\lucas}[2][]{\todo[inline,color=yellow!70, #1]{\emph{Lucas:} #2}} +\newcommand{\hilmer}[2][]{\todo[inline,color=yellow!70, #1]{\emph{Hilmer:} #2}} % Paper metadata (use plain text, for PDF inclusion and later % re-using, if desired). Use \emtpyauthor when submitting for review @@ -164,6 +171,8 @@ } } + + \maketitle %------------------------------------------------------------------------------ \input{content/00-abstract} -- libgit2 0.21.2