scholarly journals ENTANGLED AUTONOMY ON AUTOMATED AIRWAVES: THE CASE OF RIVENDELL

Author(s):  
Andy Kelleher Stuhl

Rivendell, a free and open source software suite for automated radio broadcasting, has brought several groups with clashing stances on technology, communication, and cultural politics into cooperation. This paper treats Rivendell as an opening onto the politics at play when the liberal ethos propelling free and open source software (Coleman, 2013) meets the autonomy-prizing traditions of independent broadcasting within an automation system. Complicating this already tense juncture, Rivendell has drawn users and code contributors from drastically opposed political groups within American broadcastings—right-wing Christian talk radio networks and progressive community stations—and has sustained a difficult terrain of working compromise that the activist push for low-power FM broadcasting inaugurated (Dunbar-Hester, 2014). In this paper, analysis of Rivendell's open source code base sheds light on its development and helps connect it to longer histories of media automation and its attendant social frictions. Interviews with lead Rivendell developers complete the picture of the project's trajectory, of its relation to the religious right context where the project began, and of the negotiations that have played out among its developers and its community of users in terrestrial and internet radio. The ongoing compromises and tensions threaded through Rivendell can offer insight into an issue that becomes larger and more pressing as media become increasingly complex and networked: how artists, activists, and media technologists who prioritize independence have reckoned with their reliance on socio-technical infrastructures whose connections may strike them as far less than savory.

2011 ◽  
Vol 3 (2) ◽  
pp. 43-78 ◽  
Author(s):  
M.M. Mahbubul Syeed ◽  
Timo Aaltonen ◽  
Imed Hammouda ◽  
Tarja Systä

Open Source Software (OSS) is currently a widely adopted approach to developing and distributing software. OSS code adoption requires an understanding of the structure of the code base. For a deeper understanding of the maintenance, bug fixing and development activities, the structure of the developer community also needs to be understood, especially the relations between the code and community structures. This, in turn, is essential for the development and maintenance of software containing OSS code. This paper proposes a method and support tool for exploring the relations of the code base and community structures of OSS projects. The method and proposed tool, Binoculars, rely on generic and reusable query operations, formal definitions of which are given in the paper. The authors demonstrate the applicability of Binoculars with two examples. The authors analyze a well-known and active open source project, FFMpeg, and the open source version of the IaaS cloud computing project Eucalyptus.


2017 ◽  
Author(s):  
Johan Dahlberg ◽  
Johan Hermansson ◽  
Steinar Sturlaugsson ◽  
Pontus Larsson

AbstractArteria is an automation system aimed at sequencing core facilities. It is built on existing open source technologies, with a modular design allowing for a community-driven effort to create plug-and-play micro-services. Herein we describe the Arteria system and elaborate on the underlying conceptual framework. The Arteria system breaks down into three conceptual levels; orchestration, process and execution. At the orchestration level it utilizes an event-based model of automation. It models processes, e.g. the steps involved in processing sequencing data, as workflows and executes these in a micro-service based environment. This creates a system which is both flexible and scalable. The Arteria Project code is available as open source software at http://www.github.com/arteria-project.


Author(s):  
M.M. Mahbubul Syeed ◽  
Timo Aaltonen ◽  
Imed Hammouda ◽  
Tarja Systä

Open Source Software (OSS) is currently a widely adopted approach to developing and distributing software. OSS code adoption requires an understanding of the structure of the code base. For a deeper understanding of the maintenance, bug fixing and development activities, the structure of the developer community also needs to be understood, especially the relations between the code and community structures. This, in turn, is essential for the development and maintenance of software containing OSS code. This paper proposes a method and support tool for exploring the relations of the code base and community structures of OSS projects. The method and proposed tool, Binoculars, rely on generic and reusable query operations, formal definitions of which are given in the paper. The authors demonstrate the applicability of Binoculars with two examples. The authors analyze a well-known and active open source project, FFMpeg, and the open source version of the IaaS cloud computing project Eucalyptus.


Author(s):  
Falko Glöckler ◽  
James Macklin ◽  
David Shorthouse ◽  
Christian Bölling ◽  
Satpal Bilkhu ◽  
...  

The DINA Consortium (DINA = “DIgital information system for NAtural history data”, https://dina-project.net) is a framework for like-minded practitioners of natural history collections to collaborate on the development of distributed, open source software that empowers and sustains collections management. Target collections include zoology, botany, mycology, geology, paleontology, and living collections. The DINA software will also permit the compilation of biodiversity inventories and will robustly support both observation and molecular data. The DINA Consortium focuses on an open source software philosophy and on community-driven open development. Contributors share their development resources and expertise for the benefit of all participants. The DINA System is explicitly designed as a loosely coupled set of web-enabled modules. At its core, this modular ecosystem includes strict guidelines for the structure of Web application programming interfaces (APIs), which guarantees the interoperability of all components (https://github.com/DINA-Web). Important to the DINA philosophy is that users (e.g., collection managers, curators) be actively engaged in an agile development process. This ensures that the product is pleasing for everyday use, includes efficient yet flexible workflows, and implements best practices in specimen data capture and management. There are three options for developing a DINA module: create a new module compliant with the specifications (Fig. 1), modify an existing code-base to attain compliance (Fig. 2), or wrap a compliant API around existing code that cannot be or may not be modified (e.g., infeasible, dependencies on other systems, closed code) (Fig. 3). create a new module compliant with the specifications (Fig. 1), modify an existing code-base to attain compliance (Fig. 2), or wrap a compliant API around existing code that cannot be or may not be modified (e.g., infeasible, dependencies on other systems, closed code) (Fig. 3). All three of these scenarios have been applied in the modules recently developed: a module for molecular data (SeqDB), modules for multimedia, documents and agents data and a service module for printing labels and reports: The SeqDB collection management and molecular tracking system (Bilkhu et al. 2017) has evolved through two of these scenarios. Originally, the required architectural changes were going to be added into the codebase, but after some time, the development team recognised that the technical debt inherent in the project wasn’t worth the effort of modification and refactoring. Instead a new codebase was created bringing forward the best parts of the system oriented around the molecular data model for Sanger Sequencing and Next Generation Sequencing (NGS) workflows. In the case of the Multimedia and Document Store module and the Agents module, a brand new codebase was established whose technology choices were aligned with the DINA vision. These two modules have been created from fundamental use cases for collection management and digitization workflows and will continue to evolve as more modules come online and broaden their scope. The DINA Labels & Reporting module is a generic service for transforming data in arbitrary printable layouts based on customizable templates. In order to use the module in combination with data managed in collection management software Specify (http://specifysoftware.org) for printing labels of collection objects, we wrapped the Specify 7 API with a DINA-compliant API layer called the “DINA Specify Broker”. This allows for using the easy-to-use web-based template engine within the DINA Labels & Reports module without changing Specify’s codebase. In our presentation we will explain the DINA development philosophy and will outline benefits for different stakeholders who directly or indirectly use collections data and related research data in their daily workflows. We will also highlight opportunities for joining the DINA Consortium and how to best engage with members of DINA who share their expertise in natural science, biodiversity informatics and geoinformatics.


Author(s):  
Passakorn PHANNACHITTA ◽  
Akinori IHARA ◽  
Pijak JIRAPIWONG ◽  
Masao OHIRA ◽  
Ken-ichi MATSUMOTO

Sign in / Sign up

Export Citation Format

Share Document