A Core-Periphery-Legality Architectural Style for Open Source System Development

Lokhman, Alexander; Mikkonen, Tommi; Hammouda, Imed; Kazman, Rick; Chen, Hongmei

doi:10.1109/hicss.2013.34

Cited by 5 publications

(6 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Distributed version control systems have enabled the development through pulling code from repositories to create software locally as a combination of several code sources. The range of components from operating and windowing systems to tiny, almost self-evident snippets have made open source systems an integral part of systems [22], many of which we do not consider as open source, and these are also visible in software architecture of many systems [23].…”

Section: Why the Cathedral Embraced The Bazaar?mentioning

confidence: 99%

How the Cathedral Embraced the Bazaar, and the Bazaar Became a Cathedral

Kilamo

Lenarduzzi

Ahoniemi³

et al. 2020

IFIP Advances in Information and Communication Technology

Self Cite

View full text Add to dashboard Cite

Over the past 20 years, open source has become a widely adopted approach to develop software. Code repositories provide software to power cars, phones, and other things that are considered proprietary. In parallel, proprietary development has evolved from rigid, centralized waterfall approaches to agile, iterative development. In this paper, we share our experiences regarding this co-evolution of open and closed source from the viewpoints of tools, practices, and organizing the development work, concluding that today's bazaars and cathedrals have much more common characteristics than those that separate them.

show abstract

Section: Why the Cathedral Embraced The Bazaar?mentioning

confidence: 99%

How the Cathedral Embraced the Bazaar, and the Bazaar Became a Cathedral

Kilamo

Lenarduzzi

Ahoniemi³

et al. 2020

IFIP Advances in Information and Communication Technology

Self Cite

View full text Add to dashboard Cite

show abstract

“…Because each component can be separately edited by a different set of developers, this approach is commonly used in many open source systems, where the development effort is distributed in ultra-wide scale. When pushing this approach to the extreme, a pattern called Core-Periphery ( Figure 1) has been proposed [8]. This pattern employs a single, small, extensible core -which is typically highly coupled -surrounded by a much larger periphery, which typically exhibits low coupling.…”

Section: Introductionmentioning

confidence: 99%

Elements for a cloud-based development environment

Mikkonen

Nieminen

2012

Proceedings of the WICSA/ECSA 2012 Companion Volume

Self Cite

View full text Add to dashboard Cite

In almost any other field than software development, the World Wide Web, or simply the Web has revolutionized collaboration by providing a platform for cooperative applications and services. In contrast, so far revision control, also referred to as version management, has been the key technology for enabling collaborative software development. However, even today it is feasible to build a cooperative development environment that runs in a cloud, following the spirit of Google Docs, where developers can cooperate in real time. In this paper, we take a step beyond from the design of the technical artifact that allows collaborative coding, and consider the consequences of such an approach to software development in a more general sense, in particular from the perspective of version management. The goal is to integrate collaborative development with traditional facilities commonly associated with software engineering. This in turn will lead to a development approach where new opportunities complement tools that are known to work and provide a lot of added value in software development.

show abstract

“…Consider the difference between the Lesser General Public License (LGPL; gnu.org/copyleft/lesser.html) and the GPL license (gnu.org/licenses/gpl.html). For code under the LGPL, the user is permitted to link it dynamically to other components without violating or enforcing the LGPL (Lokhman et al, 2013). In contrast, this same scenario with the GPL requires a separate executable if the software code is not being released.…”

Section: Open Source Licensing Influencing Architecturementioning

confidence: 99%

“…Most licenses are reciprocal licenses meaning they force all derived works to be licensed under the same license associated with the original copy of the component (Link, 2011 (Lokhman et al, 2013). For instance, a package that is licensed with Apache 2.0 is not compatible with GPL 1.0.…”

Section: Ahmed Shah Selman Selman and Ibrahim Abualhaolmentioning

confidence: 99%

“…Depending on developer intentions, either to distribute derived work or publish their work while maintaining copyright ownership, open source legality and licensing issues must be faced. One approach, used by the Linux kernel, is the "coreperiphery pattern" (Lokhman et al, 2013). The core of the Linux kernel owns the copyright for the core system, while applications built around this system (i.e., on the periphery) can be replaced with different applications to allow any number of versions, or distributions, of Linux to be created for different purposes and systems.…”

Section: Open Source Licensing Influencing Architecturementioning

confidence: 99%

See 1 more Smart Citation