
Open Source Systems: Enterprise Software and Solutions
Description
Alles über E-Books | Antworten auf Fragen rund um E-Books, Kopierschutz und Dateiformate finden Sie in unserem Info- & Hilfebereich.
The 14 revised full papers and 2 short papers presented were carefully reviewed and selected from 38 submissions. The papers cover a wide range of topics in the field of free/libre open source software (FLOSS) and are organized in the following thematic sections: organizational aspects of OSS projects, OSS projects validity, mining OSS data, OSS in public administration, OSS governance, and OSS reusability.
More details
Other editions
Additional editions

Content
- Intro
- General Chair's Message
- Program Chairs' Message
- Preface
- Organizational Aspects of OSS Projects
- OSS Project Validity
- Mining OSS Data
- OSS in Public Administration
- OSS Governance
- OSS Reusability
- Organization
- Contents
- Organizational Aspects of OSS Projects
- How Can Open Source Software Projects Be Compared with Organizations?
- Abstract
- 1 Introduction
- 2 The Elements of an Organization
- 3 Organizational Framework of OSS Projects
- 3.1 People
- 3.2 Organization
- 3.3 Assets
- 4 Discussion
- References
- FLOSS Project Management in Government-Academia Collaboration
- 1 Introduction
- 2 Related Work
- 3 Research Design
- 3.1 The Case Study
- 3.2 Survey, Interview and Data Collection
- 4 Results
- 5 Discussion
- 6 Conclusion
- References
- Insights into the Trilateral Relationship of Crowdfunding Campaigns, Open Source and Communities
- 1 Introduction
- 2 Background
- 2.1 Crowdfunding
- 2.2 Communities
- 2.3 Doing Business with Open Source
- 2.4 Previous Studies
- 3 Research Questions and Methodology
- 4 Results and Analysis
- 4.1 Characteristics
- 4.2 Relationship
- 4.3 Impact
- 5 Validity Threats
- 6 Conclusion
- References
- OSS Projects Validity
- Open Source Software Resilience Framework
- 1 Background
- 2 City Resilience Framework
- 2.1 City Resilience Index
- 3 Adaptation of City Resilience Index to Open Source Software
- 3.1 Open Source Software Resilience Framework (OSSRF)
- 4 Open Source Software Resilience Framework Application
- 4.1 OKapi - A Non Resilient Project
- 4.2 WooCommerce - A Resilient Project
- 5 Threats to Validity
- 6 Conclusions and Future Work
- References
- Leaving Behind the Software History When Transitioning to Open Source: Reasons and Implications
- 1 Introduction
- 2 Method
- 2.1 Research Questions
- 2.2 Studied Projects
- 2.3 Survey
- 3 RQ1: Why Some Projects Do Not Open the Software History?
- 4 RQ2: What Are the Challenges Associated with the Lack of Software History?
- 5 Implications and Limitations
- 5.1 Implications
- 5.2 Limitations
- 6 Related Work
- 7 Conclusion
- References
- Developer Dynamics and Syntactic Quality of Commit Messages in OSS Projects
- Abstract
- 1 Introduction
- 2 Related Work
- 3 The Proposed Model and Its Validation
- 4 Data Collection
- 5 Result and Analysis
- 5.1 Does the Number of Contributors Affect the Commit Message Syntactic Quality?
- 5.2 Understanding the Contribution Pattern
- 6 Limitations of the Study
- 7 Conclusions and Future Work
- References
- Mining OSS Data
- Process Mining for Process Conformance Checking in an OSS Project: An Empirical Research
- Abstract
- 1 Introduction
- 2 Background Work
- 2.1 Bugzilla
- 2.2 Koha Open Source Integrated Library System
- 2.3 Research Question
- 3 Methodology
- 3.1 Locate Relevant Data
- 3.2 Data Preparation
- 3.3 Clean Data
- 4 Findings
- 4.1 Process Mining
- 4.2 Process Conformance Check
- 5 Discussion and Future Work
- References
- Ranking Source Code Static Analysis Warnings for Continuous Monitoring of FLOSS Repositories
- 1 Introduction
- 2 Related Work
- 3 Continuous Static Analysis with kiskadee
- 4 Ranking Warnings
- 5 Results and Discussion
- 6 Conclusion
- References
- Using PageRank to Reveal Relevant Issues to Support Decision-Making on Open Source Projects
- 1 Introduction
- 2 Background
- 2.1 The Software Issue Model
- 2.2 The PageRank Algorithm
- 3 Using PageRank to Reveal Relevant Software Issues
- 4 Evaluation
- 5 Threats to Validity
- 6 Conclusion
- References
- OSS in Public Administration
- Creating and Integrating a FLOSS Product into UK Law Enforcement
- Abstract
- 1 Introduction
- 2 Background
- 2.1 Open Source Research
- 2.2 Toolkit Standardization
- 2.3 OSIRT
- 2.4 FLOSS Integration into UK Public Services
- 3 Methodology
- 3.1 Interviews
- 3.2 General Questionnaires
- 4 Results and Discussion
- 4.1 Case Study Interviews
- 4.2 OSIRT Interviews and Questionnaires
- 5 Reflection
- 6 Conclusion
- References
- Possibilities of Use of Free and Open Source Software in the Greek Local Authorities
- Abstract
- 1 Introduction
- 2 Information Gathering and Computational Details
- 2.1 Questionnaire Creation
- 2.2 Questionnaire Creation
- 2.3 Contact Establishment
- 3 Results and Discussion
- 3.1 Participation and Statistics
- 3.2 Absolute Numbers and Cost Calculations for Workstations
- 3.3 Absolute Numbers and Cost Calculations for Backbone Infrastructure
- 3.4 Cloud Computing in the Municipalities
- 3.5 Free and Open Source Software (FOSS) in the Municipalities
- 3.6 Software Support Plans
- 4 Proposals that Include Foss and Usage of Modern Technologies
- 4.1 Operating Systems and Commonly Used Software
- 4.2 Purposeful Software
- 4.3 Server Operating Systems and Software
- 4.4 Cloud Computing Utilization Possibilities
- 5 Conclusions
- References
- Mining and Linking Open Economic Data from Governmental Communities
- Abstract
- 1 Introduction
- 2 Our Proposed Model
- 3 Application Case Study: Greek Public Procurement
- 4 Conclusions
- Acknowledgments
- Acknowledgments
- References
- OSS Governance
- Understanding Industry Requirements for FLOSS Governance Tools
- Abstract
- 1 Introduction
- 2 Related Work
- 3 Research Method
- 3.1 Theoretical Sampling
- 3.2 Data Gathering and Analysis
- 4 Research Results
- 4.1 Theory of Industry Requirements for FLOSS Governance Tools
- 4.2 Evaluation
- 5 Discussion
- 6 Research Limitations
- 7 Conclusion
- Acknowledgments
- References
- OSS Reusability
- Building a Social Platform Using FLOSS to Support Collaborative Communities: The ReWeee Case Study
- 1 Introduction
- 2 Project Requirements
- 3 Satisfying Project Requirements with FLOSS
- 3.1 Django Framework
- 3.2 Extending Django User Model
- 3.3 Supporting Periodic Tasks
- 3.4 Reusable Applications with Minor Changes
- 3.5 Developed Applications
- 3.6 Discussion
- 4 Conclusions
- References
- Improving C/C++ Open Source Software Discoverability by Utilizing Rust and Node.js Ecosystems
- Abstract
- 1 Introduction
- 2 Background and Motivation
- 2.1 JavaScript in Open Source Projects
- 2.2 Challenges in C/C++ OSS
- 2.3 Rust: A Young Contender in OSS
- 2.4 Compilation to JavaScript and WebAssembly
- 3 Exposing C/C++ OSS via Rust and Node.js
- 3.1 Using Rust to Package and Publish on crates.io
- 3.2 Using Node.js to Package and Publish on npm
- 3.3 The Hypothetical Park-Miller-Carta PRNG Case
- 4 Results and Discussion
- 4.1 Discoverability Improvement
- 4.2 Code Quality Control
- 4.3 Performance Degradation
- 4.4 Code Portability
- 5 Conclusions and Future Work
- References
- Author Index
System requirements
File format: PDF
Copy protection: Watermark-DRM (Digital Rights Management)
System requirements:
- Computer (Windows; MacOS X; Linux): Use the free software Adobe Reader, Adobe Digital Editions, or any other PDF viewer of your choice (see eBook Help).
- Tablet/Smartphone (Android; iOS): Install the free app Adobe Digital Editions or another reading app for eBooks, e.g., PocketBook (see eBook Help).
- E-reader: Bookeen, Kobo, Pocketbook, Sony, Tolino and many more (only limited: Kindle).
The file format PDF always displays a book page identically on any hardware. This makes PDF suitable for complex layouts such as those used in textbooks and reference books (images, tables, columns, footnotes). Unfortunately, on the small screens of e-readers or smartphones, PDFs are rather annoying, requiring too much scrolling.
This eBook uses Watermark-DRM, a „soft” copy protection. This means that there are no technical restrictions to prevent illegal distribution. However, there is a personalised watermark embedded in the eBook that can be used to identify the purchaser of the eBook in the event of misuse and to provide evidence for legal purposes.
For more information, see our eBook Help page.