Commit ea0af73cec1744c90515f07d3dd8c561c5c06a26

Authored by Rodrigo Siqueira de Melo
1 parent a8138db4

Pequenos ajustes

closes #11
closes #9
closes #12
opensym2017/content/02-spb.tex
1 \section{Background} 1 \section{Background}
2 \label{sec:spb} 2 \label{sec:spb}
3 3
4 -FOSS is a phenomenon that has gained notoriety in recent years and has been  
5 -attracting the interest of academia. However, since the beginning of computing  
6 -the majority of developers worked in the way that we now identify as free  
7 -software, that is, sharing code openly. This openness makes the code available  
8 -for inspection, modification, and use by any person or organization  
9 -\cite{hippel2003,kon2012}. 4 +Since the beginning of computing the majority of developers worked in the way
  5 +that we now identify as free software, that is, sharing code openly. This
  6 +openness makes the code available for inspection, modification, and use by any
  7 +person or organization \cite{hippel2003,kon2012}.
10 8
11 The elements that distinguish FOSS from other types of software are the 9 The elements that distinguish FOSS from other types of software are the
12 reasoning about the development process, the economic context, the relationship 10 reasoning about the development process, the economic context, the relationship
opensym2017/content/07-process.tex
@@ -92,13 +92,12 @@ the Brazilian government and citizens interested in following the project. To @@ -92,13 +92,12 @@ the Brazilian government and citizens interested in following the project. To
92 handle those cases, we used a set of tools to communication and other to manage 92 handle those cases, we used a set of tools to communication and other to manage
93 the project. 93 the project.
94 94
95 -For communication between member in different places, we used: Google  
96 -handouts with tmate tool, IRC, and mailing lists. When one student had to  
97 -work in pair with a senior, normally, they used Google hangout for  
98 -communication and they shared a terminal session with tmate which allow  
99 -them to share the same terminal, with both typing and seeing the screen.  
100 -For questions and fast discussion, we used IRC. For general  
101 -notification, we used the mailing lists. 95 +For communication between members in different places, we used: video
  96 +conferencing with shared terminal tools, IRC, and mailing lists. For example,
  97 +when one student had to work in pair with a senior, normally, they used video
  98 +conferencing tool for talking and shared a terminal session (both typing and
  99 +seeing the screen in real time). For questions and fast discussion, we used
  100 +IRC. For general notification, we used the mailing lists.
102 101
103 For managing the project we used the SPB Portal itself; first to validate it by 102 For managing the project we used the SPB Portal itself; first to validate it by
104 ourselves, and also because it had all the required tools. We basically created 103 ourselves, and also because it had all the required tools. We basically created
opensym2017/content/08-contributions.tex
@@ -38,8 +38,8 @@ Colab uses this mechanism to manage the authentication. @@ -38,8 +38,8 @@ Colab uses this mechanism to manage the authentication.
38 Noosfero was the tool that contemplated several functional requirements, 38 Noosfero was the tool that contemplated several functional requirements,
39 therefore we made a large number of contributions with upstream. We helped to 39 therefore we made a large number of contributions with upstream. We helped to
40 migrate to the latest Rails version (web framework used by Noosfero), enable 40 migrate to the latest Rails version (web framework used by Noosfero), enable
41 -the federation implementation (federation with other social networks), decouple  
42 -the interface and the back-end, and so forth. 41 +the federation implementation (federation with other social networks), and
  42 +decouple the interface and the back-end.
43 43
44 We also made some contributions on the DevOps front. Some members of 44 We also made some contributions on the DevOps front. Some members of
45 them team became maintainers of some python libraries that were used by 45 them team became maintainers of some python libraries that were used by