From 5b64ad75e2ec56aa54e34b565aa12b08b1e9ed19 Mon Sep 17 00:00:00 2001 From: Paulo Meirelles Date: Mon, 24 Jul 2017 15:06:32 -0300 Subject: [PATCH] Removing Figure 1 and using FLOSS only --- opensym2017/content/01-introduction.tex | 14 +++++--------- opensym2017/content/03-relatedworks.tex | 6 +++--- opensym2017/content/05-requirements.tex | 4 ++-- opensym2017/content/06-architecture.tex | 6 +++--- opensym2017/content/09-process.tex | 2 +- opensym2017/content/11-lessons.tex | 2 +- opensym2017/content/12-conclusion.tex | 12 +++++------- 7 files changed, 20 insertions(+), 26 deletions(-) diff --git a/opensym2017/content/01-introduction.tex b/opensym2017/content/01-introduction.tex index 4e05a1b..0116731 100644 --- a/opensym2017/content/01-introduction.tex +++ b/opensym2017/content/01-introduction.tex @@ -4,7 +4,9 @@ The Brazilian Federal Government has been improving its processes for software contracting and development. For instance, in 2003, the recommendation to adopt Free/Libre/Open Source -Software (FLOSS) became a public policy. In 2007, the Brazilian +Software (FLOSS\footnote{In this work, the acronym ``FLOSS'' is + used as a representative for ``Free Software'', ``Open Source Software'' (OSS), and + ``Free/Open Source Software'' (FOSS).}) became a public policy. In 2007, the Brazilian Government released the Brazilian Public Software Portal (\textit{Portal do Software Público Brasileiro}, in Portuguese), with the 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 of 2,619,965.00 BRL (about 750,000.00 USD in June 2016) from the Federal Government. -\begin{figure*}[hbt] - \centering - \includegraphics[width=.9\linewidth]{figures/home-SPB_2.png} - \caption{The new SPB Portal.} - \label{fig:spb} -\end{figure*} + The project was developed by a team of three professors, two masters students, about fifty undergraduate students (not all of them at the same time, @@ -70,7 +67,6 @@ FLOSS~\cite{kon2011,deKoenigsberg2008, fagerholm2013, fagerholm2014} and Agile~\cite{steghofer2016, harzl2017} practices for Software Engineering education. -Figure \ref{fig:spb} shows the home page of this integrated platform. All the code was developed as open source. The changes we needed in the FLOSS tools were implemented by ourselves and contributed back to their respective communities. Our @@ -78,7 +74,7 @@ process was based on agile practices and FLOSS communities interaction. We incrementally released five versions of the new SPB Portal. The first release (beta) was in September 2014, only 9 months from the beginning of the project. The old portal was shut down in -September 2015. Finally, the last version, illustrated in Figure 1, was +September 2015. Finally, the last version was released in June 2016. In this paper, we present an overview of the new SPB Portal. diff --git a/opensym2017/content/03-relatedworks.tex b/opensym2017/content/03-relatedworks.tex index 9944c27..f749955 100644 --- a/opensym2017/content/03-relatedworks.tex +++ b/opensym2017/content/03-relatedworks.tex @@ -17,17 +17,17 @@ OSOR\footnote{\url{https://joinup.ec.europa.eu/community/osor}} and OW2\footnote{\url{http://ow2.org}}. The Open Source Observatory (OSOR) is a community hosted in the JoinUp platform powered by the European Commission. OSOR aims at exchanging information, experiences and best practices around the -use of FOSS in the public administration. It helps to find a FOSS made +use of FLOSS in the public administration. It helps to find a FLOSS made available by other public administrations, providing access to information such as news, events, studies and solutions related to implementation of open source software. It also offers forum discussions and community mailing lists, but it does not have an integrated source code repository manager and for the each project there is a link to its own external repository (or its tarball file). % -OW2 is a FOSS community to promote the development of FOSS middleware, generic +OW2 is a FLOSS community to promote the development of FLOSS middleware, generic business applications, cloud computing platforms and foster a community and business ecosystem. In short, it aims to support the development, deployment -and management of distributed applications with a focus on FOSS middleware and +and management of distributed applications with a focus on FLOSS middleware and related development and management tools. Moreover, in 2007 the European Comission published a study examined the impact diff --git a/opensym2017/content/05-requirements.tex b/opensym2017/content/05-requirements.tex index 4d0da46..e109b7a 100644 --- a/opensym2017/content/05-requirements.tex +++ b/opensym2017/content/05-requirements.tex @@ -44,7 +44,7 @@ requirements were: There were other requirements based on the experience of the IT -stakeholders from the Brazilian government and from the Brazilian FOSS +stakeholders from the Brazilian government and from the Brazilian FLOSS community (that UnB and USP were representing too in this project). The new platform would only work properly if there is a unique 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 requirements, we proposed the technological requirements illustrated in Figure \ref{fig:requirements} to guide the development of the new SPB platform. In other words, we have designed the SPB evolution -project based on existing FOSS tools. However, the integration of +project based on existing FLOSS tools. However, the integration of several existing systems that were already implemented in different programming languages and frameworks, adding features such as a centralized authentication, unified interface, and a search engine, as diff --git a/opensym2017/content/06-architecture.tex b/opensym2017/content/06-architecture.tex index 2e99bc9..1f414a5 100644 --- a/opensym2017/content/06-architecture.tex +++ b/opensym2017/content/06-architecture.tex @@ -5,13 +5,13 @@ From the point of view of the architecture, two main requirements was brought by the Brazilian Federal Government for the new platform: \begin{enumerate} - \item \textit{Integrate existing FOSS systems}, with minimal differences from + \item \textit{Integrate existing FLOSS systems}, with minimal differences from their original versions; \item \textit{Provide a consistent user interface} across the different systems, as well as centralized authentication. \end{enumerate} -Adopting existing FOSS systems and minimizing locally-made changes had +Adopting existing FLOSS systems and minimizing locally-made changes had the objective of being able to upgrade to newer versions of the original software, benefiting from improvements and maintenance done by the existing project communities. Providing a consistent user interface on @@ -76,7 +76,7 @@ home pages and documentation, and contact forms. \subsection{Gitlab} GitLab\footnote{\url{http://gitlab.com}} is a web-based Git repository -manager with wiki pages and issue tracking features. Gitlab is a FOSS +manager with wiki pages and issue tracking features. Gitlab is a FLOSS platform and focuses on delivering a holistic solution that will see developers from idea to production seamlessly and on a single platform. diff --git a/opensym2017/content/09-process.tex b/opensym2017/content/09-process.tex index 82781d2..43c02e5 100644 --- a/opensym2017/content/09-process.tex +++ b/opensym2017/content/09-process.tex @@ -21,7 +21,7 @@ communication to be online. In short, our work process was based on open and collaborative software development practices. The development process was defined based on the -adaptation of different agile and FOSS communities practices, highlighting the +adaptation of different agile and FLOSS communities practices, highlighting the high degree of automation resulting from DevOps practices. Thus, the work process was executed in a cadenced and continuous way. diff --git a/opensym2017/content/11-lessons.tex b/opensym2017/content/11-lessons.tex index f8b4b2e..bde54e9 100644 --- a/opensym2017/content/11-lessons.tex +++ b/opensym2017/content/11-lessons.tex @@ -56,7 +56,7 @@ opened their own companies. \textbf{Managing different organizational cultures.} In the beginning of the project, the Brazilian Government stakeholders had certain expectations about the project development that, let's -say, didn't exactly match our work style based on agile and FOSS practices. +say, didn't exactly match our work style based on agile and FLOSS practices. % We had to develop strategies that would support these different organizational cultures. As reported in Section \ref{sec:process}, the diff --git a/opensym2017/content/12-conclusion.tex b/opensym2017/content/12-conclusion.tex index 71b0655..3d76865 100644 --- a/opensym2017/content/12-conclusion.tex +++ b/opensym2017/content/12-conclusion.tex @@ -10,10 +10,10 @@ based on the results of the SPB Portal project, we point out that it is possible to mitigate conflicts experienced in the development environment and to conciliate governmental and academy cultures. -The SPB portal integrates more than 10 FOSS tools and provides several features, +The SPB portal integrates more than 10 FLOSS tools and provides several features, such as social network, mailing list, version control, content management and source code quality monitoring. Concerned with the platform susteinability and -maintainabilty, the aforementioned 10 FOSS tools were integrated with minimum +maintainabilty, the aforementioned 10 FLOSS tools were integrated with minimum differences from their official versions and the new developed features were sent upstream to ensure an alignment between the portal systems and their respective official versions. In the integration process, the main softwares @@ -36,7 +36,7 @@ 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 to develop software to +to conciliate agile methodologies and FLOSS practices to develop software to governmental organizations with functional hierarchical structures that use traditional development paradigm. 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 governmental agents another way to interact with the FLOSS community and the university. -\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 FOSS and Agile practices have impacted the students and the +how the used FLOSS and Agile practices have impacted the students and the governmental development process. For this, we would conduce a \textit{postmortem} analysis using the project open data and a survey targeting the involved actors. @@ -61,7 +59,7 @@ documentation, including detailed architecture and operation manuals are also available\footnote{\url{https://softwarepublico.gov.br/doc/} (in Portuguese only at the moment)}. % -All the integrated tools are FOSS and our contributions were published +All the integrated tools are FLOSS and our contributions were published in open repositories, available on the SPB Portal itself. We also contributed these features back to the respective communities, which benefits both those communities and us, since we can share future -- libgit2 0.21.2