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 47.
4. lappuse
... lines Activity on development version in October 2002 118 persons committed 2,063 changes 40,000 files, 6 million lines 107 persons committed 2,856 changes 50% of these commits made by 12 developers 7 developers Project management 9 ...
... lines Activity on development version in October 2002 118 persons committed 2,063 changes 40,000 files, 6 million lines 107 persons committed 2,856 changes 50% of these commits made by 12 developers 7 developers Project management 9 ...
5. lappuse
... line of descendants from the legendary Berkeley Software Distribution from 1977. FreeBSD runs on a number of different hardware platforms, most importantly Intel x86 processors, but also Alpha, PowerPC, Sparc64, NEC PC-98, and IA-64 ...
... line of descendants from the legendary Berkeley Software Distribution from 1977. FreeBSD runs on a number of different hardware platforms, most importantly Intel x86 processors, but also Alpha, PowerPC, Sparc64, NEC PC-98, and IA-64 ...
6. lappuse
... lines were changed, and what comments the committer supplied. • Conflicting changes to a file (as when two developers want to change the same lines) are handled gracefully; the last committer will have to explicitly accept or reject the ...
... lines were changed, and what comments the committer supplied. • Conflicting changes to a file (as when two developers want to change the same lines) are handled gracefully; the last committer will have to explicitly accept or reject the ...
7. lappuse
... line with what Raymond (2000) has entitled Linus'Law, “Given enough eyeballs, all bugs are shallow,” in both projects everyone can report bugs, and everyone is actively encouraged to do this. A “bug” doesn't have to be an error; rather ...
... line with what Raymond (2000) has entitled Linus'Law, “Given enough eyeballs, all bugs are shallow,” in both projects everyone can report bugs, and everyone is actively encouraged to do this. A “bug” doesn't have to be an error; rather ...
27. 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