Commit 2633e87b87f3a46c3ed42ae85363aa3449c3c379
1 parent
303f7df2
Exists in
master
and in
3 other branches
Added corrections and image
Showing
3 changed files
with
38 additions
and
8 deletions
Show diff stats
opensym2017/content/04-process.tex
@@ -82,7 +82,14 @@ We defined some level of meeting granularity to avoid to generate overheads to | @@ -82,7 +82,14 @@ We defined some level of meeting granularity to avoid to generate overheads to | ||
82 | the developers. We had a strategical and validating meeting with MPOG (the | 82 | the developers. We had a strategical and validating meeting with MPOG (the |
83 | former once in a month and the latter each 15th day), release plaining with the | 83 | former once in a month and the latter each 15th day), release plaining with the |
84 | entire team (one per month), and finally a sprint planning (one each 15th day). | 84 | entire team (one per month), and finally a sprint planning (one each 15th day). |
85 | -Figure X is a diagram that represents our meeting organization. | 85 | +Figure \ref{fig:meeting} is a diagram that represents our meeting organization. |
86 | + | ||
87 | +\begin{figure}[hbt] | ||
88 | + \centering | ||
89 | + \includegraphics[width=\linewidth]{figures/meeting_flows.png} | ||
90 | + \caption{Meetings cycles} | ||
91 | + \label{fig:meeting} | ||
92 | +\end{figure} | ||
86 | 93 | ||
87 | In the strategical meeting we usually defined the priorities and new features | 94 | In the strategical meeting we usually defined the priorities and new features |
88 | with MPOG (we always had to negotiate next steps with them). Normally the | 95 | with MPOG (we always had to negotiate next steps with them). Normally the |
@@ -124,3 +131,27 @@ Notice that this workflow gave to us and to the MPOG a full traceability from | @@ -124,3 +131,27 @@ Notice that this workflow gave to us and to the MPOG a full traceability from | ||
124 | high view of the feature to the low view (code). This provided a way to MPOG | 131 | high view of the feature to the low view (code). This provided a way to MPOG |
125 | validated all worked done and proof the concept that work with open source | 132 | validated all worked done and proof the concept that work with open source |
126 | project can give a proper view to them check. | 133 | project can give a proper view to them check. |
134 | + | ||
135 | +\subsection{Tools for communication and management} | ||
136 | + | ||
137 | +Our team had many people worked together, and most of the seniors worked in a | ||
138 | +different city remotely. Also, we tried to keep our work completely clear to | ||
139 | +the Brazilian government and citizens interested in follow the project. To | ||
140 | +handle those cases, we used a set of tools to communication and other to manage | ||
141 | +the project. | ||
142 | + | ||
143 | +For communication between member in different places, we used: google-talk with | ||
144 | +tmate, IRC, and mailing-list. When one student had to work in pair with a | ||
145 | +senior, normally, they used google-hangout for communication and they shared a | ||
146 | +session with tmate which allow them to share the same terminal. For questions | ||
147 | +and fast discussion, we used IRC. For general notification, we used the | ||
148 | +mailing-list. | ||
149 | + | ||
150 | +For managing the project we used the SPB Portal to validate it by ourselves and | ||
151 | +because it had all the required tools. We basically create one wiki page per | ||
152 | +release in Gitlab, one milestone per sprint, and one or more issues for address | ||
153 | +one user history. With this approach we achieve two important things: keep all | ||
154 | +the management close to the source code and tracked every feature developed by | ||
155 | +the project. | ||
156 | + | ||
157 | +% Ainda falta adicionar a parte da visita dos seniors e o turno sagrado |
opensym2017/content/05-architecture.tex
@@ -2,7 +2,7 @@ | @@ -2,7 +2,7 @@ | ||
2 | \label{sec:architecture} | 2 | \label{sec:architecture} |
3 | 3 | ||
4 | At the point of view of the architecture, two main requirements was brought by | 4 | At the point of view of the architecture, two main requirements was brought by |
5 | -the Brazilian Federal Government for the new platform were: | 5 | +the Brazilian Federal Government for the new platform: |
6 | 6 | ||
7 | \begin{enumerate} | 7 | \begin{enumerate} |
8 | \item \textit{Integrate existing FOSS systems}, with minimal differences from | 8 | \item \textit{Integrate existing FOSS systems}, with minimal differences from |
@@ -81,7 +81,11 @@ functionality of each application, a search in the SPB portal might | @@ -81,7 +81,11 @@ functionality of each application, a search in the SPB portal might | ||
81 | return content from any of the applications, be it web pages, mailing | 81 | return content from any of the applications, be it web pages, mailing |
82 | list posts, or source code. | 82 | list posts, or source code. |
83 | 83 | ||
84 | -%TODO: deixar coeso daqui para baixo | 84 | +% Falar do devops |
85 | +\subsection{Deploy} | ||
86 | + | ||
87 | +The SPB platform was deployed in 7 virtual machines with different functions, | ||
88 | +as we can see in Figure \ref{fig:architecture2}. | ||
85 | 89 | ||
86 | \begin{figure*}[hbt] | 90 | \begin{figure*}[hbt] |
87 | \centering | 91 | \centering |
@@ -90,11 +94,6 @@ list posts, or source code. | @@ -90,11 +94,6 @@ list posts, or source code. | ||
90 | \label{fig:architecture2} | 94 | \label{fig:architecture2} |
91 | \end{figure*} | 95 | \end{figure*} |
92 | 96 | ||
93 | -\subsection{Deploy} | ||
94 | - | ||
95 | -In real, the SPB platform was deployed in 7 virtual machines with different functions, | ||
96 | -as we can see in Figure \ref{fig:architecture2}. | ||
97 | - | ||
98 | The \textit{reverseproxy} handles the HTTP requests and redirects them to the | 97 | The \textit{reverseproxy} handles the HTTP requests and redirects them to the |
99 | \textit{integration}, the \textit{email} sends and receives e-mails on behalf | 98 | \textit{integration}, the \textit{email} sends and receives e-mails on behalf |
100 | of the platform and the \textit{monitor} keeps the entire environment tracked. | 99 | of the platform and the \textit{monitor} keeps the entire environment tracked. |
14.4 KB