Download as
Browse Code »

Commit 5b64ad75e2ec56aa54e34b565aa12b08b1e9ed19

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

Removing Figure 1 and using FLOSS only

Showing 7 changed files with 20 additions and 26 deletions   Show diff stats
opensym2017/content/01-introduction.tex
  Diff comments   View file @5b64ad7
... ... @@ -4,7 +4,9 @@
4 4 The Brazilian Federal Government has been
5 5 improving its processes for software contracting and development. For
6 6 instance, in 2003, the recommendation to adopt Free/Libre/Open Source
7   -Software (FLOSS) became a public policy. In 2007, the Brazilian
  7 +Software (FLOSS\footnote{In this work, the acronym ``FLOSS'' is
  8 + used as a representative for ``Free Software'', ``Open Source Software'' (OSS), and
  9 + ``Free/Open Source Software'' (FOSS).}) became a public policy. In 2007, the Brazilian
8 10 Government released the Brazilian Public Software Portal
9 11 (\textit{Portal do Software Público Brasileiro}, in Portuguese), with the
10 12 goal of sharing FLOSS projects developed by, or for, the Brazilian
... ... @@ -47,12 +49,7 @@ project during 30 months, UnB was funded by a grant
47 49 of 2,619,965.00 BRL (about 750,000.00 USD in June 2016)
48 50 from the Federal Government.
49 51  
50   -\begin{figure*}[hbt]
51   - \centering
52   - \includegraphics[width=.9\linewidth]{figures/home-SPB_2.png}
53   - \caption{The new SPB Portal.}
54   - \label{fig:spb}
55   -\end{figure*}
  52 +
56 53  
57 54 The project was developed by a team of three professors, two masters students,
58 55 about fifty undergraduate students (not all of them at the same time,
... ... @@ -70,7 +67,6 @@ FLOSS~\cite{kon2011,deKoenigsberg2008, fagerholm2013, fagerholm2014} and
70 67 Agile~\cite{steghofer2016, harzl2017} practices for Software Engineering
71 68 education.
72 69  
73   -Figure \ref{fig:spb} shows the home page of this integrated platform.
74 70 All the code was developed as open source. The changes we needed in the
75 71 FLOSS tools were implemented by ourselves and
76 72 contributed back to their respective communities. Our
... ... @@ -78,7 +74,7 @@ process was based on agile practices and FLOSS communities interaction.
78 74 We incrementally released five versions of the new SPB
79 75 Portal. The first release (beta) was in September 2014, only 9 months
80 76 from the beginning of the project. The old portal was shut down in
81   -September 2015. Finally, the last version, illustrated in Figure 1, was
  77 +September 2015. Finally, the last version was
82 78 released in June 2016.
83 79  
84 80 In this paper, we present an overview of the new SPB Portal.
... ...
opensym2017/content/03-relatedworks.tex
  Diff comments   View file @5b64ad7
... ... @@ -17,17 +17,17 @@ OSOR\footnote{\url{https://joinup.ec.europa.eu/community/osor}} and
17 17 OW2\footnote{\url{http://ow2.org}}. The Open Source Observatory (OSOR) is a
18 18 community hosted in the JoinUp platform powered by the European Commission.
19 19 OSOR aims at exchanging information, experiences and best practices around the
20   -use of FOSS in the public administration. It helps to find a FOSS made
  20 +use of FLOSS in the public administration. It helps to find a FLOSS made
21 21 available by other public administrations, providing access to information such
22 22 as news, events, studies and solutions related to implementation of open source
23 23 software. It also offers forum discussions and community mailing lists, but it
24 24 does not have an integrated source code repository manager and for the each
25 25 project there is a link to its own external repository (or its tarball file).
26 26 %
27   -OW2 is a FOSS community to promote the development of FOSS middleware, generic
  27 +OW2 is a FLOSS community to promote the development of FLOSS middleware, generic
28 28 business applications, cloud computing platforms and foster a community and
29 29 business ecosystem. In short, it aims to support the development, deployment
30   -and management of distributed applications with a focus on FOSS middleware and
  30 +and management of distributed applications with a focus on FLOSS middleware and
31 31 related development and management tools.
32 32  
33 33 Moreover, in 2007 the European Comission published a study examined the impact
... ...
opensym2017/content/05-requirements.tex
  Diff comments   View file @5b64ad7
... ... @@ -44,7 +44,7 @@ requirements were:
44 44  
45 45  
46 46 There were other requirements based on the experience of the IT
47   -stakeholders from the Brazilian government and from the Brazilian FOSS
  47 +stakeholders from the Brazilian government and from the Brazilian FLOSS
48 48 community (that UnB and USP were representing too in this project). The
49 49 new platform would only work properly if there is a unique
50 50 authentication to use the provided tools. Additionally, a unified
... ... @@ -71,7 +71,7 @@ web-based source code static analysis monitor. By analyzing all of these
71 71 requirements, we proposed the technological requirements
72 72 illustrated in Figure \ref{fig:requirements} to guide the development of
73 73 the new SPB platform. In other words, we have designed the SPB evolution
74   -project based on existing FOSS tools. However, the integration of
  74 +project based on existing FLOSS tools. However, the integration of
75 75 several existing systems that were already implemented in different
76 76 programming languages and frameworks, adding features such as a
77 77 centralized authentication, unified interface, and a search engine, as
... ...
opensym2017/content/06-architecture.tex
  Diff comments   View file @5b64ad7
... ... @@ -5,13 +5,13 @@ From the point of view of the architecture, two main requirements was
5 5 brought by the Brazilian Federal Government for the new platform:
6 6  
7 7 \begin{enumerate}
8   - \item \textit{Integrate existing FOSS systems}, with minimal differences from
  8 + \item \textit{Integrate existing FLOSS systems}, with minimal differences from
9 9 their original versions;
10 10 \item \textit{Provide a consistent user interface} across the different
11 11 systems, as well as centralized authentication.
12 12 \end{enumerate}
13 13  
14   -Adopting existing FOSS systems and minimizing locally-made changes had
  14 +Adopting existing FLOSS systems and minimizing locally-made changes had
15 15 the objective of being able to upgrade to newer versions of the original
16 16 software, benefiting from improvements and maintenance done by the
17 17 existing project communities. Providing a consistent user interface on
... ... @@ -76,7 +76,7 @@ home pages and documentation, and contact forms.
76 76 \subsection{Gitlab}
77 77  
78 78 GitLab\footnote{\url{http://gitlab.com}} is a web-based Git repository
79   -manager with wiki pages and issue tracking features. Gitlab is a FOSS
  79 +manager with wiki pages and issue tracking features. Gitlab is a FLOSS
80 80 platform and focuses on delivering a holistic solution that will see
81 81 developers from idea to production seamlessly and on a single platform.
82 82  
... ...
opensym2017/content/09-process.tex
  Diff comments   View file @5b64ad7
... ... @@ -21,7 +21,7 @@ communication to be online.
21 21  
22 22 In short, our work process was based on open and collaborative software
23 23 development practices. The development process was defined based on the
24   -adaptation of different agile and FOSS communities practices, highlighting the
  24 +adaptation of different agile and FLOSS communities practices, highlighting the
25 25 high degree of automation resulting from DevOps practices. Thus, the work
26 26 process was executed in a cadenced and continuous way.
27 27  
... ...
opensym2017/content/11-lessons.tex
  Diff comments   View file @5b64ad7
... ... @@ -56,7 +56,7 @@ opened their own companies.
56 56 \textbf{Managing different organizational cultures.}
57 57 In the beginning of the project, the Brazilian Government stakeholders
58 58 had certain expectations about the project development that, let's
59   -say, didn't exactly match our work style based on agile and FOSS practices.
  59 +say, didn't exactly match our work style based on agile and FLOSS practices.
60 60 %
61 61 We had to develop strategies that would support these different
62 62 organizational cultures. As reported in Section \ref{sec:process}, the
... ...
opensym2017/content/12-conclusion.tex
  Diff comments   View file @5b64ad7
... ... @@ -10,10 +10,10 @@ based on the results of the SPB Portal project, we point out that it is
10 10 possible to mitigate conflicts experienced in the development environment
11 11 and to conciliate governmental and academy cultures.
12 12  
13   -The SPB portal integrates more than 10 FOSS tools and provides several features,
  13 +The SPB portal integrates more than 10 FLOSS tools and provides several features,
14 14 such as social network, mailing list, version control, content management and
15 15 source code quality monitoring. Concerned with the platform susteinability and
16   -maintainabilty, the aforementioned 10 FOSS tools were integrated with minimum
  16 +maintainabilty, the aforementioned 10 FLOSS tools were integrated with minimum
17 17 differences from their official versions and the new developed features were
18 18 sent upstream to ensure an alignment between the portal systems and their
19 19 respective official versions. In the integration process, the main softwares
... ... @@ -36,7 +36,7 @@ embraced opportunities in public and private sectors, within national borders
36 36 and abroad. Some other students went further and started their own companies.
37 37  
38 38 We also demonstrate that, with some adaptations/"translation processes", it is feasible
39   -to conciliate agile methodologies and FOSS practices to develop software to
  39 +to conciliate agile methodologies and FLOSS practices to develop software to
40 40 governmental organizations with functional hierarchical structures that use
41 41 traditional development paradigm.
42 42 Aiming at reducing client questions about workconclusion, a DevOps front was
... ... @@ -47,10 +47,8 @@ focused on providing a friendly working environment as well as on showing to
47 47 governmental agents another way to interact with the FLOSS community and the
48 48 university.
49 49  
50   -\leo{Padronziar uso FOSS vs FLOSS. Qual vcs preferem?}
51   -
52 50 Future work should use data produced by the project to validate and evaluate
53   -how the used FOSS and Agile practices have impacted the students and the
  51 +how the used FLOSS and Agile practices have impacted the students and the
54 52 governmental development process. For this, we would conduce a \textit{postmortem}
55 53 analysis using the project open data and a survey targeting the involved actors.
56 54  
... ... @@ -61,7 +59,7 @@ documentation, including detailed architecture and operation manuals are
61 59 also available\footnote{\url{https://softwarepublico.gov.br/doc/}
62 60 (in Portuguese only at the moment)}.
63 61 %
64   -All the integrated tools are FOSS and our contributions were published
  62 +All the integrated tools are FLOSS and our contributions were published
65 63 in open repositories, available on the SPB Portal itself. We also
66 64 contributed these features back to the respective communities, which
67 65 benefits both those communities and us, since we can share future
... ...