Categorizing bugs with social networks: A case study on four open source software communities

O desenvolvimento de software é uma atividade intensive em esforço humano. Assim, a forma como os desenvolvedores encaram suas tarefas é de suam importância. Em um ambiente como o usual em projetos de FOSS (free/open source software) em que profissionais (desenvolvedores pagos) compartilham os esforços de desenvolvimento com voluntários, a moral da comunidade de desenvolvedores e usuários é fundamental. Neste artigo, apresentamos uma análise preliminary utilizando técnicas de análise de sentimentos realizada em um projeto de FOSS. Para isso, executamos a mineração da lista de endereços eletrônicos de um projeto e aplicamos as técnicas propostas aos participantes mais relevantes. Embora a aplicação seja limitada, no momento atual, experamos que essa experiência possa ser benéfica no future para determiner situações que possam afetar os desenvolvedores ou o projeto, tais como baixa produtividade, abandono do projeto ou bifurcação do projeto, entre outras.

Download Full-text

XML (almost) all the way

Proceedings of Balisage: The Markup Conference 2015 ◽

10.4242/balisagevol15.flynn01 ◽

2015 ◽

Author(s):

Peter Flynn

Keyword(s):

Human Factors ◽

Open Source ◽

Support Group ◽

Open Source Software ◽

Financial Resources ◽

Small Scale ◽

It Support ◽

Source Journal ◽

Almost All

In 2006 my university academic IT support group was approached by an academic colleague wanting to start a new journal, which would be available in electronic form only. There were restrictions imposed by the technical capabilities of the pool of authors, the requirements of the discipline, and — unsurprisingly — the lack of financial resources. The decision was made to implement a system using only open source software, and building largely from scratch, as the existing open source journal publishing systems at the time, although comprehensive and well-established, were seen as far too large and complex for the task. This paper is a case study describing the process and explaining the background to the decisions made. It attempts to draw some conclusions about the technical viability of creating a small-scale publishing system which attempted to retain XML throughout the workflow, and about the human factors which influenced the decisions.

Download Full-text

Boundary Critique and Stakeholder Collaboration in Open Source Software Migration

Knowledge and Technological Development Effects on Organizational and Social Structures ◽

10.4018/978-1-4666-2151-0.ch012 ◽

2012 ◽

pp. 194-208

Author(s):

Osden Jokonya ◽

Stan Hardman

Keyword(s):

Open Source ◽

South African ◽

Open Source Software ◽

South African Government ◽

Structured Interviews ◽

African Government ◽

Stakeholder Collaboration ◽

Boundary Critique ◽

Software Migration

This paper investigates the contribution of stakeholder collaboration during an open source software migration using a case study. The case study is based on the Presidential National Commission, a South African government department that migrated from proprietary software to open source software in 2007. The organization was one of the few that migrated to open source software as part of a South African government initiative. The case study consisted of semi-structured interviews with the participants involved in the migration. The interviews centered on the contribution of stakeholder collaboration during the software migration using a boundary critique. The results suggest that stakeholder collaboration can contribute to open source software migration. From a managerial perspective, business leaders must understand the value of stakeholder collaboration in open source software migration. Boundary critique can be an important tool for achieving broader collaboration of stakeholders.

Download Full-text

Assessing the Health of an Open Source Ecosystem

Emerging Free and Open Source Software Practices ◽

10.4018/978-1-59904-210-7.ch011 ◽

2007 ◽

pp. 238-258 ◽

Cited By ~ 5

Author(s):

Donald Wynn Jr.

Keyword(s):

Conceptual Framework ◽

Open Source ◽

Open Source Software ◽

Ecosystem Health ◽

Three Dimensions ◽

Software Projects

This study examines the concept of an ecosystem as originated in the field of ecology and applied to open source software projects. Additionally, a framework for assessing the three dimensions of ecosystem health is defined and explained using examples from a specific open source ecosystem. The conceptual framework is explained in the context of a case study for a sponsored open source ecosystem. The framework and case study highlight a number of characteristics and aspects of these ecosystems which can be evaluated by existing and potential members to gauge the health and sustainability of open source projects and the products and services they produce.

Download Full-text

Open Source Software Adoption

Software Applications ◽

10.4018/978-1-60566-060-8.ch099 ◽

2009 ◽

pp. 1675-1698 ◽

Cited By ~ 1

Author(s):

Brian Fitzgerald

Keyword(s):

Public Sector ◽

Open Source ◽

Open Source Software ◽

Longitudinal Case Study ◽

Software Adoption ◽

Public Sector Organization ◽

Desktop Application ◽

Depth Study ◽

Over Time

Current estimates suggest widespread adoption of open source software (OSS) in organizations worldwide. However, the problematic nature of OSS adoption is readily evidenced in the fairly frequent reports of problems, unforeseen hold-ups, and outright abandonment of OSS implementation over time. Hibernia Hospital, an Irish public sector organization, have embarked on the adoption of a range of OSS applications over several years, some of which have been successfully deployed and remain in live use within the organisation, whereas others, despite achieving high levels of assimilation over a number of years, have not been ultimately retained in live use in the organization. Using a longitudinal case study, we discuss in depth the deployment process for two OSS applications – the desktop application suite whose deployment was unsuccessful ultimately, and the email application which was successfully deployed. To our knowledge, this is the first such in-depth study into successful and unsuccessful OSS implementation.

Download Full-text