%0 Conference Proceedings %B MSR '15: Proceedings of the 2015 International Working Conference on Mining Software Repositories %D 2015 %T Generating the Blueprints of the Java Ecosystem %A Vassilios Karakoidas %A Mitropoulos, Dimitris %A Louridas, Panos %A Gousios, Georgios %A Diomidis Spinellis %B MSR '15: Proceedings of the 2015 International Working Conference on Mining Software Repositories %I IEEE Computer Society %8 05/2015 %U http://gaijin.dmst.aueb.gr/~bkarak/poster_msr2015.pdf %0 Conference Paper %B MSR '15: Proceedings of the 12th Working Conference on Mining Software Repositories %D 2015 %T A Repository with 44 Years of Unix Evolution %A Diomidis Spinellis %X The evolution of the Unix operating system is made available as a version-control repository, covering the period from its inception in 1972 as a five thousand line kernel, to 2015 as a widely-used 26 million line system. The repository contains 659 thousand commits and 2306 merges. The repository employs the commonly used Git system for its storage, and is hosted on the popular GitHub archive. It has been created by synthesizing with custom software 24 snapshots of systems developed at Bell Labs, Berkeley University, and the 386BSD team, two legacy repositories, and the modern repository of the open source FreeBSD system. In total, 850 individual contributors are identified, the early ones through primary research. The data set can be used for empirical research in software engineering, information systems, and software archaeology. %B MSR '15: Proceedings of the 12th Working Conference on Mining Software Repositories %I IEEE %P 13–16 %8 05/2015 %U http://www.dmst.aueb.gr/dds/pubs/conf/2015-MSR-Unix-History/html/Spi15c.html %R 10.1109/MSR.2015.6 %> https://flosshub.org/sites/flosshub.org/files/Spi15c.pdf %0 Conference Paper %B Proceedings of the 11th Working Conference on Mining Software Repositories %D 2014 %T The Bug Catalog of the Maven Ecosystem %A Mitropoulos, Dimitris %A Vassilios Karakoidas %A Louridas, Panos %A Gousios, Georgios %A Diomidis Spinellis %K findbugs %K Maven Repository %K msr data showcase %K Software Bugs %X Examining software ecosystems can provide the research community with data regarding artifacts, processes, and communities. We present a dataset obtained from the Maven central repository ecosystem (approximately 265GB of data) by statically analyzing the repository to detect potential software bugs. For our analysis we used FindBugs, a tool that examines Java bytecode to detect numerous types of bugs. The dataset contains the metrics results that FindBugs reports for every project version (a JAR) included in the ecosystem. For every version we also stored specific metadata such as the JAR's size, its dependencies and others. Our dataset can be used to produce interesting research results, as we show in specific examples. %B Proceedings of the 11th Working Conference on Mining Software Repositories %S MSR 2014 %I ACM %C New York, NY, USA %P 372–375 %@ 978-1-4503-2863-0 %U http://doi.acm.org/10.1145/2597073.2597123 %R 10.1145/2597073.2597123 %> https://flosshub.org/sites/flosshub.org/files/mitro.pdf %0 Conference Paper %B 2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories %D 2009 %T A platform for software engineering research %A Gousios, Georgios %A Diomidis Spinellis %K alitheia core %X Research in the fields of software quality, maintainability and evolution requires the analysis of large quantities of data, which often originate from open source software projects. Collecting and preprocessing data, calculating metrics, and synthesizing composite results from a large corpus of project artifacts is a tedious and error prone task lacking direct scientific value. The Alitheia Core tool is an extensible platform for software quality analysis that is designed specifically to facilitate software engineering research on large and diverse data sources, by integrating data collection and preprocessing phases with an array of analysis services, and presenting the researcher with an easy to use extension mechanism. Alitheia Core aims to be the basis of an ecosystem of shared tools and research data that will enable researchers to focus on their research questions at hand, rather than spend time on re-implementing analysis tools. In this paper, we present the Alitheia Core platform in detail and demonstrate its usefulness in mining software repositories by guiding the reader through the steps required to execute a simple experiment. %B 2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories %I IEEE %C Vancouver, BC, Canada %P 31 - 40 %@ 978-1-4244-3493-0 %R 10.1109/MSR.2009.5069478 %> https://flosshub.org/sites/flosshub.org/files/31gousios.pdf %0 Conference Paper %B Electronic Notes in Theoretical Computer Science %D 2008 %T Evaluating the Quality of Open Source Software %A Diomidis Spinellis %A Gousios, Georgios %A Vassilios Karakoidas %A Panagiotis Louridas %A Paul J. Adams %A Samoladas, Ioannis %A Ioannis Stamelos %K bug tracking system %K email %K email archives %K mailing list %K metrics %K open source %K process quality attributes %K product quality attributes %K source code %K SQO-OSS %K wiki %X Traditionally, research on quality attributes was either kept under wraps within the organization that performed it, or carried out by outsiders using narrow, black-box techniques. The emergence of open source software has changed this picture allowing us to evaluate both software products and the processes that yield them. Thus, the software source code and the associated data stored in the version control system, the bug tracking databases, the mailing lists, and the wikis allow us to evaluate quality in a transparent way. Even better, the large number of (often competing) open source projects makes it possible to contrast the quality of comparable systems serving the same domain. Furthermore, by combining historical source code snapshots with significant events, such as bug discoveries and fixes, we can further dig into the causes and effects of problems. Here we present motivating examples, tools, and techniques that can be used to evaluate the quality of open source (and by extension also proprietary) software. %B Electronic Notes in Theoretical Computer Science %I The Reengineering Forum %V 233 %P 5–28 %8 03/2009 %U http://www.dmst.aueb.gr/dds/pubs/conf/2008-SQM-SQOOSS/html/SGKL09.html %R 10.1016/j.entcs.2009.02.058 %> https://flosshub.org/sites/flosshub.org/files/entcs-sqooss.pdf %0 Conference Paper %B OSS2008: Open Source Development, Communities and Quality (IFIP 2.13) %D 2008 %T The SQO-OSS Quality Model: Measurement Based Open Source Software Evaluation %A Samoladas, Ioannis %A Gousios, Georgios %A Diomidis Spinellis %A Ioannis Stamelos %X Software quality evaluation has always been an important part of software business. The quality evaluation process is usually based on hierarchical quality models that measure various aspects of software quality and deduce a characterization of the product quality being evaluated. The particular nature of open source software has rendered existing models inappropriate for detailed quality evaluations. In this paper, we present a hierarchical quality model that evaluates source code and community processes, based on automatic calculation of metric values and their correlation to a set of predefined quality profiles.1 %B OSS2008: Open Source Development, Communities and Quality (IFIP 2.13) %S IFIP International Federation for Information Processing %I Springer %V 275/2008 %P 237 - 248 %8 2008/// %G eng %& 19 %R http://dx.doi.org/10.1007/978-0-387-09684-1_19 %> https://flosshub.org/sites/flosshub.org/files/SQO-OSS%20Quality%20Model.pdf %0 Conference Paper %B Proceedings of the 30th international conference on Software engineering %D 2008 %T A tale of four kernels %A Diomidis Spinellis %K comparison %K freebsd %K linux %K open source %K opensolaris %K proprietary software %K windows %K wrk %X The FreeBSD, GNU/Linux, Solaris, and Windows operating systems have kernels that provide comparable facilities. Interestingly, their code bases share almost no common parts, while their development processes vary dramatically. We analyze the source code of the four systems by collecting metrics in the areas of file organization, code structure, code style, the use of the C preprocessor, and data organization. The aggregate results indicate that across various areas and many different metrics, four systems developed using wildly different processes score comparably. This allows us to posit that the structure and internal quality attributes of a working, non-trivial software artifact will represent first and foremost the engineering requirements of its construction, with the influence of process being marginal, if any. %B Proceedings of the 30th international conference on Software engineering %S ICSE '08 %I ACM %C New York, NY, USA %P 381–390 %@ 978-1-60558-079-1 %U http://doi.acm.org/10.1145/1368088.1368140 %R 10.1145/1368088.1368140 %0 Journal Article %D 2004 %T How is Open Source affecting software development? %A Diomidis Spinellis %A Clemens Szyperski %X Paper describes impact of using open source software in general development environments. (From the intro): " The dynamism of open source software development efforts, numerous high-profile success stories, and the novel economic, business, and legal aspects of open source software adoption are justifiably creating a stir in the development community. We software practitioners increasingly face the possibility of using or basing our work on open source components, libraries, frameworks, systems, platforms, and development environments." %8 January %G eng %> https://flosshub.org/sites/flosshub.org/files/spinellisszyperski.pdf