This article discusses the motivation for, history of, and capabilities of Fac-Back-OPAC, an alternative library catalogue built on open source technology.

One of the major problems facing schools in South Africa is the difficulty in obtaining modern, up-to-date computer facilities. This paper looks at the use of open source solutions in two government schools in South Africa to demonstrate that it is possible for schools to utilise almost any existing computer to provide effective network solutions.

Techn. Univ., Diplomarbeit, --Zugl.: Dresden, 2005.

<p>Denna rapport visar hur ett företag kan gå tillväga för att sammanställa utvecklingen av proprietär tillägg till öppen källkod. Rapporten presenterar en strategi för hantering av extern källkod. Examensarbetet har utförts på Ericsson AB i Linköping och har gått ut på att sammanställa deras internutveckling av protokollavkodare till Wireshark. I rapporten presenteras hur ett program som licensierats under öppen källkod kan utvärderas. Vidare ges en kort introduktion till de legala grunderna för öppen källkod. Rapporten tar även upp de risker som kan associeras med öppen källkod. Examensarbetet resulterade praktiskt i ett system som sammanställde Ericssons internutveckling av proprietär tillägg till öppen källkod.</p>

In this study, I design an empirical open source software selection process, which reuses some ideas from Commercial Off-the-Shelf selection methods and addresses the characteristics of the open source software. Basically, it consists of three basic steps: identification, screening and evaluation. The identification step is to find all possible alternatives to open source software that can meet the high level requirements. The next step is screening, in which the refined requirements are applied to filter the alternatives. The evaluation step is based on the Analytic Hierarchy Process, in which the alternatives are inspected from functional suitability, source code, support strength and popularity. In more detail, under functionality suitability criterion, alternatives to open source software are evaluated in viewing of how much functionality can fit in with the functional user requirements. The source code of the alternatives is evaluated from six criteria: programming language, code size, code comment, code intra-module complexity and code inter-module complexity. The evaluation of support strength depends on the evaluation of field support and support resources. The field support includes commercial support and community support. The community support specifically refers to the direct responses from the community to the support requests. Aside from field support, open source software projects also provide various support-related resources such as, documents, wiki, blog, etc. To determine the popularity of the alternatives, I evaluate them from software use, development participation and web popularity. In the case study, I utilize the process to select the best open source unified modeling language tool from the ten alternatives for the software development process. After the screening phase, the four competitive alternatives, BOUML, ArgoUML, UMLet and Violet, are evaluated from functionality, source code, support strength and popularity criteria. The evaluation result indicates that ArgoUML is the best tool for the requirement. The case study demonstrates the effectiveness of the selection process. Various important attributes of open source software are taken into consideration systematically and the final decision is reached based on comprehensive investigation and analysis. The process provides an operable solution to the open source selection problem in practice.

In recent years, the development of software in open source communities has attracted immense attention from research and practice. The idea of commercial quality, free software, and open source code accelerated the development of well-designed open source software such as Linux, Apache tools, or Perl. Intrinsic motivation, group identification processes, learning, and career concerns are the key drivers for a successful cooperation among the participants. These factors and most mechanisms of control, coordination, and monitoring forms of open source communities can hardly be explained by traditional organizational theories. In particular, the micro and macro structures of open source communities and their mode of operation are hardly compatible with the central assumption of the New Institutional Theory, like opportunistic behavior. The aim of this contribution is to identify factors that sustain the motivation of the community members over the entire life cycle of an open source project. Adequate coordination and controlling mechanisms for the governance in open source communities may be extracted.

In this thesis, I address the problem and promise of decentralization, in the context of standard-setting for physical systems. I explore how the process of the decentralization of power works in the context of physical information, in three subsets:the relationship between existing standards and the decentralized control of physical information; how hands-on experimentation helps to shed light on the decentralized control of physical information; and how existing Free/Libre Open Source Software culture addresses the decentralized control of physical information.

In this thesis, I address the problem and promise of decentralization, in the context of standard-setting for physical systems. I explore how the process of the decentralization of power works in the context of physical information, in three subsets:the relationship between existing standards and the decentralized control of physical information; how hands-on experimentation helps to shed light on the decentralized control of physical information; and how existing Free/Libre Open Source Software culture addresses the decentralized control of physical information.

In this study, I design an empirical open source software selection process, which reuses some ideas from Commercial Off-the-Shelf selection methods and addresses the characteristics of the open source software. Basically, it consists of three basic steps: identification, screening and evaluation. The identification step is to find all possible alternatives to open source software that can meet the high level requirements. The next step is screening, in which the refined requirements are applied to filter the alternatives. The evaluation step is based on the Analytic Hierarchy Process, in which the alternatives are inspected from functional suitability, source code, support strength and popularity. In more detail, under functionality suitability criterion, alternatives to open source software are evaluated in viewing of how much functionality can fit in with the functional user requirements. The source code of the alternatives is evaluated from six criteria: programming language, code size, code comment, code intra-module complexity and code inter-module complexity. The evaluation of support strength depends on the evaluation of field support and support resources. The field support includes commercial support and community support. The community support specifically refers to the direct responses from the community to the support requests. Aside from field support, open source software projects also provide various support-related resources such as, documents, wiki, blog, etc. To determine the popularity of the alternatives, I evaluate them from software use, development participation and web popularity. In the case study, I utilize the process to select the best open source unified modeling language tool from the ten alternatives for the software development process. After the screening phase, the four competitive alternatives, BOUML, ArgoUML, UMLet and Violet, are evaluated from functionality, source code, support strength and popularity criteria. The evaluation result indicates that ArgoUML is the best tool for the requirement. The case study demonstrates the effectiveness of the selection process. Various important attributes of open source software are taken into consideration systematically and the final decision is reached based on comprehensive investigation and analysis. The process provides an operable solution to the open source selection problem in practice.

ITC/USA 2013 Conference Proceedings / The Forty-Ninth Annual International Telemetering Conference and Technical Exhibition / October 21-24, 2013 / Bally's Hotel & Convention Center, Las Vegas, NV / Applications that use TMATS benefit from the ability to presume that the TMATS data is well constructed. This need is met by a TMATS validator. Some classified systems need source code rather than an executable to avoid expensive testing before being allowed in. An Open Source Validator is proposed, presented and made available to the public. Major points and difficulties are discussed. The source is available in a Visual Studio 2008 project here: www.bkelly.ws/irig/validator.html A bulletin board for TMATS / Chapter 10 discussion is here: http://www.bkelly.ws/irig_106/