Free/open Source Software DevelopmentStefan Koch Idea Group Inc (IGI), 2005. gada 1. janv. - 309 lappuses Free/Open Source Software Development gives an overview of the current research streams in the field of free and open source software development. A multitude of research approaches are used to explore free and open source software development processes, attributes of their products and the workings within the development communities. This book offers a glimpse beyond 'classical' free and open source software development, and analyzes chances and risks for cooperations with traditional organizations and the implications of this new model for areas other than software development. |
No grāmatas satura
6.–10. rezultāts no 71.
14. lappuse
... contributor and perform the actual changes to the repository. Historically, more than 1,700 persons have contributed to FreeBSD (Contributors to FreeBSD, 2003), and approximately 850 persons to Mozilla (Our Contributors, 2003). A ...
... contributor and perform the actual changes to the repository. Historically, more than 1,700 persons have contributed to FreeBSD (Contributors to FreeBSD, 2003), and approximately 850 persons to Mozilla (Our Contributors, 2003). A ...
18. lappuse
... contributors is to quickly see the results of their work; a frozen tree will inhibit this. • When the trunk is ... contributions that eventually will lead to the next release. Copyright © 2005, Idea Group Inc. Copying or distributing in ...
... contributors is to quickly see the results of their work; a frozen tree will inhibit this. • When the trunk is ... contributions that eventually will lead to the next release. Copyright © 2005, Idea Group Inc. Copying or distributing in ...
19. lappuse
... contributor and to keep other team members productive on the project.” 1. 2. 3. Assignment – choosing the task to work on. There is a general recommendation to “stay focused on the most important problems,” but no explicit, given task ...
... contributor and to keep other team members productive on the project.” 1. 2. 3. Assignment – choosing the task to work on. There is a general recommendation to “stay focused on the most important problems,” but no explicit, given task ...
21. lappuse
... contributions become too complicated and time-consuming, there will be a significant risk of losing developers, especially if they, as Raymond (2000) puts it, are “self-directed egoists.” Reducing the potential problem of lacking or ...
... contributions become too complicated and time-consuming, there will be a significant risk of losing developers, especially if they, as Raymond (2000) puts it, are “self-directed egoists.” Reducing the potential problem of lacking or ...
22. lappuse
Esat sasniedzis šīs grāmatas aplūkošanas reižu limitu.
Esat sasniedzis šīs grāmatas aplūkošanas reižu limitu.
Saturs
FOSS Development and Software Engineering Practices Extensive Analysis | 83 |
FOSS Projects as Social Constructs | 124 |
Simulating FOSS Development Dynamic Swarms | 173 |
FOSS Development Interacting with Commercial and Public Organizations | 221 |
Implications of the FOSS Development Model The Broad Picture | 258 |
About the Editor | 296 |
About the Authors | 297 |
Index | 306 |
Citi izdevumi - Skatīt visu
Bieži izmantoti vārdi un frāzes
active analysis Apache application approach authors changes chapter commits companies complex Computer considered contributions contributors Copying or distributing Copyright core create culture Debian design patterns discussion distributing in print documentation effort electronic forms ethical evolution example existing F/OSS development F/OSS projects fact Figure forms without written free software FreeBSD GNUe Idea Group Inc important individual intellectual property interest languages lines Linux means modularity module Mozilla open source software organization packages participation permis person possible practices present print or electronic problems programming release reported requirements Retrieved role Science shows simulation SLOC social software development software engineering source code structure task technical testing tion University users values written permission