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
1.–5. rezultāts no 20.
8. lappuse
... requirement specifications, each bug identifying a requirement to a new version of the software. Further, the hierarchical organization of bugs and the option of assigning bugs to releases make Mozilla's Bugzilla system also function as ...
... requirement specifications, each bug identifying a requirement to a new version of the software. Further, the hierarchical organization of bugs and the option of assigning bugs to releases make Mozilla's Bugzilla system also function as ...
19. lappuse
... requirements for this project will often come from the bug-tracking system, but developers can also specify their own requirements—“scratching their personal itch” (Raymond, 2000). Most developers seem to work more or less alone ...
... requirements for this project will often come from the bug-tracking system, but developers can also specify their own requirements—“scratching their personal itch” (Raymond, 2000). Most developers seem to work more or less alone ...
20. lappuse
... requirements to “discuss any significant change before committing [author's emphasis]”, “when in doubt, ask for review,” and “respect existing maintainers” (The FreeBSD Committers' Big List of Rules, n.d.). • There is no daily closing ...
... requirements to “discuss any significant change before committing [author's emphasis]”, “when in doubt, ask for review,” and “respect existing maintainers” (The FreeBSD Committers' Big List of Rules, n.d.). • There is no daily closing ...
21. lappuse
... requirement for separate design documentation; • No requirement to follow a specific model or method; • Developers can choose their own task; and • Only very basic tests are required before committing. On the other hand, the projects ...
... requirement for separate design documentation; • No requirement to follow a specific model or method; • Developers can choose their own task; and • Only very basic tests are required before committing. On the other hand, the projects ...
23. 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