The future of continuous integration in GNOME

Walters, C.R.; Poo-Caamaño, Germán; Germán, Daniel M.

doi:10.1109/releng.2013.6607695

Cited by 3 publications

(4 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…These quality assurance activities are performed by a small group of developers, mainly the release team as who is in charge of continuous integration. In the words of a release team member, continuous integration is a necessity: OSTree [79] is a project that aims to address this issue by continuously building GNOME and providing a testable system ready to be downloaded and run. The release team uses it to build and test GNOME.…”

Section: Test the Gnome Releasementioning

confidence: 99%

“…We chose GNOME because it is a large and mature software ecosystem [49], it has been studied before [22,36,39,46,47,67,79], its official release is a single product comprised of many independent and distributed projects, and more important, it has a successful and stable release schedule: a new GNOME release is issued every six months. We studied the high level communication of the release management process across five releases.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Herding cats in a FOSS ecosystem: a tale of communication and coordination for release management

Poo-Caamaño

Knauss

Singer

et al. 2017

J Internet Serv Appl

Self Cite

View full text Add to dashboard Cite

Release management in large-scale software development projects requires significant communication and coordination. It is particularly challenging in Free and Open Source Software (FOSS) ecosystems, in which hundreds of loosely connected developers and their projects are coordinated to release software to a schedule. To better understand this process and its challenges, we analyzed over two and half years of communication in the GNOME ecosystem and studied developers' interactions. Through a case study, we cataloged communication channels, determined the main channel from which we categorized high level communication and coordination activities spanning five releases, and triangulated our results by interviewing ten key developers. We found that a release schedule, influence (instead of direct control), and diversity are the main factors that positively impact the release process in the GNOME ecosystem. We report a set of lessons learned that encapsulates our understanding of how the Release Management process function in a FOSS ecosystem, we learned that: (1) ensure that the release team follows the main communication channels used by developers, (2) provide a common place for coordination for an ecosystem, (3) consider including both good technical and social skills in a release team, (4) aim for a diverse release team, (5) based on lack of power, lobbying and consensus based management must be followed, (6) help the release team in the coordination process with a well defined schedule, and (7) release team work is different from regular software work. Our results can help organizations build better large-scale teams and show that research focused on individual projects might miss important parts of the picture.

show abstract

Section: Test the Gnome Releasementioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Herding cats in a FOSS ecosystem: a tale of communication and coordination for release management

Poo-Caamaño

Knauss

Singer

et al. 2017

J Internet Serv Appl

Self Cite

View full text Add to dashboard Cite

show abstract

“…OSTree [28] is a project that aims to address this issue by continuously building GNOME and providing a testable system ready to be downloaded and run. The Release Team uses it to build and test GNOME.…”

Section: What Are the Challenges That Release Managers Face In A Fossmentioning

confidence: 99%

“…GNOME is a FOSS project whose main goal is to create a platform to build applications for the desktop for Linux and Unix-like systems. We chose GNOME because it is a large and mature software ecosystem [18], it has been studied before [7,11,14,17,16,24,28], its official release is a single product comprised of many independent and distributed projects, and more important, it has a successful and stable release schedule: a new GNOME release is issued every 6 months. We studied the high level communication of the release management process across 5 releases.…”

Section: Introductionmentioning

confidence: 99%

Herding Cats: A Case Study of Release Management in an Open Collaboration Ecosystem

Poo-Caamaño

Singer

Knauss

et al. 2016

IFIP Advances in Information and Communication Technology

Self Cite

View full text Add to dashboard Cite

Part 1: Full PapersInternational audienceRelease management in large-scale software development projects requires significant communication and coordination. It is particularly challenging in Free and Open Source Software (FOSS) ecosystems, in which hundreds of loosely connected developers and their projects need to be coordinated to release software to a schedule. To better understand this process and its challenges, we analyzed over two and half years of communication in the GNOME ecosystem and studied developers’ interactions. We cataloged communication channels, categorized high level communication and coordination activities in one of them, and triangulated our results by interviewing developers. We found that a release schedule, influence instead of direct control, and diversity are factors that impact positively the release process in the GNOME ecosystem. Our results can help organizations build better large-scale teams and show that research focused on individual projects might miss important parts of the picture

show abstract

İnsani Yardım, Özgür ve Açık Kaynak Kodlu Yazılım Projeleri (İÖAKK)

Selçuk

Akıncı

Şeker

2021

İstanbul Sabahattin Zaim Üniversitesi Fen Bilimleri Enstitüsü Dergisi

View full text Add to dashboard Cite

İnsani yardım amacıyla açık kaynak kodlu yazılım platformları projelendirildiğinde biç ok topluma yararlı yazılım ve programlar ortaya çıkmaktadır. Engelliler için erişilebilirlik, afet durumlarında kriz yönetimi, sağlıkla ilgili vb konularda açık kaynak kodlu yazılıp platformları insani yardım amacıyla geliştirilebilir. Bu geliştirme sürecinde de üniversite öğrencilerinden yararlanılabilir. Üniversitelerin ilgili bölümünde okuyanlar için İÖAKK projeleri hem yazılım tecrübelerini ve mesleki bilgilerini geliştirme fırsatı hem de sosyalleşme ve toplumun çıkarları için iş yapma fırsatı sağlanmış olur. Bu çalışmada insani yardım amaçlı kullanılan AKK yazılım projelerinin dünyada nasıl şekillendiği ve gerek eğitim öğretim açısından ve gerekse toplum hizmeti açısından nasıl sonuçlar doğurduğu araştırılmıştır. İÖAKK projelerine üniversite öğrencilerinde katılması ile bazı ülkelerde destek sağlandığı ve çok iyi sonuçlar alındığı görülmüştür. Ülkemizde de benzeri girişim potansiyelinin olduğu göz önünde bulundurularak İÖAKK projelerinin mutlaka üniversite öğrencileri için fırsat haline getirilerek ülkemizde de arttırılması gerektiği sonucuna varılmıştır.

show abstract

The future of continuous integration in GNOME

Cited by 3 publications

References 4 publications

Herding cats in a FOSS ecosystem: a tale of communication and coordination for release management

Herding cats in a FOSS ecosystem: a tale of communication and coordination for release management

Herding Cats: A Case Study of Release Management in an Open Collaboration Ecosystem

İnsani Yardım, Özgür ve Açık Kaynak Kodlu Yazılım Projeleri (İÖAKK)

Contact Info

Product

Resources

About