Jesus M. Gonzalez Barahona

Jesus M. Gonzalez Barahona

Auto-generated profile, based on publicly available information

Jesus M. Gonzalez Barahona

Universidad Rey Juan Carlos, Madrid, Spain

Research Focus & Metrics

Academic Career Length

30Years (1997-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
1 January 2008
Verified
Conference Paper
Closed access
FOFelipe Ortega
Felipe Ortega
JGJesus M. Gonzalez-Barahona
Jesus M. Gonzalez-Barahona
GRGregorio Robles
Gregorio Robles
Wikipedia is one of the most successful examples of massive collaborative content development. However, many of the mechanisms and procedures that it uses are still unknown in detail. For instance, how equal (or unequal) are the contributions to it has been discussed in the last years, with no conclusive results. In this paper, we study exactly that aspect by using Lorenz curves and Gini coefficients, very well known instruments to economists. We analyze the trends in the inequality of distributions for the ten biggest language editions of Wikipedia, and their evolution over time. As a result, we have found large differences in the number of contributions by different authors (something also observed in free, open source software development), and a trend to stable patterns of inequality in the long run.

18 October 2011 in Empirical Software Engineering
Verified
Journal Article
Open access
PDF file
JGJesús M. González-Barahona
Jesús M. González-Barahona
GRGregorio Robles
Gregorio Robles
Among empirical software engineering studies, those based on data retrieved from development repositories (such as those of source code management, issue tracking or communication systems) are specially suitable for reproduction. However their reproducibility status can vary a lot, from easy to almost impossible to reproduce. This paper explores which elements can be considered to characterize the reproducibility of a study in this area, and how they can be analyzed to better understand the type of reproduction studies they enable or obstruct. One of the main results of this exploration is the need of a systematic approach to asses the reproducibility of a study, due to the complexity of the processes usually involved, and the many details to be taken into account. To address this need, a methodology for assessing the reproducibility of studies is also presented and discussed, as a tool to help to raise awareness about research reproducibility in this field. The application of the methodology in practice has shown how, even for papers aimed to be reproducible, a systematic analysis raises important aspects that render reproduction difficult or impossible. We also show how, by identifying elements and attributes related to reproducibility, it can be better understood which kind of reproduction can be done for a specific study, given the description of datasets, methodologies and parameters it uses.

1 July 2018 in Information and Software Technology
Verified
Journal Article
Closed access
GRGema Rodríguez-Pérez
Gema Rodríguez-Pérez
GRGregorio Robles
Gregorio Robles
JGJesús M. González-Barahona
Jesús M. González-Barahona

17 April 2018
Verified
Book Chapter
Open access
PDF file
AZAhmed Zerouali
Ahmed Zerouali
ECEleni Constantinou
Eleni Constantinou
TMTom Mens
Tom Mens
GRGregorio Robles
Gregorio Robles
JGJesús González-Barahona
Jesús González-Barahona
Software library packages are constantly evolving and increasing in number. Not updating to the latest available release of dependent libraries may negatively affect software development by not benefiting from new functionality, vulnerability and bug fixes available in more recent versions. On the other hand, automatically updating to the latest release may introduce incompatibility issues. We introduce a technical lag metric for dependencies in package networks, in order to assess how outdated a software package is compared to the latest available releases of its dependencies. We empirically analyse the package update practices and technical lag for the npm distribution of JavaScript packages. Our results show a strong presence of technical lag caused by the specific use of dependency constraints, indicating a reluctance to update dependencies to avoid backward incompatible changes.

29 November 2008 in Empirical Software Engineering
Verified
Journal Article
Open access
PDF file
JGJesus M. Gonzalez-Barahona
Jesus M. Gonzalez-Barahona
GRGregorio Robles
Gregorio Robles
MMMartin Michlmayr
Martin Michlmayr
JAJuan José Amor
Juan José Amor
DGDaniel M. German
Daniel M. German
Software evolution studies have traditionally focused on individual products. In this study we scale up the idea of software evolution by considering software compilations composed of a large quantity of independently developed products, engineered to work together. With the success of libre (free, open source) software, these compilations have become common in the form of ‘software distributions’, which group hundreds or thousands of software applications and libraries into an integrated system. We have performed an exploratory case study on one of them, Debian GNU/Linux, finding some significant results. First, Debian has been doubling in size every 2 years, totalling about 300 million lines of code as of 2007. Second, the mean size of packages has remained stable over time. Third, the number of dependencies between packages has been growing quickly. Finally, while C is still by far the most commonly used programming language for applications, use of the C++, Java, and Python languages have all significantly increased. The study helps not only to understand the evolution of Debian, but also yields insights into the evolution of mature libre software systems in general.

1 February 2019
Verified
Conference Paper
Closed access
AZAhmed Zerouali
Ahmed Zerouali
TMTom Mens
Tom Mens
GRGregorio Robles
Gregorio Robles
JGJesus M. Gonzalez-Barahona
Jesus M. Gonzalez-Barahona
Packaging software into containers is becoming a common practice when deploying services in cloud and other environments. Docker images are one of the most popular container technologies for building and deploying containers. A container image usually includes a collection of software packages, that can have bugs and security vulnerabilities that affect the container health. Our goal is to support container deployers by analysing the relation between outdated containers and vulnerable and buggy packages installed in them. We use the concept of technical lag of a container as the difference between a given container and the most up-to-date container that is possible with the most recent releases of the same collection of packages. For 7,380 official and community Docker images that are based on the Debian Linux distribution, we identify which software packages are installed in them and measure their technical lag in terms of version updates, security vulnerabilities and bugs. We have found, among others, that no release is devoid of vulnerabilities, so deployers cannot avoid vulnerabilities even if they deploy the most recent packages. We offer some lessons learned for container developers in regard to the strategies they can follow to minimize the number of vulnerabilities. We argue that Docker container scan and security management tools should improve their platforms by adding data about other kinds of bugs and include the measurement of technical lag to offer deployers information of when to update.