Open Source Software Product Lines

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.

Open-source software abbreviated as OSS is computer software that is available with source code and is provided under a software license that permits users to study, change, and improve the software. For the commercial software the source code and certain other rights are normally reserved for copyright holders,i.e. the company who developes the software. A group of people in a collaborative manner often developes the Open source software, not under the roof of a large organization. This strategy makes open source software cheap, reliable and modifiable if needed. In this context we shall discuss mainly the features of Open Source Software, differences of open source and free software and open source software movement in Indian perspective.

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

This book presents a dense and intricate journey into the world of hacking with a specific focus on the Free and Open Source Software (FOSS) movement. Soderberg embeds the FOSS model in a distinctl...

Software product line (PL) engineering has been established in the last decade as a proven way to build flexibility and reusability into software systems. This approach is centred around the idea that the initial investments made in the development of reusable artefacts are outweighed by the quality and product improvements gained through the reuse of such artefacts. While there are many studies on introducing PL engineering into software development and calculating expected value upfront, there is little documented evidence of long-term experiences with PL engineering. This paper examines perceptions of the value of PL engineering for three PL of different ages. The paper confirms that, while PL engineering enhances product value and quality through shared components and architecture, this is also the predominant limitation of PL engineering. Furthermore, our investigations show that while perceptions of product quality differ depending on PL maturity, this is not the case for time-to-market and cost.

Tools and artifacts produced by open source software (OSS) have been woven into the foundation of the technology industry. To keep this foundation intact, the open source community needs to actively invest in sustainable approaches to bring in new contributors and nurture existing ones. We take a first step at this by collaboratively designing a maintainer dashboard that provides recommendations on how to attract and retain open source contributors. For example, by highlighting project goals (e.g., a social good cause) to attract diverse contributors and mechanisms to acknowledge (e.g., a "rising contributor" badge) existing contributors. Next, we conduct a project-specific evaluation with maintainers to better understand use cases in which this tool will be most helpful at supporting their plans for growth. From analyzing feedback, we find recommendations to be useful at signaling projects as welcoming and providing gentle nudges for maintainers to proactively recognize emerging contributors. However, there are complexities to consider when designing recommendations such as the project current development state (e.g., deadlines, milestones, refactoring) and governance model. Finally, we distill our findings to share what the future of recommendations in open source looks like and how to make these recommendations most meaningful over time. LAY ABSTRACT Open Source Software (OSS) plays an important role in the development and maintenance of software products that are widely deployed in different domains from computer science to astrophysics and cut-ting edge medicines research. Chances are there is an open source project for anyone to contribute to. With the recent deployment of the popular Linux open source project on Mars even the sky is no limit. However, OSS projects largely depend on volunteers and attracting, retaining, and keeping contributors engaged is a severe challenge. In this paper, we present the design and evaluation of a dashboard to support community managers, such as maintainers, to track and acknowledge newcomers' contributions. With the support of tools such as ours, maintainers will be better prepared to attract and retain their emerging community.

In these recent years, several metaheuristic optimization algorithms have been developed to solve complex real-world problems. However, according to the no free lunch theorem, there is no metaheuristic algorithm which has the best suited for solving all optimization problems. Therefore, developing new metaheuristic algorithms is an open problem. Two major categories of metaheuristics are swarm intelligence and evolutionary algorithms. Both of them have their own advantages. In this paper, we present a naturally swarm and evolutionary algorithm in which its particles have memory, collaboration, information sharing, and competition inherited from one specific analogy. So, it has the advantages of both swarm and evolutionary algorithms without complications of hybridizing them. We formulate a new metaheuristic optimization algorithm called open source development model algorithm (ODMA) inspired by open source development model and communities, in such a way that each potential solution is considered as a software, and by evolution of the softwares, better solutions of the function that should be optimized are searched. The main operations of the algorithm include employing features and methods of leading softwares, evolution of leading softwares based on their history and forking from leading softwares. After a detailed formulation and explanation of its implementation, the algorithm is evaluated by $$17$$17 well-known benchmark functions, and the results are compared with PSO, ICA, and GA. The results show that ODMA outperforms GA, PSO, and ICA in terms of finding the global optimum and convergence.

The popularity of Open Source Software and the usage of Open Source Licenses has greatly increased in the last few years. While some years ago, working on an Open Source basis was merely done by some alternative programmers, Open Source Projects have by now become an established, efficient and cost-saving way of realizing difficult and extensive projects and a real competition to proprietary software. Open Source licenses have become interesting for software enterprises, too. Some companies recognised that the Open Source community on the internet may constitute a strong support for projects, if it is possible to create enthusiasm for a project within the community. A recent, well-known example is the new web browser publicised by Google, Chrome, which is based on Open Source Software. In some cases, it might also be attractive for a software company to sell services, warranties, addons or other valuable products related to an Open Source product, which itself is given away for free. In this connection, however, it has become an important topic for enterprises to what extent it is possible to commercially exploit the results of Open Source Projects. This commercial usability strongly depends on the Open Source license chosen for a certain project. Therefore, the people responsible for a project have to conduct a thorough analysis on which license to choose. As the most common licenses GPL (GNU Public License) and LGPL (Lesser GNU Public License) do not constitute an ideal solution in this regard. This article will, in particular, take a closer look at alternative licenses existing.

Software product family or line is a software engineering paradigm that systematizes reuse. In software product line engineering, two phases are distinguished: domain engineering which is in charge of developing a common infrastructure and assets and application engineering which makes use of those assets to generate the products. One of the key aspects of product lines is variability and its management. However, the main focus has been on functional variability and quality variability in software product lines has not received so much attention by researchers. In a product line different members of the line may require different levels of a quality requirement, for instance they could differ in terms of their availability, security, reliability, etc. Due to this variability, quality evaluation in software product lines is much more complicated that in single-systems. One alternative is to evaluate all the products of a line but it is very expensive and ways of reducing evaluation efforts are necessary. In this direction, the paper presents a method for facilitating cost-effective quality evaluation of a product line taking into consideration variability on quality attributes.

Open source communities bring together a dispersed collection of people, sometimes a large number of them, around the development of open source software. In the absence of enforceable formal structures, like those found in corporate settings, how are the activities of all these participants coordinated? From the outside looking in, it may seem that chaos and disorder rule. It is true that most decisions are made on an individual basis by the participants themselves. Nevertheless, work is coordinated successfully. We first discuss mechanisms that reduce the need for coordination— most notably by striving for modularity and elegance. We then turn to a number of mechanisms that provide coordination even under the difficult conditions that are present in open source communities. We conclude by outlining a number of potential steps for future research.

This report explains the challenges experienced as Overwatch Textron Systems transitioned to a software product line approach. Overwatch Textron Systems provides both software products and custom software development in the domain of intelligence planning, collection and analysis to the U.S. Government and its allies. This report: a) Describes the approach taken to transition Overwatch Textron Systems to a product line organization. b) Provides an overview of the Overwatch Textron Systems software product line; the Overwatch Intelligence Center. c) Describes the product line architecture that is key to the Overwatch Intelligence Center software product line. d) Provides a summary of the lessons learned during the transition.

Most research on open source software communities has focused on those that are community founded. More recently, firms have founded their own open source communities. How do sponsored open source communities differ from their autonomous counterparts? With comparative examination of 12 open source projects initiated by corporate sponsors, we identify three design parameters that together help form a participation architecture—the opportunity structure extended to potential external contributors. In exploring sponsors' community design decisions, we found that sponsored open source projects were more likely to offer transparency than they were accessibility and that this had implications for their communities' growth. We contribute theoretical constructs that offer a common basis of comparison for the future study of open source projects and illustrate how the tension between control and growth affects open source community design and creation.

A systematic mapping study on software product line evolution: From legacy system reengineering to product line refactoring

The popularity of open source has witnessed significant growth in the past two decades. The sustainability and success of open source projects rely heavily on the active community of contributors, who have the freedom to join or depart voluntarily. The churn of core developers can have detrimental effects on the continuous development and progress of these communities. Therefore, previous studies have aimed to identify the factors that influence developer churn and reveal its impact on open source communities. However, there is currently a lack of research on predicting whether a developer will leave or retain within a given timeframe. This article aims to bridge this gap by introducing a novel model called context-aware dynamic graph neural network (ConDyGNN), which is designed specifically for predicting developer churn in open source communities. By leveraging historical data, this model takes into consideration various factors such as developers’ activities, collaborative networks, and community context information. To capture both temporal dependencies and spatial correlations among different developers, temporal convolutional network (TCN) and graph convolutional network (GCN) modules are employed in <italic xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">ConDyGNN</i>. Furthermore, a context-aware module based on a multihead attention mechanism is proposed to effectively integrate macrolevel community information and enhance the predictive performance. The superiority of the proposed model is empirically demonstrated through extensive comparative experiments and an ablation study.

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