Download as
Browse Code »

Commit 38934816d5cb6db3c5648c0b5841af7e051a35d0

Authored by Hilmer Rodrigues Neri
2 parents cacd32ca 20ef58bc
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

Merge from my work in section 2 with 20ef58bc97f202e9b47f631abe87bdeed6912ce9 commit

Showing 3 changed files with 13 additions and 26 deletions   Show diff stats
opensym2017/content/01-introduction.tex
  Diff comments   View file @3893481
... ... @@ -16,7 +16,7 @@ acquisition of a proprietary solution must be explicitly justified by
16 16 demonstrating that there is no suitable option in the SPB Portal.
17 17  
18 18 Since 2009, however, the SPB Portal was having several technical issues.
19   -The original codebase was not being developed anymore, and there as a
  19 +The original codebase was not being developed anymore, and there was a
20 20 large amount of technical debt to overcome. The system was a modified
21 21 version of an existing FOSS platform that was not being developed
22 22 anymore, and the portal maintenance was becoming harder and harder.
... ... @@ -32,7 +32,7 @@ this paper, we present an overview of this new generation of the SPB
32 32 Portal.
33 33  
34 34 The project was developed by a team of 3 professors, 6 professionals, 2
35   -masters students, and approximately 40 undergrad students (not all of
  35 +masters students, and approximately 40 undergraduate students (not all of
36 36 them at the same time, though -- graduations and other events triggered
37 37 changes in the team).
38 38  
... ...
opensym2017/content/04-process.tex
  Diff comments   View file @3893481
1 1 \section{Development Organization and Process}
2 2 \label{sec:process}
3 3  
4   -The SPB members were composed of a variety of professionals with different
5   -levels and skills. Most of them were undergraduate students with major in
6   -software engineering (from 4th semester or upper), hence they could not
7   -dedicate many hours in the project per week. In their daily lives in the
8   -project, they had programming and devops tasks. It is important to highlight
9   -that the students always had the flexibility to negotiate their work hours
10   -during the semester, because we tried to not cause any damage to their grades.
11   -
12   -The development of SPB project required a vast experience and background that
13   -usually undergraduate students do not have yet, for this reason, some senior
14   -developer joined to the project to help with hard issues and to transfer
15   -knowledge to the students. Their main tasks provide solutions for hard
16   -problems, in other words, they worked as a developer. All the senior lived in a
17   -different states spread around Brazil, and all the communication was made via
18   -internet. Finally, those professionals are very skilful and the project could
19   -not afford a full time work for them, as a result, some of them worked
20   -partially on the project.
  4 +The SPB team was composed of a variety of professionals with different levels and skills, where most of them were undergraduate students with major in software engineering (from 4th semester or upper).
  5 +Since the students could not dedicate many hours per week to the project, they always had the flexibility to negotiate their work schedule during the semester in order not to cause any damage to their grades. Their daily work routine in the project included programming and devops tasks.
  6 +
  7 +The development of SPB project required a vast experience and background that usually undergraduate students do not have yet. For this reason, some senior developers have joined to the project to help with hard issues and to transfer knowledge to the students. Their main task was to provide solutions for complex problems, in other words, they worked as a developer. As these professionals are very skillful and the project could not fund a full time work for them, some of them worked partially on the project. In addition, they lived in a different states spread around Brazil which led much of the communication to be made via Internet.
21 8  
22 9 Finally, the last group of actors of this project was composed of employees
23 10 formally working for the Brazilian Government, in the Ministery of Planning,
... ...
opensym2017/content/08-contributions.tex
  Diff comments   View file @3893481
1 1 \section{Contributing with Free Software Communities}
2 2 \label{sec:contributions}
3 3  
4   -- projeto feito do jeito certo com relação ao software livre (contribuições upstream etc)
5   -* Colab -> RevProxy
6   -* Colab, atualização do python/django
7   -* Contribuições para o GitLab (autenticação)
8   -* Noosfero, atualização do Rails, preparação para federação, nova interface ...
9   -* Coper, empacotamentos (obs), omniauth
  4 +%- projeto feito do jeito certo com relação ao software livre (contribuições upstream etc)
  5 +%* Colab -> RevProxy
  6 +%* Colab, atualização do python/django
  7 +%* Contribuições para o GitLab (autenticação)
  8 +%* Noosfero, atualização do Rails, preparação para federação, nova interface ...
  9 +%* Coper, empacotamentos (obs), omniauth
10 10  
11 11  
12 12 During the execution of this project we made several contributions from
... ... @@ -33,7 +33,7 @@ Noosfero was the tool that contemplated several functional requirements,
33 33 therefore we made a large number of contributions with upstream. We helped to
34 34 migrate to the latest Rails version (web framework used by Noosfero), enable
35 35 the federation implementation (federation with other social networks), decouple
36   -the interface and the back-end, and so fourth.
  36 +the interface and the back-end, and so forth.
37 37  
38 38 We also contributed with some DevOps tools as well during the project. Some
39 39 member of our team took the maintenance of some python libraries that we used
... ...