[opensym] removing pt-br references and fixing bibtex file

Paulo Meireles
1 parent 381a8210
Showing 3 changed files with 74 additions and 48 deletions Show diff stats
opensym2017/content/02-spb.tex
opensym2017/content/04-researchdesign.tex
opensym2017/spb.bib
@@ -4,27 +4,27 @@
 Since the beginning of computing the majority of developers worked in the way
 that we now identify as free software, that is, sharing code openly. This
 openness makes the code available for inspection, modification, and use by any
-person or organization \cite{hippel2003,kon2012}.
+person or organization \cite{hippel2003,kon2011}.
 The elements that distinguish FLOSS from other types of software are the
 reasoning about the development process, the economic context, the relationship
 between developers and users, as well as the ethical and legal characteristics
 that relate to the software. In the context of FLOSS, user freedom is promoted
 and its development is based on open collaboration and development practices
-\cite{meirelles2013}.
+\cite{kon2011}.
 From the economic point of view, unlike what happens with proprietary software,
 FLOSS promotes the establishment of several suppliers that can compete with
 each other based on the same software. This stronger competition among
 suppliers brings benefits to users because it gives better assurances regarding
-the evolution of the system and induces a reduction in prices \cite{kon2012}.
+the evolution of the system and induces a reduction in prices \cite{kon2011}.
 These freedoms and assurances on software are guaranteed in Brazil by Law
 9610/98 (copyright law).  Most of the time, this protection from the law
 complies with the terms conferred by a contract related to certain software.
 This contract is called ``license''. A software license determines a list of
 rights that are given to, and duties that are imposed on a user of the
 software. In particular, what differentiates FLOSS from proprietary software is
-just the way they are licensed \cite{sabino2009}. The FLOSS licenses guarantee
+just the way they are licensed \cite{kon2011}. The FLOSS licenses guarantee
 the right to execute, study, adapt, and improve the software. Example of common
 FLOSS licenses  are the \textit{GPL (GNU General Public License)}, the Apache
 license, the MIT license, and the BSD license.
 \section{Challenging Questions}
 \label{sec:researchdesign}
-In this paper, we aims to share our experience designing and developing the new
+In this paper, we aim to share our experience designing and developing the new
 SPB Portal by reporting, alongside the technical efforts carried out, our
 empirical work process and the lessons learned. In the begins of the new SPB
 Portal project, we had in mind 3 main challenges to overcome, as explained in
@@ -8,7 +8,7 @@
 }
 @inproceedings{kon2011,
-  author = {Kon, Fabio and Meirelles, Paulo and Lago, Nelson and de Azevedo Terceiro, Antonio Soares and Chavez, Christina and Mendonça, Manoel G.},
+  author = {Kon, Fabio and Meirelles, Paulo and Lago, Nelson and Terceiro, Antonio and Chavez, Christina and Mendonça, Manoel},
   booktitle = {SBES},
   ee = {http://doi.ieeecomputersociety.org/10.1109/SBES.2011.19},
   interhash = {cb27e5a1aa6816e36e92a1d3b9011615},
@@ -96,18 +96,18 @@
 }
 @article{ducheneaut2005,
-  author = {Ducheneaut, N.},
-  date-added = {2008-01-20 20:37:12 -0800},
-  date-modified = {2008-01-20 20:37:12 -0800},
-  interhash = {8cfe59af50070854ba2a8383ad75d492},
-  intrahash = {8a17826d55e41bcc35851ee8493f0b66},
-  journal = {Computer Supported Cooperative Work (CSCW)},
-  number = {4},
-  pages = {323--368},
-  publisher = {Springer},
-  title = {{Socialization in an Open Source Software Community: A Socio-Technical Analysis}},
-  volume = {14},
-  year = {2005}
+  author    = {Nicolas Ducheneaut},
+  title     = {Socialization in an Open Source Software Community: {A} Socio-Technical Analysis},
+  journal   = {Computer Supported Cooperative Work},
+  volume    = {14},
+  number    = {4},
+  pages     = {323--368},
+  year      = {2005},
+  url       = {https://doi.org/10.1007/s10606-005-9000-1},
+  doi       = {10.1007/s10606-005-9000-1},
+  timestamp = {Sun, 28 May 2017 13:18:01 +0200},
+  biburl    = {http://dblp.uni-trier.de/rec/bib/journals/cscw/Ducheneaut05},
+  bibsource = {dblp computer science bibliography, http://dblp.org}
 }
 @article{fagerholm2013,
@@ -179,12 +179,17 @@
 }
 @article{bobr2003,
-  author = {Booch, Grady and Brown, Alan W.},
-  journal = {Advances in Computers},
-  pages = {?},
-  title = {Collaborative Development Environments},
-  volume = {59},
-  year = {2003}
+  author    = {Grady Booch and Alan W. Brown},
+  title     = {Collaborative Development Environments},
+  journal   = {Advances in Computers},
+  volume    = {59},
+  pages     = {1--27},
+  year      = {2003},
+  url       = {https://doi.org/10.1016/S0065-2458(03)59001-5},
+  doi       = {10.1016/S0065-2458(03)59001-5},
+  timestamp = {Sat, 20 May 2017 00:22:37 +0200},
+  biburl    = {http://dblp.uni-trier.de/rec/bib/journals/ac/BoochB03},
+  bibsource = {dblp computer science bibliography, http://dblp.org}
 }
 @inproceedings{chao2007student,
@@ -234,31 +239,42 @@
   year = {2008}
 }
-
 @book{refactoring,
-  title={Refactoring for software design smells: Managing technical debt},
-  author={Suryanarayana, Girish and Samarthyam, Ganesh and Sharma, Tushar},
-  year={2014},
-  publisher={Morgan Kaufmann}
-}
+ author = {Suryanarayana, Girish and Samarthyam, Ganesh and Sharma, Tushar},
+ title = {Refactoring for Software Design Smells: Managing Technical Debt},
+ year = {2014},
+ isbn = {0128013974, 9780128013977},
+ edition = {1st},
+ publisher = {Morgan Kaufmann Publishers Inc.},
+ address = {San Francisco, CA, USA},
+} 
-@article{mezuro_oss,
+@inproceedings{mezuro_oss,
   title={Mezuro: Understanding source code metrics},
-  author={Guedes and Meirelles and  Manzo and Camarinha},
-  journal={International Conference on Open Source Systems},
-  volume={01},
+  author={Guedes, Dylan and Meirelles, Paulo and  Manzo, Rafael and Camarinha, Diego},
+  booktitle={Poster Proceedings of the 13th International Conference on Open Source Systems},
+  pages={15--18},
   year={2017},
-  publisher={OSS}
+  url = {http://oss2017.lifia.info.unlp.edu.ar/blog/wp-content/uploads/2017/03/PosterProceedings.rar},
+  organization={OSS Conference}
 }
 @article{collaboration_tools,
-  title={Collaboration tools for global software engineering},
-  author={Lanubile, Filippo and Ebert, Christof and Prikladnicki, Rafael and Vizca{\'\i}no, Aurora},
-  journal={IEEE software},
-  volume={27},
-  number={2},
-  year={2010},
-  publisher={IEEE}
+  author    = {Filippo Lanubile and
+               Christof Ebert and
+               Rafael Prikladnicki and
+               Aurora Vizca{\'{\i}}no},
+  title     = {Collaboration Tools for Global Software Engineering},
+  journal   = {{IEEE} Software},
+  volume    = {27},
+  number    = {2},
+  pages     = {52--55},
+  year      = {2010},
+  url       = {https://doi.org/10.1109/MS.2010.39},
+  doi       = {10.1109/MS.2010.39},
+  timestamp = {Thu, 08 Jun 2017 09:06:58 +0200},
+  biburl    = {http://dblp.uni-trier.de/rec/bib/journals/software/LanubileEPV10},
+  bibsource = {dblp computer science bibliography, http://dblp.org}
 }
 @article{parker2007wiki,
@@ -273,10 +289,20 @@
 }
 @inproceedings{opensourcestyle,
-  title={Open source-style collaborative development practices in commercial projects using github},
-  author={Kalliamvakou, Eirini and Damian, Daniela and Blincoe, Kelly and Singer, Leif and German, Daniel M},
-  booktitle={Proceedings of the 37th International Conference on Software Engineering-Volume 1},
-  pages={574--585},
-  year={2015},
-  organization={IEEE Press}
+  author    = {Eirini Kalliamvakou and
+               Daniela E. Damian and
+               Kelly Blincoe and
+               Leif Singer and
+               Daniel M. Germ{\'{a}}n},
+  title     = {Open Source-Style Collaborative Development Practices in Commercial
+               Projects Using GitHub},
+  booktitle = {37th {IEEE/ACM} International Conference on Software Engineering,
+               {ICSE} 2015, Florence, Italy, May 16-24, 2015, Volume 1},
+  pages     = {574--585},
+  year      = {2015},
+  url       = {https://doi.org/10.1109/ICSE.2015.74},
+  doi       = {10.1109/ICSE.2015.74},
+  timestamp = {Sun, 04 Jun 2017 01:00:00 +0200},
+  biburl    = {http://dblp.uni-trier.de/rec/bib/conf/icse/KalliamvakouDBS15},
+  bibsource = {dblp computer science bibliography, http://dblp.org}
 }
	@@ -4,27 +4,27 @@		@@ -4,27 +4,27 @@
4	Since the beginning of computing the majority of developers worked in the way	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	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	6	openness makes the code available for inspection, modification, and use by any
7	-person or organization \cite{hippel2003,kon2012}.	7	+person or organization \cite{hippel2003,kon2011}.
8		8
9	The elements that distinguish FLOSS from other types of software are the	9	The elements that distinguish FLOSS from other types of software are the
10	reasoning about the development process, the economic context, the relationship	10	reasoning about the development process, the economic context, the relationship
11	between developers and users, as well as the ethical and legal characteristics	11	between developers and users, as well as the ethical and legal characteristics
12	that relate to the software. In the context of FLOSS, user freedom is promoted	12	that relate to the software. In the context of FLOSS, user freedom is promoted
13	and its development is based on open collaboration and development practices	13	and its development is based on open collaboration and development practices
14	-\cite{meirelles2013}.	14	+\cite{kon2011}.
15		15
16	From the economic point of view, unlike what happens with proprietary software,	16	From the economic point of view, unlike what happens with proprietary software,
17	FLOSS promotes the establishment of several suppliers that can compete with	17	FLOSS promotes the establishment of several suppliers that can compete with
18	each other based on the same software. This stronger competition among	18	each other based on the same software. This stronger competition among
19	suppliers brings benefits to users because it gives better assurances regarding	19	suppliers brings benefits to users because it gives better assurances regarding
20	-the evolution of the system and induces a reduction in prices \cite{kon2012}.	20	+the evolution of the system and induces a reduction in prices \cite{kon2011}.
21	These freedoms and assurances on software are guaranteed in Brazil by Law	21	These freedoms and assurances on software are guaranteed in Brazil by Law
22	9610/98 (copyright law). Most of the time, this protection from the law	22	9610/98 (copyright law). Most of the time, this protection from the law
23	complies with the terms conferred by a contract related to certain software.	23	complies with the terms conferred by a contract related to certain software.
24	This contract is called ``license''. A software license determines a list of	24	This contract is called ``license''. A software license determines a list of
25	rights that are given to, and duties that are imposed on a user of the	25	rights that are given to, and duties that are imposed on a user of the
26	software. In particular, what differentiates FLOSS from proprietary software is	26	software. In particular, what differentiates FLOSS from proprietary software is
27	-just the way they are licensed \cite{sabino2009}. The FLOSS licenses guarantee	27	+just the way they are licensed \cite{kon2011}. The FLOSS licenses guarantee
28	the right to execute, study, adapt, and improve the software. Example of common	28	the right to execute, study, adapt, and improve the software. Example of common
29	FLOSS licenses are the \textit{GPL (GNU General Public License)}, the Apache	29	FLOSS licenses are the \textit{GPL (GNU General Public License)}, the Apache
30	license, the MIT license, and the BSD license.	30	license, the MIT license, and the BSD license.
1	\section{Challenging Questions}	1	\section{Challenging Questions}
2	\label{sec:researchdesign}	2	\label{sec:researchdesign}
3		3
4	-In this paper, we aims to share our experience designing and developing the new	4	+In this paper, we aim to share our experience designing and developing the new
5	SPB Portal by reporting, alongside the technical efforts carried out, our	5	SPB Portal by reporting, alongside the technical efforts carried out, our
6	empirical work process and the lessons learned. In the begins of the new SPB	6	empirical work process and the lessons learned. In the begins of the new SPB
7	Portal project, we had in mind 3 main challenges to overcome, as explained in	7	Portal project, we had in mind 3 main challenges to overcome, as explained in