@conference { ISI:000392265300025,
	title = {Who Can Help to Review This Piece of Code?},
	booktitle = {COLLABORATION IN A HYPERCONNECTED WORLD},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {480},
	year = {2016},
	note = {17th IFIP WG 5.5 Working Conference on Virtual Enterprises (PRO-VE), Porto, PORTUGAL, OCT 03-05, 2016},
	pages = {289-301},
	publisher = {IFIP WG 5 5 Co Operat Infrastructure Virtual Enterprises \& Elect Business; Soc Collaborat Networks; U Porto; INESCTEC; Univ Amsterdam; Nova Univ Lisbon; UNINOVA},
	organization = {IFIP WG 5 5 Co Operat Infrastructure Virtual Enterprises \& Elect Business; Soc Collaborat Networks; U Porto; INESCTEC; Univ Amsterdam; Nova Univ Lisbon; UNINOVA},
	abstract = {Successful software projects require collaboration between team members. Efficient collaboration relies on both technical and social linkages. In this paper, we investigate whether a socio-technical analysis can support software contributors in identifying experts helping to review their source code. We mined the histories of five open source projects (OSS) from GitHub and examined both technical and socio-technical interactions based on Social Network Analysis (SNA). Mapping communication network to files co-edition network shows the existence of collaboration patterns between core teams and peripherals in the studied OSS projects. Our main contribution is the construction and mapping of three sources of social networks, in which contributors interact by co-editing, commenting or reviewing. We were able to identify behavioral patterns between core teams and peripherals related to the activity of code review. Our findings have implications on improving collaboration between contributors within virtual OSS communities witch drive teams{\textquoteright} performance and software products quality.},
	isbn = {978-3-319-45390-3; 978-3-319-45389-7},
	issn = {1868-4238},
	doi = {10.1007/978-3-319-45390-3\_25},
	author = {Kerzazi, Noureddine and El Asri, Ikram},
	editor = {Afsarmanesh, H and CamarinhaMatos, LM and Soares, AL}
}
@conference { ISI:000382224200013,
	title = {Who Needs Release and DevOps Engineers, and Why?},
	booktitle = {INTERNATIONAL WORKSHOP ON CONTINUOUS SOFTWARE EVOLUTION AND DELIVERY, CSED 2016},
	year = {2016},
	note = {1st International Workshop on Continuous Software Evolution and Delivery (CSED), Austin, TX, MAY 14-15, 2016},
	pages = {77-83},
	publisher = {Assoc Comp Machinery; IEEE Comp Soc; IEEE Tech Council Software Engn; ACM Special Interest Grp Software Engn},
	organization = {Assoc Comp Machinery; IEEE Comp Soc; IEEE Tech Council Software Engn; ACM Special Interest Grp Software Engn},
	abstract = {The recent surge in interest in continuous delivery has opened up the job market for release and DevOps engineers. However, despite an increasing number of conferences and publications on continuous delivery, smaller companies and start-ups still have a hard time determining the core tasks their future release and DevOps engineers should be responsible for (and what the differences between those two roles are), while universities are not sure what essential techniques and skills they should teach to their students. This paper performs an empirical analysis of online job postings to determine and compare the main tasks of release and DevOps engineers, globally and across countries. Our qualitative analysis shows that automation is the most important activity across the three roles, as articulated in job posting description data, and that the release engineer role combines the top activities of the DevOps and more traditional build engineer roles. Finally, different countries have a moderate degree of similarity between their ads, although each country has its specific focus.},
	isbn = {978-1-4503-4157-8},
	doi = {10.1145/2896941.2896957},
	author = {Kerzazi, Noureddine and Adams, Bram}
}
