Licensing and Competition for Services in Open Source Software

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.

The Move to the Middle: Convergence of the Open-Source and Proprietary Software Industries

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).

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.

Open Source vs. Proprietary Software: Competition and Compatibility

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.

Background: The popularity of the open source software development in the last decade, has brought about an increased interest from the industry on how to use open source components, participate in the open source community, build business models around this type of software development, and learn more about open source development methodologies. Aim: The aim of this study is to review research carried out on usage of open source components and development methodologies by the industry, as well as companies’ participation in the open source community. Method: Systematic review through searches in library databases and manual identification of articles from the open source conference. Results: 19 articles were identified. Conclusions: The articles could be divided into four categories: open source as part of component based software engineering, business models with open source in commercial organization, company participation in open source development communities, and usage of open source processes within a company.

Despite the growing success of the Open Source movement, most of the general public continues to feel that Open Source software is inaccessible to them. This paper discusses five fundamental problems with the current Open Source software development trend, explores why these issues are holding the movement back, and offers solutions that might help overcome these problems. The lack of focus on user interface design causes users to prefer proprietary software’s more intuitive interface. Open Source software tends to lack the complete and accessible documentation that retains users. Developers focus on features in their software, rather than ensuring that they have a solid core. Open Source programmers also tend to program with themselves as an intended audience, rather than the general public. Lastly, there is a widely known stubbornness by Open Source programmers in refusing to learn from what lessons proprietary software has to offer. If Open Source software wishes to become widely used and embraced by the general public, all five of these issues will have to be overcome.

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

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.

In open source software development, a major challenge is the prioritization of new requirements as well as the identification of responsible developers for their implementation. Unlike conventional industrial software development, where requirements engineers have to explicitly define who implements what, in the context of open source development, developers (contributors) usually decide on their own which requirements to implement next. Contributors have to deal with a huge number of requirements where the recognition of the most relevant ones often becomes a crucial task with a high impact on the success of a software project. This fact defines our major motivation for the development of a prioritization tool for the ECLIPSE community which recommends relevant requirements (issues/bugs) to open source developers. Our tool uses real-world data from ECLIPSE in order to build a prediction model. We trained and tested our tool with different classifiers such as Naive Bayes (representing our baseline), Decision Tree, and Random Forest. The evaluation results indicate that the Random Forest classifier correctly predicts issues with a precision of 0.88 (F1-score 0.68).CCS CONCEPTS• Information systems → Recommender systems; • Humancentered computing → Open source software; • Computing methodologies → Machine learning approaches; Natural language processing; • Software and its engineering → Requirements analysis.

One opportunity for organizations to participate in open source software (OSS) development is through <italic xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">organizations OSS</i> (orgsOSS), a term we use to describe a group of organizations that commit resources to collectively develop OSS. This archetype of OSS development is distinct from other types that include organizations, yet is understudied. As organizations increasingly contribute to and rely on OSS as part of their strategy, understanding how they can collaborate to build software holds importance for the future of software development. This study collects a unique dataset of development tasks from a large orgsOSS project spanning over two years and seven releases. Building on existing OSS research, we explore norms with respect to collaboration, i.e., how developers assign, discuss, and complete tasks, in an orgsOSS project. Interestingly, our analysis reveals that developers in orgsOSS do not always adhere to ideals of widespread sharing and participation espoused by traditional OSS, however some developer and task characteristics helped foster these ideals. Based on these and other findings, we develop a set of propositions and associated collaboration mechanisms that are important to future orgsOSS and other similarly structured software development projects.

Abstract. Landslides exhibit themselves in different mass movement processes and are considered among the most complex natural hazards occurring on the earth surface. Making landslide database available online via WWW (World Wide Web) promotes the spreading and reaching out of the landslide information to all the stakeholders. The aim of this research is to present a comprehensive database for generating landslide hazard scenario with the help of available historic records of landslides and geo-environmental factors and make them available over the Web using geospatial Free &amp;amp; Open Source Software (FOSS). FOSS reduces the cost of the project drastically as proprietary software's are very costly. Landslide data generated for the period 1982 to 2009 were compiled along the national highway road corridor in Indian Himalayas. All the geo-environmental datasets along with the landslide susceptibility map were served through WEBGIS client interface. Open source University of Minnesota (UMN) mapserver was used as GIS server software for developing web enabled landslide geospatial database. PHP/Mapscript server-side application serve as a front-end application and PostgreSQL with PostGIS extension serve as a backend application for the web enabled landslide spatio-temporal databases. This dynamic virtual visualization process through a web platform brings an insight into the understanding of the landslides and the resulting damage closer to the affected people and user community. The landslide susceptibility dataset is also made available as an Open Geospatial Consortium (OGC) Web Feature Service (WFS) which can be accessed through any OGC compliant open source or proprietary GIS Software.

Nowadays, Open Source Software (OSS) is widely used and plays a crucial role in the software industry. OSS development is a knowledge-intensive activity that requires very high levels of domain knowledge and needs to maintain the knowledge sharing environment. OSS project develop by the contribution of OSS members on its virtual community where every member can communicate and develop software together. To create new open source software needs the motivation of all members, the resources embedded in the relationship in community and the coordination of members as a virtual team to complete the OSS tasks. This study focused on the knowledge sharing in the OSS project community under the individual motivation, virtual community and virtual team perspectives. We analyzed 304 surveys collected from OSS communities and found that the extrinsic motivation, some perspectives of virtual community such as social interaction, identification and perspective of virtual team – team cognition have a direct impact on knowledge sharing of OSS project community. The study found that all the perspectives of virtual community have a significant impact on team cognition, and therefore have indirect effect on the knowledge sharing in OSS. Moreover, our results indicated that knowledge sharing has a significant impact on project performance. Implications for theory building, practical management and future research are also discussed.

Shared understandings are important for software development as they guide effective individual contributions and coordination of the software development process. However, it is not clear if such understandings can be developed in highly distributed groups that do not regularly meet face-to-face. In this paper, we present the results of a preliminary analysis of shared mental models within a Free/Libre Open Source Software (FLOSS) development team. We analyzed mental models using cognitive mapping and process analysis and compared the models of four developers from the Apache Lucene Java project. Our analysis suggests that there is a high level of sharing among core developers but the sharing is not complete, with some differences related to tenure and role in the project. Finally, we suggest directions for further research on shared mental models in FLOSS teams.