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 87.
11. lappuse
... not always of a sufficient quality: bug reports may be erroneous, newsgroup postings may be misleading or irrelevant ... forms without written permission Top-Level Management Both Mozilla and FreeBSD are headed by groups of Idea Group ...
... not always of a sufficient quality: bug reports may be erroneous, newsgroup postings may be misleading or irrelevant ... forms without written permission Top-Level Management Both Mozilla and FreeBSD are headed by groups of Idea Group ...
13. lappuse
... without review by the maintainer.” And it seems to be more like a duty and less like a privilege, compared to ... written acceptance from three super reviewers (Getting CVS Write Access to Mozilla, 2003). Copyright © 2005, Idea Group Inc.
... without review by the maintainer.” And it seems to be more like a duty and less like a privilege, compared to ... written acceptance from three super reviewers (Getting CVS Write Access to Mozilla, 2003). Copyright © 2005, Idea Group Inc.
14. lappuse
... no formal procedures involved in becoming a contributor. A contributor is simply someone who in some way has contributed ... forms without written permisFreeBSD Core Team is democratically elected by and from the committers. sion of Idea ...
... no formal procedures involved in becoming a contributor. A contributor is simply someone who in some way has contributed ... forms without written permisFreeBSD Core Team is democratically elected by and from the committers. sion of Idea ...
20. lappuse
... no super-reviewers in FreeBSD, only requirements to “discuss any significant change before committing [author's emphasis] ... forms without written permisBalancing Anarchy with Control In traditional software engineering, the quality ...
... no super-reviewers in FreeBSD, only requirements to “discuss any significant change before committing [author's emphasis] ... forms without written permisBalancing Anarchy with Control In traditional software engineering, the quality ...
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