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.
3. lappuse
... source code, so we will not go into details regarding how the projects handle tasks like infrastructure maintenance, public relations, and user documentation. Several previous studies have looked into how F/OSS is developed, often ...
... source code, so we will not go into details regarding how the projects handle tasks like infrastructure maintenance, public relations, and user documentation. Several previous studies have looked into how F/OSS is developed, often ...
5. lappuse
... source code repositories under CVS control (Fogel & Bar, 2001) and reachable via the Internet. Developers contribute to the projects by continually and in parallel updating (changing, adding, and deleting) repository files. The CVS ...
... source code repositories under CVS control (Fogel & Bar, 2001) and reachable via the Internet. Developers contribute to the projects by continually and in parallel updating (changing, adding, and deleting) repository files. The CVS ...
9. lappuse
... source code in the trunk is tested on a daily basis. The tests follow this scheme, according to Yeh (1999) and our own observations: • At 8 AM (PST) each working day, the tree closes, which means that further updates to the source code ...
... source code in the trunk is tested on a daily basis. The tests follow this scheme, according to Yeh (1999) and our own observations: • At 8 AM (PST) each working day, the tree closes, which means that further updates to the source code ...
11. lappuse
... source code in the repositories. In effect, anyone can contribute to the projects with bug reports or suggestions for changes; they can do this just once or on a regular basis, and thus it is not obvious whether these contributors ...
... source code in the repositories. In effect, anyone can contribute to the projects with bug reports or suggestions for changes; they can do this just once or on a regular basis, and thus it is not obvious whether these contributors ...
13. lappuse
... code ...Changes to directories which have a maintainer defined shall be sent to the maintainer for review before being committed.” FreeBSD seems, however, to have a more relaxed attitude to module ownership. There is an accepted risk ...
... code ...Changes to directories which have a maintainer defined shall be sent to the maintainer for review before being committed.” FreeBSD seems, however, to have a more relaxed attitude to module ownership. There is an accepted risk ...
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