| 1. |
- Butler, Simon, et al.
(författare)
-
An Investigation of Work Practices Used by Companies Making Contributions to Established OSS Projects
- 2018
-
Ingår i: ICSE-SEIP '18 Proceedings of the 40th International Conference on Software Engineering: Software Engineering in Practice. - New York : Association for Computing Machinery (ACM). - 9781450356596 ; , s. 201-210
-
Konferensbidrag (refereegranskat)abstract
- Professionals contribute to open source software (OSS) projects aspart of their employment. Previous research has addressed motivationsof individuals and the ways they engage with OSS projects.However, there is a lack of research which examines and explainswork practices used by companies in their engagement with projects.Work practices used by companies to contribute to five establishedOSS projects are investigated through examination of the actions ofemployees in public communication channels and draw on our experienceswhen analysing engagement with the same projects. Wefind that companies utilise work practices for contributing whichare congruent with the circumstances and their capabilities thatsupport their short and long term needs. We find that companiescontribute to OSS projects in different ways, such as employing coreproject developers, making donations, and joining project steeringcommittees in order to advance strategic interests.
|
|
| 2. |
- Klotins, Eriks, et al.
(författare)
-
Exploration of technical debt in start-ups
- 2018
-
Ingår i: Proceedings - International Conference on Software Engineering. - New York, NY, USA : IEEE Computer Society. - 9781450356596 ; , s. 75-84
-
Konferensbidrag (refereegranskat)abstract
- Context: Software start-ups are young companies aiming to build and market software-intensive products fast with little resources. Aiming to accelerate time-to-market, start-ups often opt for ad-hoc engineering practices, make shortcuts in product engineering, and accumulate technical debt. Objective: In this paper we explore to what extent precedents, dimensions and outcomes associated with technical debt are prevalent in start-ups. Method: We apply a case survey method to identify aspects of technical debt and contextual information characterizing the engineering context in start-ups. Results: By analyzing responses from 86 start-up cases we found that start-ups accumulate most technical debt in the testing dimension, despite attempts to automate testing. Furthermore, we found that start-up team size and experience is a leading precedent for accumulating technical debt: larger teams face more challenges in keeping the debt under control. Conclusions: This study highlights the necessity to monitor levels of technical debt and to preemptively introduce practices to keep the debt under control. Adding more people to an already difficult to maintain product could amplify other precedents, such as resource shortages, communication issues and negatively affect decisions pertaining to the use of good engineering practices. © 2018 ACM.
|
|
| 3. |
- Urli, S., et al.
(författare)
-
How to design a program repair bot? : Insights from the repairnator project
- 2018
-
Ingår i: Proceeding ICSE-SEIP '18 Proceedings of the 40th International Conference on Software Engineering: Software Engineering in Practice. - New York, NY, USA : IEEE Computer Society. - 9781450356596 ; , s. 95-104
-
Konferensbidrag (refereegranskat)abstract
- Program repair research has made tremendous progress over the last few years, and software development bots are now being invented to help developers gain productivity. In this paper, we investigate the concept of a "program repair bot" and present Repairnator. The Repairnator bot is an autonomous agent that constantly monitors test failures, reproduces bugs, and runs program repair tools against each reproduced bug. If a patch is found, Repairnator bot reports it to the developers. At the time of writing, Repairnator uses three different program repair systems and has been operating since February 2017. In total, it has studied 11 523 test failures over 1 609 open-source software projects hosted on GitHub, and has generated patches for 15 different bugs. Over months, we hit a number of hard technical challenges and had to make various design and engineering decisions. This gives us a unique experience in this area. In this paper, we reflect upon Repairnator in order to share this knowledge with the automatic program repair community.
|
|
