[opensym] Adding contributions to Mezuro

Paulo Meireles
1 parent 5cef1922
Showing 2 changed files with 20 additions and 3 deletions Show diff stats
opensym2017/content/10-contributions.tex
opensym2017/spb.bib
@@ -41,11 +41,18 @@ migrate to the latest Rails version (web framework used by Noosfero), enable
 the federation implementation (federation with other social networks), and
 decouple the interface and the back-end.
  
+Mezuro was completely rewritten and its architecture evolved adopting the
+microservice architecture\cite{namiot2014micro}. This way, we minimize the
+amount of code to maintain it, helping to test it and grant its code quality.
+In practice, we modularize the Mezuro project in several independent services.
+Currently, its computation and visualization modules use Kalibro and Prezento,
+respectively. They were developed into the Mezuro project and evolved during
+its integration to the new SPB Portal.
+
+
 We also made some contributions on the DevOps front. Some members of
-them team became maintainers of some python libraries that were used by
+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
-
@@ -306,3 +306,13 @@
   biburl    = {http://dblp.uni-trier.de/rec/bib/conf/icse/KalliamvakouDBS15},
   bibsource = {dblp computer science bibliography, http://dblp.org}
 }
+
+@article{namiot2014micro,
+  title={On Micro-services Architecture},
+  author={Namiot, Dmitry and Sneps-Sneppe, Manfred},
+  journal={International Journal of Open Information Technologies},
+  volume={2},
+  number={9},
+  pages={24--27},
+  year={2014}
+}
...	...	@@ -41,11 +41,18 @@ migrate to the latest Rails version (web framework used by Noosfero), enable
41	41	the federation implementation (federation with other social networks), and
42	42	decouple the interface and the back-end.
43	43
	44	+Mezuro was completely rewritten and its architecture evolved adopting the
	45	+microservice architecture\cite{namiot2014micro}. This way, we minimize the
	46	+amount of code to maintain it, helping to test it and grant its code quality.
	47	+In practice, we modularize the Mezuro project in several independent services.
	48	+Currently, its computation and visualization modules use Kalibro and Prezento,
	49	+respectively. They were developed into the Mezuro project and evolved during
	50	+its integration to the new SPB Portal.
	51	+
	52	+
44	53	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
	54	+them team became maintainers of some Python libraries that were used by
46	55	our scripts to upload packages to OBS (Open Build Service). We developed
47	56	a tool called copr-status to keep track of the different stages of the
48	57	lifecycle of each of the individual packages we were working on.
49	58
50		-%TODO: Mezuro
51		-
...	...
...	...	@@ -306,3 +306,13 @@
306	306	biburl = {http://dblp.uni-trier.de/rec/bib/conf/icse/KalliamvakouDBS15},
307	307	bibsource = {dblp computer science bibliography, http://dblp.org}
308	308	}
	309	+
	310	+@article{namiot2014micro,
	311	+ title={On Micro-services Architecture},
	312	+ author={Namiot, Dmitry and Sneps-Sneppe, Manfred},
	313	+ journal={International Journal of Open Information Technologies},
	314	+ volume={2},
	315	+ number={9},
	316	+ pages={24--27},
	317	+ year={2014}
	318	+}
...	...