Mining frequent bug-fix code changes

Detecting bugs as early as possible plays an important role in ensuring software quality before shipping. We argue that mining previous bug fixes can produce good knowledge about why bugs happen and how they are fixed. In this paper, we mine the change history of 717 open source projects to extract bug-fix patterns. We also manually inspect many of the bugs we found to get insights into the contexts and reasons behind those bugs. For instance, we found out that missing null checks and missing initializations are very recurrent and we believe that they can be automatically detected and fixed.

Towards Faster Method Search Through Static Ecosystem Analysis

Software developers are often unsure of the exact name of the method they need to use to invoke the desired behavior in a given context. This results in a process of searching for the correct method name in documentation, which can be lengthy and distracting to the developer. We can decrease the method search time by enhancing the documentation of a class with the most frequently used methods. Usage frequency data for methods is gathered by analyzing other projects from the same ecosystem - written in the same language and sharing dependencies. We implemented a proof of concept of the approach for Pharo Smalltalk and Java. In Pharo Smalltalk, methods are commonly searched for using a code browser tool called "Nautilus", and in Java using a web browser displaying HTML based documentation - Javadoc. We developed plugins for both browsers and gathered method usage data from open source projects, in order to increase developer productivity by reducing method search time. A small initial evaluation has been conducted showing promising results in improving developer productivity.

Critical Issues of Centralized and Cloudified LTE-FDD Radio Access Networks

Cloudification of the Centralized-Radio Access Network (C-RAN) in which signal processing runs on general purpose processors inside virtual machines has lately received significant attention. Due to short deadlines in the LTE Frequency Division Duplex access method, processing time fluctuations introduced by the virtualization process have a deep impact on C-RAN performance. This paper evaluates bottlenecks of the OpenAirInterface (OAI is an open-source software-based implementation of LTE) cloud performance, provides feasibility studies on C-RAN execution, and introduces a cloud architecture that significantly reduces the encountered execution problems. In typical cloud environments, the OAI processing time deadlines cannot be guaranteed. Our proposed cloud architecture shows good characteristics for the OAI cloud execution. As an example, in our setup more than 99.5% processed LTE subframes reach reasonable processing deadlines close to performance of a dedicated machine.

Capacity Building in Geoprocessing

Manual used for the implementation of CDE's Geoprocessing courses in the South and East. Composed of 6 modules covering important aspects of GIS handling and implementation: 1) Introduction to GIS; 2) Management issues; 3) GIS data preparation; 4) GIS data presentation; 5) Vector data analysis; 6) Raster data analysis. At the moment the manual is designed for use with ArcGIS. Work on a manual for use with open source software is currently ongoing. This manual was successfully used during several GIS training events in Kenya and Tajikistan.

Extending private-collective innovation: a case study

The private-collective innovation model proposes incentives for individuals and firms to privately invest resources to create public goods innovations. Such innovations are characterized by non-rivalry and non-exclusivity in consumption. Examples include open source software, user-generated media products, drug formulas, and sport equipment designs. There is still limited empirical research on private-collective innovation. We present a case study to (1) provide empirical evidence of a case of private-collective innovation, showing specific benefits, and (2) to extend the private-collective innovation model by analyzing the hidden costs for the company involved. We examine the development of the Nokia Internet Tablet, which builds on both proprietary and open source software development, and that involves both Nokia developers and volunteers who are not employed by the company. Seven benefits for Nokia are identified, as are five hidden costs: difficulty to differentiate, guarding business secrets, reducing community entry barriers, giving up control, and organizational inertia. We examine the actions taken by the management to mitigate these costs throughout the development period.

How Firms Make Friends: Communities in Private-Collective Innovation

When firms contribute to open source projects, they in fact invest into public goods which may be used by everyone, even by their competitors. This seemingly paradoxical behavior can be explained by the model of private-collective innovation where private investors participate in collective action. Previous literature has shown that companies benefit through the production process providing them with unique incentives such as learning and reputation effects. By contributing to open source projects firms are able to build a network of external individuals and organizations participating in the creation and development of the software. As will be shown in this doctoral dissertation firm-sponsored communities involve the formation of interorganizational relationships which eventually may lead to a source of sustained competitive advantage. However, managing a largely independent open source community is a challenging balancing act between exertion of control to appropriate value creation, and openness in order to gain and preserve credibility and motivate external contributions. Therefore, this dissertation consisting of an introductory chapter and three separate research papers analyzes characteristics of firm-driven open source communities, finds reasons why and mechanisms by which companies facilitate the creation of such networks, and shows how firms can benefit most from their communities.

Who cares about my feature request?

Previous studies on issue tracking systems for open source software (OSS) focused mainly on requests for bug fixes. However, requests to add a new feature or an improvement to an OSS project are often also made in an issue tracking system. These inquiries are particularly important because they determine the further development of the software. This study examines if there is any difference between requests of the IBM developer community and other sources in terms of the likelihood of successful implementation. Our study consists of a case study of the issue tracking system BugZilla in the Eclipse integrated development environment (IDE). Our hypothesis, which was that feature requests from outsiders have less chances of being implemented, than feature requests from IBM developers, was confirmed.