%0 Journal Article %J Journal of the Association for Information Systems %D 2011 %T Adopting Free/Libre/Open Source Software Practices, Techniques and Methods for Industrial Use %A Torkar, Richard %A Minoves, Pau %A Garrigós, Janina %K freebsd %K jboss %K linux %K linux kernel %X Today’s software companies face the challenges of highly distributed development projects and constantly changing requirements. This paper proposes the adoption of relevant Free/Libre/Open Source Software (FLOSS) practices in order to improve software development projects in industry. Many FLOSS projects have proven to be very successful, producing high quality products with steady and frequent releases. This study aims to identify FLOSS practices that can be adapted for the corporate environment. To achieve this goal, a framework to compare FLOSS and industrial development methodologies was created. Three successful FLOSS projects were selected as study targets (the Linux Kernel, the FreeBSD operating system, and the JBoss application server), as well as two projects from Ericsson, a large telecommunications company. Based on an analysis of these projects, FLOSS best practices were tailored to fit industrial development environments. The final results consisted of a set of key adoption opportunities that aimed to improve software quality and overall development productivity by importing best practices from the FLOSS environment. The adoption opportunities were then validated at three large corporations. %B Journal of the Association for Information Systems %V 12 %U http://aisel.aisnet.org/jais/vol12/iss1/1 %N 1 %0 Conference Paper %B 2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010) %D 2010 %T The evolution of ANT build systems %A McIntosh, Shane %A Adams, Bram %A Hassan, Ahmed E. %K ant %K argouml %K build %K eclipse %K jboss %K maintenance %K metrics %K source code %K tomcat %X Build systems are responsible for transforming static source code artifacts into executable software. While build systems play such a crucial role in software development and maintenance, they have been largely ignored by software evolution researchers. With a firm understanding of build system aging processes, project managers could allocate personnel and resources to build system maintenance tasks more effectively, reducing the build maintenance overhead on regular development activities. In this paper, we study the evolution of ANT build systems from two perspectives: (1) a static perspective, where we examine the build system specifications using software metrics adopted from the source code domain; and (2) a dynamic perspective where representative sample build runs are conducted and their output logs are analyzed. Case studies of four open source ANT build systems with a combined history of 152 releases show that not only do ANT build systems evolve, but also that they need to react in an agile manner to changes in the source code. %B 2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010) %I IEEE %C Cape Town, South Africa %P 42 - 51 %@ 978-1-4244-6802-7 %R 10.1109/MSR.2010.5463341 %> https://flosshub.org/sites/flosshub.org/files/42msr2010_mcintosh.pdf %0 Conference Paper %B Proceedings of the 2008 international workshop on Mining software repositories - MSR '08 %D 2008 %T On the relation of refactorings and software defect prediction %A Sigmund, Thomas %A Gall, Harald C. %A Ratzinger, Jacek %Y Hassan, Ahmed E. %Y Lanza, Michele %Y Godfrey, Michael W. %K argouml %K bug fixing %K bug reports %K defects %K evolution %K jboss %K liferay %K prediction %K refactoring %K spring %K weka %K xdoclet %X This paper analyzes the influence of evolution activities such as refactoring on software defects. In a case study of five open source projects we used attributes of software evolution to predict defects in time periods of six months. We use versioning and issue tracking systems to extract 110 data mining features, which are separated into refactoring and non-refactoring related features. These features are used as input into classification algorithms that create prediction models for software defects. We found out that refactoring related features as well as non-refactoring related features lead to high quality prediction models. Additionally, we discovered that refactorings and defects have an inverse correlation: The number of software defects decreases, if the number of refactorings increased in the preceding time period. As a result, refactoring should be a significant part of both bug fixes and other evolutionary changes to reduce software defects. %B Proceedings of the 2008 international workshop on Mining software repositories - MSR '08 %I ACM Press %C New York, New York, USA %P 35-38 %8 05/2008 %@ 9781605580241 %! MSR '08 %R 10.1145/1370750.1370759 %> https://flosshub.org/sites/flosshub.org/files/p35-ratzinger.pdf %0 Conference Paper %B Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007) %D 2007 %T How Long Will It Take to Fix This Bug? %A Weiss, Cathrin %A Premraj, Rahul %A Zimmermann, Thomas %A Zeller, Andreas %K bug fixing %K bug reports %K effort estimation %K jboss %K lucene %K prediction %K time %X Predicting the time and effort for a software problem has long been a difficult task. We present an approach that automatically predicts the fixing effort, i.e., the person-hours spent on fixing an issue. Our technique leverages existing issue tracking systems: given a new issue report, we use the Lucene framework to search for similar, earlier reports and use their average time as a prediction. Our approach thus allows for early effort estimation, helping in assigning issues and scheduling stable releases. We evaluated our approach using effort data from the JBoss project. Given a sufficient number of issues reports, our automatic predictions are close to the actual effort; for issues that are bugs, we are off by only one hour, beating naive predictions by a factor of four. %B Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007) %I IEEE %C Minneapolis, MN, USA %P 1 %@ 0-7695-2950-X %R 10.1109/MSR.2007.13 %> https://flosshub.org/sites/flosshub.org/files/28300001.pdf %0 Conference Paper %B Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007) %D 2007 %T Mining Workspace Updates in CVS %A Zimmermann, Thomas %K change management %K cvs %K developers %K gcc %K jboss %K jedit %K python %K workspaces %X The version control archive CVS records not only all changes in a project but also activity data such as when developers create or update their workspaces. Furthermore, CVS records when it has to integrate changes because of parallel development. In this paper, we analyze the CVS activity data of four large open-source projects GCC, JBOSS, JEDIT, and PYTHON to investigate parallel development: What is the degree of parallel development? How frequently do conflicts occur during updates and how are they resolved? How do we identify changes that contain integrations? %B Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007) %I IEEE %C Minneapolis, MN, USA %P 11 - 11 %@ 0-7695-2950-X %R 10.1109/MSR.2007.22 %> https://flosshub.org/sites/flosshub.org/files/28300011.pdf