Commit 7411b512810540f2636050f1bf4788a85526d3ce
1 parent
2f169f57
Exists in
master
and in
3 other branches
draft of contributions
Showing
1 changed file
with
37 additions
and
0 deletions
Show diff stats
opensym2017/content/08-contributions.tex
@@ -7,3 +7,40 @@ | @@ -7,3 +7,40 @@ | ||
7 | * Contribuições para o GitLab (autenticação) | 7 | * Contribuições para o GitLab (autenticação) |
8 | * Noosfero, atualização do Rails, preparação para federação, nova interface ... | 8 | * Noosfero, atualização do Rails, preparação para federação, nova interface ... |
9 | * Coper, empacotamentos (obs), omniauth | 9 | * Coper, empacotamentos (obs), omniauth |
10 | + | ||
11 | + | ||
12 | +During the execution of this project we made several contributions from | ||
13 | +different levels to the communities we interacted with. This occurred due to | ||
14 | +our development process aligned with those of the respective communities. We | ||
15 | +used to discuss with upstream the features and bug fixes that we was working | ||
16 | +on, this kind of discussion improve the developers' technical solutions and | ||
17 | +allowed upstream to accept our contribution more easily. | ||
18 | + | ||
19 | +In Colab we helped upstream to redesign the entirely architecture, enabling the | ||
20 | +development of plugins to integrate new tools. We also added a feature that | ||
21 | +allowed Colab to run asynchronous tasks, which was a major improvement for us | ||
22 | +since we were developing a complex system. A migration to the latest Django | ||
23 | +version was made (web framework used by Colab). Moreover, we worked on RevProxy | ||
24 | +(the greatest Colab dependency) to put it in a good shape, fixing many bugs. | ||
25 | + | ||
26 | +Gitlab was the tool that we made the least number of modifications. We | ||
27 | +contributed with some improvements related with configuration files and we | ||
28 | +developed a new omniauth plugin, which enables the user authentication in | ||
29 | +Gitlab via remote\_user HTTP header. This omniauth plugin was needed because | ||
30 | +Colab uses this mechanism to manage the authentication. | ||
31 | + | ||
32 | +Noosfero was the tool that contemplated several functional requirements, | ||
33 | +therefore we made a large number of contributions with upstream. We helped to | ||
34 | +migrate to the latest Rails version (web framework used by Noosfero), enable | ||
35 | +the federation implementation (federation with other social networks), decouple | ||
36 | +the interface and the back-end, and so fourth. | ||
37 | + | ||
38 | +We also contributed with some DevOps tools as well during the project. Some | ||
39 | +member of our team took the maintenance of some python libraries that we used | ||
40 | +to support our scripts to upload our packages to OBS (Open Build Service). | ||
41 | +Since we were composed by many teams with large number of developers we had | ||
42 | +some problems related with the tracking of our per team/software releases, the | ||
43 | +DevOps team did not know when was the right time to package that software or | ||
44 | +not. Thus we developed a tool called copr-status to keep tracked the version | ||
45 | +packaged and the version finished by the developers, basically this is a web | ||
46 | +interface that helps you to visualize the status of that package/software. |