Results 1 - 10
of
76
Coordination of free/libre open source software development
, 2005
"... the state of the literature. We develop a framework for organizing the literature based on the input-mediatoroutput-input (IMOI) model from the small groups literature. We present a quantitative summary of articles selected for the review and then discuss findings of this literature categorized into ..."
Abstract
-
Cited by 75 (28 self)
- Add to MetaCart
the state of the literature. We develop a framework for organizing the literature based on the input-mediatoroutput-input (IMOI) model from the small groups literature. We present a quantitative summary of articles selected for the review and then discuss findings of this literature categorized into issues pertaining to inputs (e.g., member characteristics, technology use and project characteristics), processes (software development and social processes), emergent states (e.g., trust and task related states) and outputs (e.g. team performance, FLOSS implementation and project evolution). Based on this review, we suggest topics for future research, as well as identifying methodological and theoretical issues for future inquiry in this area, including issues relating to sampling and the need for more longitudinal studies.
Emerging issues in the acquisition of open source software within the U.S. Department of Defense
- In Proceedings of the 5th Annual Acquisition Research Symposium
, 2008
"... ^Åèìáëáíáçå=oÉëÉ~êÅÜ=mêçÖê~ã= do^ar^qb=p`elli=lc=_rpfkbpp=C=mr_if`=mlif`v= k^s^i=mlpqdo^ar^qb=p`elli= Approved for public release, distribution is unlimited. ..."
Abstract
-
Cited by 26 (22 self)
- Add to MetaCart
(Show Context)
^Åèìáëáíáçå=oÉëÉ~êÅÜ=mêçÖê~ã= do^ar^qb=p`elli=lc=_rpfkbpp=C=mr_if`=mlif`v= k^s^i=mlpqdo^ar^qb=p`elli= Approved for public release, distribution is unlimited.
Engineering the software for understanding climate change
- Computing in Science and Engineering
, 2009
"... Climate scientists build large, complex simulations with little or no software engineering training, and do not readily adopt the latest software engineering tools and techniques. In this paper, we describe an ethnographic study of the culture and practices of climate scientists at the Met Office Ha ..."
Abstract
-
Cited by 19 (1 self)
- Add to MetaCart
(Show Context)
Climate scientists build large, complex simulations with little or no software engineering training, and do not readily adopt the latest software engineering tools and techniques. In this paper, we describe an ethnographic study of the culture and practices of climate scientists at the Met Office Hadley Centre. The study examined how the scientists think about software correctness, how they prioritize requirements, and how they develop a shared understanding of their models. The findings show that climate scientists have developed customized techniques for verification and validation that are tightly integrated into their approach to scientific research. Their software practices share many features of both agile and open source projects, in that they rely on self-organisation of the teams, extensive use of informal communication channels, and developers who are also users and domain experts. These comparisons offer insights into why such practices work. 1.
Understanding Requirements for Open Source Software
, 2008
"... This study presents findings from an empirical study directed at understanding the roles, forms, and consequences arising in requirements for open source software (OSS) development efforts. Five open source software development communities are described, examined, and compared to help discover wha ..."
Abstract
-
Cited by 18 (7 self)
- Add to MetaCart
(Show Context)
This study presents findings from an empirical study directed at understanding the roles, forms, and consequences arising in requirements for open source software (OSS) development efforts. Five open source software development communities are described, examined, and compared to help discover what differences may be observed. At least two dozen kinds of software informalisms are found to play a critical role in the elicitation, analysis, specification, validation, and management of requirements for developing OSS systems. Subsequently, understanding the roles these software informalisms take in a new formulation of the requirements development process for OSS is the focus of this study. This focus enables considering a reformulation of the requirements engineering process and its associated artifacts or (in)formalisms to better account for the requirements when developing OSS systems. Other findings identify how OSS requirements are decentralized across multiple informalisms, and to the need for advances in how to specify the capabilities of existing OSS systems.
The Commit Size Distribution of Open Source Software
- In Proceedings of the 42nd Hawaiian International Conference on System Sciences (HICSS 42
, 2009
"... ..."
(Show Context)
Let’s talk about it: evaluating contributions through discussion in GitHub
- In: Proceedings of the 22nd ACM SIGSOFT international
"... Open source software projects often rely on code contributions from a wide variety of developers to extend the capabilities of their software. Project members evaluate these contributions and often engage in extended discussions to decide whether to integrate changes. These discussions have importan ..."
Abstract
-
Cited by 8 (0 self)
- Add to MetaCart
(Show Context)
Open source software projects often rely on code contributions from a wide variety of developers to extend the capabilities of their software. Project members evaluate these contributions and often engage in extended discussions to decide whether to integrate changes. These discussions have important implications for project management regarding new contributors and evolution of project requirements and direction. We present a study of how developers in open work environments evaluate and discuss pull requests, a primary method of contribution in GitHub, analyzing a sample of extended discussions around pull requests and interviews with GitHub developers. We found that developers raised issues around contributions over both the appropriateness of the problem that the submitter attempted to solve and the correctness of the implemented solution. Both core project members and third-party stakeholders discussed and sometimes implemented alternative solutions to address these issues. Different stakeholders also influenced the outcome of the evaluation by eliciting support from different communities such as dependent projects or even companies. We also found that evaluation outcomes may be more complex than simply acceptance or rejection. In some cases, although a submitter's contribution was rejected, the core team fulfilled the submitter's technical goals by implementing an alternative solution. We found that the level of a submitter's prior interaction on a project changed how politely developers discussed the contribution and the nature of proposed alternative solutions.
Towards a Global Research Infrastructure for Multidisciplinary Study of Free/Open Source Software Development
- In Open Source Development, Community and Quality, IFIP International Federation for Information Processing
, 2008
"... Abstract. The Free/Open Source Software (F/OSS) research community is growing across and within multiple disciplines. This community faces a new and unusual situation. The traditional difficulties of gathering enough empirical data have been replaced by issues of dealing with enormous amounts of fr ..."
Abstract
-
Cited by 7 (5 self)
- Add to MetaCart
(Show Context)
Abstract. The Free/Open Source Software (F/OSS) research community is growing across and within multiple disciplines. This community faces a new and unusual situation. The traditional difficulties of gathering enough empirical data have been replaced by issues of dealing with enormous amounts of freely available public data from many disparate sources (online discussion forums, source code directories, bug reports, OSS Web portals, etc.). Consequently, these data are being discovered, gathered, analyzed, and used to support multidisciplinary research. However at present, no means exist for assembling these data under common access points and frameworks for comparative, longitudinal, and collaborative research across disciplines. Gathering and maintaining large F/OSS data collections reliably and making them usable present several research challenges. For example, current projects usually rely on direct access to, and mining of raw data from groups that generate it, and both of these methods require unique effort for each new corpus, or even for updating existing corpora. In this paper, we identify several needs and critical factors in F/OSS empirical research across disciplines, and suggest recommendations for design of a global research infrastructure for multi-disciplinary research into F/OSS development.
Computer Game Mods, Modders, Modding, and the Mod Scene
"... Computer games have increasingly been the focus of user-led innovations in the form of game mods. This paper examines how different kinds of socio-technical affordances serve to organize the actions of the people who develop and share their game mods. The affordances examined include customization a ..."
Abstract
-
Cited by 6 (0 self)
- Add to MetaCart
(Show Context)
Computer games have increasingly been the focus of user-led innovations in the form of game mods. This paper examines how different kinds of socio-technical affordances serve to organize the actions of the people who develop and share their game mods. The affordances examined include customization and tailoring mechanisms, software and content copyright licenses, game software infrastructure and development tools, career contingencies and organizational practices of mod teams, and social worlds intersecting the mod scene. Numerous examples will be used to ground this review and highlight how such affordances can organize, facilitate or constrain what can be done. Overall, this study helps to provide a deeper understanding of how a web of associated affordances collectively serve to govern what mods get made, how modding practices emerge and flourish, and how modders and the game industry serve each others ' interests, though not always in equivocal terms.
The Future of Research in Free/Open Source Software Development
"... Free/Open Source Software (FOSS) development is not the same an Software Engineering (SE). Why this is so is unclear and open to various interpretations. Both address the challenges of developing large software systems, but the development processes, work practices, and project forms differ signific ..."
Abstract
-
Cited by 5 (1 self)
- Add to MetaCart
(Show Context)
Free/Open Source Software (FOSS) development is not the same an Software Engineering (SE). Why this is so is unclear and open to various interpretations. Both address the challenges of developing large software systems, but the development processes, work practices, and project forms differ significantly and in interesting ways according to recent empirical studies. This paper reports on highlights from a workshop held in early 2010 on the future of research in FOSS, and how such research relates to or informs our understanding of FOSS and SE, collaborative software development work, software evolution, and new software ecosystems. FOSS and SE are complementary in many ways, yet different in others, so understanding these complements and differences can help advance the future of research in both FOSS and SE. Some of these complements and differences are identified in this paper. Categories and Subject Descriptors
Ongoing Software Development without Classical Requirements
"... Abstract—Many prominent open source software (OSS) development projects produce systems without overt requirements artifacts or processes, contrary to expectations resulting from classical software development experience and research, and a growing number of critical software systems are evolved and ..."
Abstract
-
Cited by 4 (0 self)
- Add to MetaCart
(Show Context)
Abstract—Many prominent open source software (OSS) development projects produce systems without overt requirements artifacts or processes, contrary to expectations resulting from classical software development experience and research, and a growing number of critical software systems are evolved and sustained in this way yet provide quality and rich functional capabilities to users and integrators that accept them without question. We examine data from several OSS projects to investigate this conundrum, and discuss the results of research into OSS outcomes that sheds light on the consequences of this approach to software requirements in terms of risk of development failure and quality of the resulting system. Index Terms—open source software; open source requirements; provisionments. I.
