From 7344b9374b701f98ae5e144904c2758838f7d28a Mon Sep 17 00:00:00 2001 From: Antonio Terceiro Date: Wed, 24 May 2017 15:00:38 -0300 Subject: [PATCH] 08-contributions.tex: reviews --- opensym2017/content/08-contributions.tex | 54 ++++++++++++++++++++++++++++-------------------------- 1 file changed, 28 insertions(+), 26 deletions(-) diff --git a/opensym2017/content/08-contributions.tex b/opensym2017/content/08-contributions.tex index 1436ae9..286e18e 100644 --- a/opensym2017/content/08-contributions.tex +++ b/opensym2017/content/08-contributions.tex @@ -1,4 +1,4 @@ -\section{Contributing with Free Software Communities} +\section{Contributions to the upstream communities} \label{sec:contributions} %- projeto feito do jeito certo com relação ao software livre (contribuições upstream etc) @@ -9,24 +9,30 @@ %* Coper, empacotamentos (obs), omniauth -During the execution of this project we made several contributions from -different levels to the communities we interacted with. This occurred due to -our development process aligned with those of the respective communities. We -used to discuss with upstream the features and bug fixes that we was working -on, this kind of discussion improve the developers' technical solutions and -allowed upstream to accept our contribution more easily. - -In Colab we helped upstream to redesign the entirely architecture, enabling the -development of plugins to integrate new tools. We also added a feature that -allowed Colab to run asynchronous tasks, which was a major improvement for us -since we were developing a complex system. A migration to the latest Django -version was made (web framework used by Colab). Moreover, we worked on RevProxy -(the greatest Colab dependency) to put it in a good shape, fixing many bugs. +During the execution of this project we made several contributions to +the upstream communities we interacted with. This occurred due to our +development process aligned with those of the respective communities. +During development, we would explicitly discuss the features and bug +fixes that we were working on with the applicable upstream communities. +This contributed to improve the developers technical solutions with +expertise outside of our team, and make it easier for those changes to +be accepted in the original projects. Having changes accepted upstream +in turn makes our life easier as it minimizes the delta between our +codebase and upstream's allowing us to upgrade and benefit from +development work from others. + +In Colab, we helped upstream redesign the entirely architecture, +enabling the development of plugins to integrate new tools. We also +added a feature that allowed Colab to run asynchronous tasks, which was +a major improvement for us since we were developing a complex system. A +migration to the latest Django version was made (web framework used by +Colab). Moreover, we worked on RevProxy (the more important dependency +of Colab) to put it in a good shape, fixing many bugs. Gitlab was the tool that we made the least number of modifications. We -contributed with some improvements related with configuration files and we -developed a new omniauth plugin, which enables the user authentication in -Gitlab via REMOTE\_USER HTTP header. This omniauth plugin was needed because +contributed with some improvements related with configuration files and +we developed a new plugin that enables user authentication in Gitlab +through the REMOTE\_USER HTTP header. This plugin was needed because Colab uses this mechanism to manage the authentication. Noosfero was the tool that contemplated several functional requirements, @@ -35,15 +41,11 @@ migrate to the latest Rails version (web framework used by Noosfero), enable the federation implementation (federation with other social networks), decouple the interface and the back-end, and so forth. -We also contributed with some DevOps tools as well during the project. Some -member of our team took the maintenance of some python libraries that we used -to support our scripts to upload our packages to OBS (Open Build Service). -Since we were composed by many teams with large number of developers we had -some problems related with the tracking of our per team/software releases, the -DevOps team did not know when was the right time to package that software or -not. Thus we developed a tool called copr-status to keep tracked the version -packaged and the version finished by the developers, basically this is a web -interface that helps you to visualize the status of that package/software. +We also made some contributions on the DevOps front. Some members of +them team became maintainers of some python libraries that were used by +our scripts to upload packages to OBS (Open Build Service). We developed +a tool called copr-status to keep track of the different stages of the +lifecycle of each of the individual packages we were working on. %TODO: Mezuro -- libgit2 0.21.2