The Co-Evolution of Systems and Communities in Free and Open Source Software Development

2008 ◽  
pp. 3765-3776
Author(s):  
Yunwen Ye ◽  
Kumiyo Nakakoji ◽  
Yasuhiro Yamamoto ◽  
Kouichi Kishida

Because a Free and Open Source Software (F/OSS) project is unlikely to sustain a long-term success unless there is an associated community that provides the platform for developers, users, and user-turned-developers to collaborate with each other, understanding the well-observed phenomenon that F/OSS systems experience “natural product evolution” cannot be complete without understanding the structure and evolution of their associated communities. This chapter examines the structure of F/OSS communities and the co-evolution of F/OSS systems and communities based on a case study. Although F/OSS systems and communities generally co-evolve, they co-evolve differently depending on the goal of the system and the structure of the community. A systematic analysis of the differences leads us to propose a classification of F/OSS projects into three types: Exploration-Oriented, Utility-Oriented, and Services-Oriented. Practical implications of realizing the co-evolution and recognizing the different types of F/OSS projects are discussed to provide guidance for F/OSS practitioners.

Author(s):  
Yunwen Ye ◽  
Kumiyo Nakakoji ◽  
Yasuhiro Yamamoto ◽  
Kouichi Kishida

Because a Free and Open Source Software (F/OSS) project is unlikely to sustain a long-term success unless there is an associated community that provides the platform for developers, users, and user-turned-developers to collaborate with each other, understanding the well-observed phenomenon that F/OSS systems experience “natural product evolution” cannot be complete without understanding the structure and evolution of their associated communities. This chapter examines the structure of F/OSS communities and the co-evolution of F/OSS systems and communities based on a case study. Although F/OSS systems and communities generally co-evolve, they co-evolve differently depending on the goal of the system and the structure of the community. A systematic analysis of the differences leads us to propose a classification of F/OSS projects into three types: Exploration-Oriented, Utility-Oriented, and Services-Oriented. Practical implications of realizing the co-evolution and recognizing the different types of F/OSS projects are discussed to provide guidance for F/OSS practitioners.


2009 ◽  
pp. 361-370
Author(s):  
Javier Soriano ◽  
Rafael Fernández ◽  
Miguel Jiménez

Traditionally, collaboration has been a means for organizations to do their work. However, the context in which they do this work is changing, especially in regards to where the work is done, how the work is organized, who does the work, and with this the characteristics of collaboration. Software development is no exception; it is itself a collaborative effort that is likewise affected by these changes. In the context of both open source software development projects and communities and organizations that develop corporate products, more and more developers need to communicate and liaise with colleagues in geographically distant places about the software product they are conceiving, designing, building, testing, debugging, deploying and maintaining. Thus, work teams face sizeable collaborative challenges, for which they have need of tools that they can use to communicate and coordinate their work efficiently.


Author(s):  
A. Mascitelli ◽  
M. Ravanelli ◽  
S. Mattoccia ◽  
C. Berardocco ◽  
A. Mazzoni

Abstract. Indoor mapping is an essential process in several applications such as the visualization of space and its utilization, security and resource planning, emergency planning and location-based alerts and, last but not least, indoor navigation. In this work, a completely free and open-source (FOS) approach to map indoor environments, and to navigate through them, is presented. Our tests were carried out within Sapienza University of Rome public buildings; in detail, Letters and Philosophy faculty and Engineering faculty indoor environments were mapped. To reach this goal, only open source software such as Quantum GIS (QGIS) and open-source platforms like Open Street Map (OSM) and its indoor viewer, Open Level Up (OLU) were adopted. A database of indoor environments of the two faculties, completely compatible with OLU, was created through QGIS. In this way, a public territorial information system of classrooms, offices and laboratories is accessible to everyone who can, hence, add or modify the information, following the principle of crowdsourcing and of Volunteered Geographic Information (VGI). The developed procedure is now standard and its outputs accepted by the OSM community. Hence, the long-term developments of this project are the proposal for the volunteered and cooperative indoor mapping and design of strategic buildings and infrastructures (hospitals, schools, public offices, shopping centers, stations, airports etc.), starting from the available information (indoor layouts) and knowledge acquired through experience of people who normally work inside them and/or visit them frequently. In this context it is possible to state that the development of VGI for internal maps for strategic buildings, infrastructures and denied GNSS environments, not only supports and improves internal and external navigation without interruption, but can also have a significant positive impact on security and emergency management.


Author(s):  
Javier Soriano ◽  
Rafael Fernández ◽  
Miguel Jiménez

Traditionally, collaboration has been a means for organizations to do their work. However, the context in which they do this work is changing, especially in regards to where the work is done, how the work is organized, who does the work, and with this the characteristics of collaboration. Software development is no exception; it is itself a collaborative effort that is likewise affected by these changes. In the context of both open source software development projects and communities and organizations that develop corporate products, more and more developers need to communicate and liaise with colleagues in geographically distant places about the software product they are conceiving, designing, building, testing, debugging, deploying and maintaining. Thus, work teams face sizeable collaborative challenges, for which they have need of tools that they can use to communicate and coordinate their work efficiently.


Sign in / Sign up

Export Citation Format

Share Document