Trust in Open Source Software Development Communities: A Comprehensive Analysis

Trust in Open Source Software Development Communities: A Comprehensive Analysis

Amitpal Singh Sohal (Research Scholar, IKG Punjab Technical University, Kapurthala, Punjab, India), Sunil Kumar Gupta (Department of Computer Science and Engineering, Beant College of Engineering and Technology, Gurdaspur, Punjab, India) and Hardeep Singh (Department of Computer Science, Guru Nanak Dev University, Amritsar, Punjab, India)
Copyright: © 2018 |Pages: 19
DOI: 10.4018/IJOSSP.2018100101
OnDemand PDF Download:
No Current Special Offers


This study presents the significance of trust for the formation of an Open Source Software Development (OSSD) community. OSSD has various challenges that must be overcome for its successful operation. First is the development of a community, which requires a healthy community formation environment. Taking into consideration various factors for community formation, a strong sense of TRUST among its members has been felt. Trust development is a slow process with various methods for building and maintaining it. OSSD is teamwork but the team is of unknowns and volunteers. Trust forms a pillar for effective cooperation, which leads to a reduction in conflicts and risks, associated with quality software development. This study offers an overview of various existing trust models, which aids in the development of a trust evaluation framework for OSSD communities. Towards the end of the study, various components of the trust evaluation along with an empirical framework for the same have been proposed.
Article Preview

1. Introduction

Open source software development (OSSD) is an ideology, which has paved the way for which dedicated teams of volunteer software developers participate and contribute in various areas of software engineering. The aim of OSSD communities is to make a high quality and reliable software, no matter how complex an application may be (Asundi, 2001). The project is initiated by the core team and is made open for developers across the globe to contributing code and feature enhancements. The core team of the project analyzes the contributions from various contributors. The core team may have single or number of coordinators. Coordinators are project creators and are responsible for the evolution and growth of the community. They would take the final decision to incorporate the received code into the final build and release the next test version of the software. After rigorous testing and debugging when the required quality of software is achieved, test versions of software are promoted to be the next stable release. Further, with the passage of time new contributions in form of bug fixes and feature enhancements for the software are received. The same cycle of thorough testing and integration of code into existing software is followed. Every effort is done to attract more and more people towards the project and with the passage of time the community grows. The team members of the OSSD community provide feedback, which acts as a base for the planning of future project managing strategies. With constant efforts, gradually, the project attains high quality and upcoming issues are dealt with even better ways. The ways in which development work is coordinated and communicated amongst the developers makes it different from existing software development strategies and this is what is unique. It is intended to perform a study for improvement of the relationship among the virtual team members of an OSSD community, which in turn enhances the quality of the developed open source software. We move ahead with this work, keeping in mind the following research objectives.

Complete Article List

Search this Journal:
Open Access Articles
Volume 13: 4 Issues (2022): Forthcoming, Available for Pre-Order
Volume 12: 4 Issues (2021): 1 Released, 3 Forthcoming
Volume 11: 4 Issues (2020)
Volume 10: 4 Issues (2019)
Volume 9: 4 Issues (2018)
Volume 8: 4 Issues (2017)
Volume 7: 4 Issues (2016)
Volume 6: 1 Issue (2015)
Volume 5: 3 Issues (2014)
Volume 4: 4 Issues (2012)
Volume 3: 4 Issues (2011)
Volume 2: 4 Issues (2010)
Volume 1: 4 Issues (2009)
View Complete Journal Contents Listing