Download as
Browse Code »

Commit 6d2c48b82d3355f95e1976cbfd239f269870fcaf

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

[opensym] We've a 10 pages version

Showing 3 changed files with 5 additions and 12 deletions   Show diff stats
opensym2017/content/01-introduction.tex
  Diff comments   View file @6d2c48b
... ... @@ -30,9 +30,8 @@ and traditional processes and the lack of expertise of public agents in
30 30 real-world software development produce inefficiency in software development
31 31 contracts, besides unjustifiable expending of taxpayers money.
32 32  
33   -Since 2009, the SPB Portal has had several technical issues. The original
34   -codebase development has stopped, leaving substantial technical
35   -debt~\cite{refactoring}. The system was a modified version of an existing
  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
36 35 FLOSS platform called OpenACS\footnote{\url{http://openacs.org}}, and the old
37 36 SPB Portal did not receive updates from OpenACS releases. In this scenario,
38 37 the portal maintenance has become increasingly difficult.
... ...
opensym2017/content/06-architecture.tex
  Diff comments   View file @6d2c48b
... ... @@ -88,7 +88,7 @@ tracking.
88 88  
89 89 \subsection{Mezuro}
90 90  
91   -Mezuro\footnote{\url{http://mezuro.org/}} \cite{mezuro_oss} is a platform to
  91 +Mezuro\footnote{\url{http://mezuro.org/}} is a platform to
92 92 collect source code metrics to monitor the internal quality of software written
93 93 in C, C++, Java, Python, Ruby, and PHP.
94 94  
... ...
opensym2017/content/09-conclusion.tex
  Diff comments   View file @6d2c48b
... ... @@ -63,9 +63,6 @@ focused on providing a friendly working environment as well as on showing to
63 63 governmental agents another way to interact with the FLOSS community and the
64 64 university.
65 65  
66   -\subsection{Lessons Learned}
67   -\label{sec:lessons}
68   -
69 66 From the answers of our initial open questions, we can also highlighted six lessons learned to make easier to share our experience during the development of the new SPB Portal.
70 67  
71 68 \textbf{L1 -- The participation of experienced professionals is crucial to
... ... @@ -172,12 +169,9 @@ should have been more involved with the process so they could at least be
172 169 comfortable in managing the platform infrastructure.
173 170  
174 171  
175   -\textbf{Final remarks and future work}
176   -
177   -The portal is available at \url{softwarepublico.gov.br}. All
  172 +Ultimately, the SPB portal is available at \url{softwarepublico.gov.br}. All
178 173 documentation, including detailed architecture and operation manuals are
179   -also available\footnote{\url{https://softwarepublico.gov.br/doc/}
180   -(in Portuguese only at the moment)}.
  174 +also available\footnote{\url{https://softwarepublico.gov.br/doc/}}.
181 175 %
182 176 All the integrated tools are FLOSS and our contributions were published
183 177 in open repositories, available on the SPB Portal itself. We also
... ...