How is open source affecting software development?

Spinellis, Diomidis; Szyperski, Clemens

doi:10.1109/ms.2004.1259204

Cited by 98 publications

(64 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Nevertheless, there are very few empirical studies addressing release management in open source software development [5,10]. This is unfortunate since many lessons can be learned from open source software communities [11][12][13]. After all, the freedom to study socio-technical aspect of software development contrasts open source software from the proprietary model where access to the software development team is only granted to a few.…”

Section: Introductionmentioning

confidence: 99%

Release Early, Release Often and Release on Time. An Empirical Case Study of Release Management

Teixeira

2017

Open Source Systems: Towards Robust Practices

View full text Add to dashboard Cite

Abstract. The dictum of "Release early, release often." by Eric Raymond as the Linux modus operandi highlights the importance of release management in open source software development. Nevertheless, there are very few empirical studies addressing release management in open source software development. It is already known that most open source software communities adopt either feature-based or time-based release strategies. Each of these has its advantages and disadvantages that are context-specific. Recent research reported that many prominent open source software projects have moved from feature-based to timebased releases. In this longitudinal case study, we narrate how OpenStack shifted towards a liberal six-month release cycle. If prior research discussed why projects should adopt time-based releases and how they can adopt such a strategy, we discuss how OpenStack adapted its software development processes, its organizational design and its tools toward a hybrid release management strategy -a strive for balancing the benefits and drawbacks of feature-based and time-based release strategies.

show abstract

Section: Introductionmentioning

confidence: 99%

Release Early, Release Often and Release on Time. An Empirical Case Study of Release Management

Teixeira

2017

Open Source Systems: Towards Robust Practices

View full text Add to dashboard Cite

show abstract

“…The deriving evolutionary pressure requires the system design and architecture to have enhanced quality factors: in particular, they have to retain the (user perceived as well as system-intrinsic) dependability at a satisfactory level and make component installation/removal operations less haphazard [2].…”

Section: Introductionmentioning

confidence: 99%

“…Packages define the granularity at which components are managed (installed, removed, upgraded to newer version, etc.) using package manager applications, such as APT 1 or Apache maven 2 . Furthermore, the system openness affords an anarchic array of dependency modalities between the adopted packages.…”

Section: Introductionmentioning

confidence: 99%

A Model Driven Approach to Upgrade Package-Based Software Systems

Cicchetti

Ruscio

Pierantonio

et al. 2010

Communications in Computer and Information Science

View full text Add to dashboard Cite

Abstract. Complex software systems are often based on the abstraction of package, brought to popularity by Free and Open Source Software (FOSS) distributions. While helpful as an encapsulation layer, packages do not solve all problems of deployment, and more generally of management, of large software collections. In particular upgrades, which can affect several packages at once due to interpackage dependencies, often fail and do not hold good transactional properties. This paper shows how to apply model driven techniques to describe and manage software upgrades of FOSS distributions. It is discussed how to model static and dynamic aspects of package upgrades-the latter being the more challenging to deal with-in order to be able to predict common causes of upgrade failures and undo residual effects of failed or undesired upgrades.

show abstract

“…The literature on OSS has been focused on several topics related to the successful OSS development (Perkings 1999, Trung et al 2005, Henkel 2006), motivation of programmers and developers (Bonaccorsi and Rossi 2003, Hertel et al 2003, Wu and Tsang, 2008, the benefits of OSS (Kogut and Metiu 2001, Spinellis and Szyperski 2004, Spinellis 2006) and its implications for the public sector (Applewhite 2003), or public domain licensing (Valimaki andOksanen 2005, Gambardella and. This article will be focused on successful OSS development, but instead of analysing the development in terms of the source code produced, we will focus on the social relationships among virtual community members.…”

Section: Introductionmentioning

confidence: 99%

Virtual communities as a resource for the development of OSS projects: the case of Linux ports to embedded processors

Toral

Torres

Barrero

2009

Behaviour & Information Technology

View full text Add to dashboard Cite

Open source software (OSS) projects represent a new paradigm of software creation and development based on hundreds or even thousands of developers and users organised in the form of a virtual community. The success of an OSS project is closely linked to the successful organisation and development of the virtual community of support. The main objective of this article is to analyse the activity of virtual communities. Social network analysis is employed to analyse Linux ports to embedded processors as a case study to achieve this aim. The obtained results confirm the necessity of structuring the virtual community with a selection of active developers and core members to promote community activity and attract peripheral users, expanding the impact of the underlying software. The obtained result will be useful for the software industry migrating to the open source software paradigm.

show abstract

How is open source affecting software development?

Cited by 98 publications

References 1 publication

Release Early, Release Often and Release on Time. An Empirical Case Study of Release Management

Release Early, Release Often and Release on Time. An Empirical Case Study of Release Management

A Model Driven Approach to Upgrade Package-Based Software Systems

Virtual communities as a resource for the development of OSS projects: the case of Linux ports to embedded processors

Contact Info

Product

Resources

About