Review on Quality Models for Open Source Software and its reflection on Social Coding

Cyber security is a rapidly developing field and open-source software (OSS) is being led by a collaborative community and a transparent nature. This research intends to make a theoretical framework highlighting the symbiosis of community engagement models, governance models, and the security of open-source ecosystems. The significant purposes aim to investigate how community engagement affects open source software development, analyze the deployment of the governance systems in widely used open source projects, and create the theoretical model that brings the cybersecurity processes in those practices. The literature survey covers existing research on open-source software development, community engagement, governance models, and cybersecurity practices within the OSS ecosystem. Through literature review the basic concepts are investigated using conceptual analysis to determine which principles and mechanisms the Community Model Engagement and Governance models operate, influencing the security of Open Source Software. Open-source project policy recommendations are the foundation for the security of communities where members fully contribute to better governance. This includes developing a fundamental conceptual analysis to lay out the framework's principles and operation (mechanisms). This contributes to the overall development of the theoretical framework. This research expects to develop a standardized theoretical framework that tackles the community engagement-governance models-security software link from new and insightful perspectives. Practical policy recommendations to protect OSS projects will be presented to solve the cybersecurity problem easily and immediately. This study aims to add to the academic and practical discussions that focus on human and organizational components' critical roles in securing open-source software. The discussion of theoretical aspects gives this platform a unique angle that fits well into the technical approach while improving the understanding of a legally open cybersecurity community

Open Source Software (OSS) is software products available to the public, with its source code to study, change, and improves its design. Open Source Software Development (OSSD) is the process by which open source software is developed within the confines of software engineering life-cycle methods. However when open source used for commercial purpose, then an open source license is required. Open source software is very often developed in a public and collaborative manner. The quality assurance principle under open source software development is an approach to improve software product quality against traditional methods and techniques. Despite the fact that the open source developments have seen remarkable successful in recent years, there are a number of product quality issues and challenges facing the open source development model. Many industries and business sectors are following or using OSSD, since they realize the benefits, but they do have some reservations concerning quality assurance in the form of program code quality, maintenance of the code and its quality, over the life-cycle of the product and third party usage. This paper reviews the literature of the process of the latest quality assurance, under open source software development methods and techniques. The result from this review is to show the process of quality assurance of open source software and that how it can affect the overall quality assurance principal.

Summary form only given. In spite of the hype and hysteria surrounding open source software development, there is very little that can be said of open source in general. Open source projects range in scope from the miniscule, such as the thousands of non-maintained code dumps left behind at the end of class projects, dissertations, and failed commercial ventures, to the truly international, with thousands of developers collaborating, directly or indirectly, on a common platform. One characteristic that is shared by the largest and most successful open source projects, however, is a software architecture designed to promote anarchic collaboration through extensions while at the same time preserving centralized control over the interfaces. This paper features a survey of the state-of-the-practice in open source development in regards to software architecture, with particular emphasis on the modular extensibility interfaces within several of the most successful projects, including Apache httpd, Eclipse, Mozilla Firefox, Linux kernel, and the World Wide Web (which few people recognize as an open source project in itself). These projects fall under the general category of collaborative open source software development, which emphasizes community aspects of software engineering in order to compensate for the often-volunteer nature of core developers and take advantage of the scalability obtainable through Internet-based virtual organizations.

Interest of scientific research on Open Source software and its development process is frequent. The number of articles available and the number of tracks or workshops on this topic in most relevant IS Conferences is high. The usability of Open Source Software has been scarcely considered until few years ago, probably due to the particular role that the user has in such a development environment. In Open Source software development, users and developers are not so different. Anyhow, the diffusion of the Open Source software outside the development community contributes to sharpen the distinction among these two groups that are no longer equivalent. This circumstance has contributed to increase the interest on usability of Open Source software. Nevertheless, studies on end-users in Open Source contexts are still young. This paper introduces a pilot study on end user's perception of Open Source software. The aim of this pilot study is to identify how the end user perceives the Open Source software (in terms of Usability, Functionality, Reliability, Efficiency and Quality in Use).

“We do not appreciate being experimented on”: Developer and researcher views on the ethics of experiments on open-source projects

Open source software is becoming increasingly prominent, and the economic structure of open-source development is changing. In recent years, firms motivated by revenues from software services markets have become the primary contributors to open-source development. In this paper we study the role of services in open source software development and explore the choice between open source and proprietary software. Specifically, our economic model jointly analyzes the investment and pricing decisions of the originators of software and of subsequent open-source contributors. We find that if a contributor is efficient in software development, the originator should adopt an open-source strategy, allowing the contributor to offer higher total quality and capture the higher end of the market while the originator focuses on providing software services to lower end consumers. Conversely, if the contributor is not efficient in development, the originator should adopt a proprietary software development strategy, gaining revenue from software sales and squeezing the contributor out of the services market. In certain cases an increase in originator development efficiency can result in increased contributor profits. Finally, we find that, somewhat counterintuitively, an increase in contributor development efficiency can reduce overall social welfare.

There has been a recent surge of interest in open source software development, which involves developers at many different locations and organizations sharing code to develop and refine programs. To an economist, the behavior of individual programmers and commercial companies engaged in open source projects is initially startling. This paper makes a preliminary exploration of the economics of open source software. We highlight the extent to which labor economics, especially the literature on career concerns’, can explain many of these projects’ features. Aspects of the future of open source development process, however, remain somewhat difficult to predict with off-the-shelf’ economic models.

Open Source Software (OSS) projects rely on the efforts of thousands of software developers. The sustainability and diversity of these communities are two important factors for the longterm viability of OSS communities. This paper reviews the research on OSS sustainability and diversity. Drawing on the findings of measures on sustainability and diversity, we applied a number of the established metrics to the Android Open Source Project and found that over a third of all contributions originate from Google. Surprisingly, in 2015 we saw a decrease in the total number of contributors within the Android project. Findings from our analysis highlight the importance of sustainability and diversity for the development of OSS.

In spite of the lack of organizational control, a large number of these self-organized groups have successfully developed high quality software in open source software projects. We examined the process through which coordinated action emerges from the collection of individual developers' choices, i.e., how bottom-up coordination occurs and argue that developer herding on a social coding platform may have a positive impact on OSSD outcomes. As an exploratory study, we analyzed the participation patterns in 10 randomly sampled OSSD projects on a social open source code foundry, Github. Based on the findings we generate theoretical propositions regarding developer herding behavior in OSSD.

Usability is an important quality characteristic of software products and information systems. Different approaches for introducing usability activities into open source software (OSS) development have not yet been fully evaluated. This paper experiments with the introduction of usability activities into OSS development through a participative approach. An empirical case study was carried out in a game development OSS project. The results of this study suggest that it is beneficial to introduce usability activities into OSS development through the participative approach. In the participative approach the usability experts become recognized part of the development community through adapting their ways of work into the culture of the OSS project and submitting code patches. This participative approach had a clear impact in the case project as seen in changes in the user interface and in improved usability. The challenge of adapting usability and OSS development philosophies and practices should, however, be researched further.

This paper outlines a critical, textual approach for the analysis of the relationship between different actors in information technology (IT) production, and further concretizes the approach in the analysis of the role of users in the open source software (OSS) development literature. Central concepts of the approach are outlined. The role of users is conceptualized as reader involvement aiming to contribute to the configuration of the reader (to how users and the parameters for their work practices are defined in OSS texts). Afterwards, OSS literature addressing reader involvement is critically reviewed. In OSS context, the OSS writers as readers configure the reader and other readers are assumed to be capable of and interested in commenting the texts. A lack of OSS research on non-technical reader involvement is identified. Furthermore, not only are the OSS readers configured, but so are OSS writers. In OSS context while writers may be empowered, this clearly does not apply to the non-technical OSS readers. Implication for research and practice are discussed.

By reviewing the history of the open-source movement and highlighting recent research on its unique developmental processes, the author suggests that there are general lessons for anyone seeking to encourage innovation in any field or industry. What incentives, for instance, spark these Internet-based communities of software developers to innovate voluntarily outside the company's boundaries without formal work agreements? Research shows that open-source software developers freely reveal and share information because they garner personal benefits, such as reputation enhancement, expertise refinement and, quite simply, enjoyment. Researchers also note that, since most of these benefits are contingent upon membership in well-functioning developer enclaves, a sense of community is important to the open-source phenomenon. For example, identification with the highly esteemed Linux operating-system project instills a sense of responsibility and loyalty among contributors, who are motivated by their perceived indispensability to the team. Researchers point out, however, that developers also are motivated by a pragmatic desire to customize software. Much of the referenced research explores the unusual nature of open-source licensing agreements and intellectual-property protection. That is, open-source licenses guarantee the rights not of developers, but of future users against appropriation, and developers guard their work zealously with online sanctioning, brands and logos. Noting that the products emanating from open-source projects are often commercially attractive and widely used in business and government (for example, at IBM, NASA, Sun Microsystems, the German government), the author concludes by discussing the implications for future business activities.

The use of free and open source software (OSS) is gaining momentum due to the ever increasing availability and use of the Internet. Organizations are also now adopting open source software, despite some reservations, in particular regarding the provision and availability of support. Some of the biggest concerns about free and open source software are post release software defects and their rectification, management of dynamic requirements and support to the users. A common belief is that there is no appropriate support available for this class of software. A contradictory argument is that due to the active involvement of Internet users in online forums, there is in fact a large resource available that communicates and manages the provision of support. The research model of this empirical investigation examines the evidence available to assess whether this commonly held belief is based on facts given the current developments in OSS or simply a myth, which has developed around OSS development. We analyzed a dataset consisting of 1880 open source software projects covering a broad range of categories in this investigation. The results show that online forums play a significant role in managing software defects, implementation of new requirements and providing support to the users in open source software and have become a major source of assistance in maintenance of the open source projects.

In stark contrast with the fully participative “bazaar” imagery of open source software (OSS) development, some recent empirical research has pointed out that much of the OSS development is carried out by a small percentage of developers. This raises serious concerns that concentration of development effort on a few will limit knowledge sharing and underutilize the available resources. Using the notion of strategic interaction, this paper argues that individual developers often interact strategically with other highly resourceful developers by forming a smaller but better organized structure to intensify the types of epistemic interactions that matter most to the OSS development. A general framework of strategic interaction including participation inequality, conversational interactivity, and cross-thread connectivity is proposed to examine its impact on knowledge sharing, and validated using 128 discussion threads from the K Desktop Environment (KDE) developer mailing list. The findings indicate that strategic interaction has expanded knowledge sharing but with the caveat that extreme concentration of development could have an opposite effect. For researchers, this study dovetails the incentive logic by proposing and validating the strategic aspects of OSS participation to better understand the collective dynamics underpinning OSS development. Practitioners can use this approach to evaluate and better support existing knowledge-sharing initiatives.

BackgroundInnovation through an open source model has proven to be successful for software development. This success has led many to speculate if open source can be applied to other industries with similar success. We attempt to provide an understanding of open source software development characteristics for researchers, business leaders and government officials who may be interested in utilizing open source innovation in other contexts and with an emphasis on drug discovery.MethodsA systematic review was performed by searching relevant, multidisciplinary databases to extract empirical research regarding the common characteristics and barriers of initiating and maintaining an open source software development project.ResultsCommon characteristics to open source software development pertinent to open source drug discovery were extracted. The characteristics were then grouped into the areas of participant attraction, management of volunteers, control mechanisms, legal framework and physical constraints. Lastly, their applicability to drug discovery was examined.ConclusionsWe believe that the open source model is viable for drug discovery, although it is unlikely that it will exactly follow the form used in software development. Hybrids will likely develop that suit the unique characteristics of drug discovery. We suggest potential motivations for organizations to join an open source drug discovery project. We also examine specific differences between software and medicines, specifically how the need for laboratories and physical goods will impact the model as well as the effect of patents.