- Paperback: 350 pages
- Publisher: Paraglyph Press; Third Edition edition (July 1 2003)
- Language: English
- ISBN-10: 1932111816
- ISBN-13: 978-1932111811
- Product Dimensions: 22.6 x 18 x 1.8 cm
- Shipping Weight: 522 g
- Average Customer Review: 4.3 out of 5 stars See all reviews (26 customer reviews)
- Amazon Bestsellers Rank: #1,623,482 in Books (See Top 100 in Books)
|
||||||||||||||||||
|
||||||||||||||||||
|
||||||||||||||||||
| ||||||||||||
Product Details |
Product Description
From Amazon
The need for a modern source-code management strategy in the distributed open-source community is paramount. The benevolent dictatorship model of open-source maintainers is only quasi-stable, but it is far better than the other extreme: the chaos of democratic code development.
The best available compromise is the concurrent versioning system (CVS), which introduces proctored code merging into source code management. CVS is ideally suited for worldwide open-source development, and the world is ready for monographs that address the management issues that Per Cederqvist explicitly avoided in his fine 164-page postscript manual distributed with the CVS tar-ball. What is the role of a maintainer/manager in establishing test protocols for code merges? What minimal functional level of developer communications is necessary for merges to remain stable? Is a maintainer-less release possible?
These questions go largely unanswered in Karl Fogel's new Open Source Development with CVS. Fogel's 300-page book consists of chapters alternating between CVS basics and common code maintenance issues. He includes a few anecdotes from open-source lore and lots of nonspecific commonsense guidelines on team software development.
Fogel is at his best when he is engaging us in thinking about what should and should not be under CVS control. He points out that complex relationships exist between developing code and its dependencies on intimately related applications, such as build tools themselves (gcc, autoconf) or partner applications (e.g., the server's client or the client's server). His brief discussion of strategies is too short to be satisfying.
Frustratingly, this book is chock-full of postmodern self-indulgences, such as his boasting reverence for technological ignorance. The discipline needed by good maintainers is missing here; Fogel's informal prose is often grating, and his copious parenthetical remarks are distracting or bullying (they sure are); one wonders where his editor was. Ultimately, his management arguments boil down to an endorsement for the benevolent dictatorship model--a safe conclusion, but one that seems not to use CVS's merging capability for all it's worth. To the question of how to run a project, he responds, "Well, we're all still trying to figure that out, actually." True, and he isn't there yet, but at least he has the questions right. --Peter Leopold --This text refers to an out of print or unavailable edition of this title.
Book Description
Open Source Development with CVS, Third Edition, is an updated edition of the best-selling guide to the most widely used version control software for open source developers. This new edition has been enhanced with more value-added material covering third-party tools, remote operation, scalability, client access limits, BitKeeper, and overall server administration for CVS.
Inside This Book
(Learn More)
First Sentence
"Traditional capitalism is based on the idea of limited supply; however, information has become a commodity in itself and is never in short supply." Read the first page
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
"Traditional capitalism is based on the idea of limited supply; however, information has become a commodity in itself and is never in short supply." Read the first page
Explore More
Concordance
Browse Sample PagesConcordance
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organize and find favorite items. |
Customer Reviews
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most helpful customer reviews
3.0 out of 5 stars
I couldn't get past the setup part,
By
This review is from: Open Source Development with CVS (Paperback)
The book looks to be well written with lots of details, but I feel the first few introductory pages are insufficiently detailed which prevented me from setting things up. Specifically:* The examples don't say whether your supposed to be in or above the working directory for various cvs commands. The reader is supposed to assume that current directory for this example is the same place as the current directory at the end of the previous example, but nothing says that. (it's obvious once you know). * The overview chapter only talks about importing a whole directory tree. It's not clear how to add a directory or a file to an already imported directory tree. Actually, it's explained 20 pages later, but I didn't find that for a while. * I made a mistake and imported a working dir subdirectory as a top level directory in the central cvs repository. There's no quick overview commands for removing setup mistakes. (Actually, that's shown about 30 pages after the overview). The book doesn't say that importing a subdirectory if you're in the subdirectory, makes it a top level directory in the CVS repository. I'm sure once I understand what's going on, it'll be obvious. But to do my basic directory setup, and cleanup from a mistake, I had to wade through all sorts of "once it's working" text to find what I wanted. Also, in the Removing Directories section, he keeps referring to directories without saying whether he's referring to directories in the user tree or under the CVS repository tree.
5.0 out of 5 stars
very useful examples concerning tagging and branching,
By
This review is from: Open Source Development with CVS (Paperback)
I've used cvs for a couple of years, but have never really needed tagging or branching until I became a developer on the www.mycibavision.com project. Then, we needed it. Tagging and branching were difficult to grasp for me. This book was critical in helping me to understand what tagging and branching were and how to do use those features.Aside from that, the main reason I like this book so much is that _everything_ has example code to go with it. Even better is that the output from every command is displayed as well. I found myself executing the commands and then comparing the output. I would highly recommend this book.
4.0 out of 5 stars
Good Book.. Great Examples,
By
This review is from: Open Source Development with CVS (Paperback)
I was looking a good guide and reference for CVS, so I decided to pick up this book. Overall, I think this book does a good job of going through most of CVS's features, however I think there could of been a little more detail in the administration section and dealing with permissions. I was pleasantly surprised that besides covering CVS, this book gives some great background in to the OSS movement and the advantages of OSS in general. I would also like to thank the authors and the publisher for deciding to put most of the meatier chapters on-line, its nice to see people practicing what they preach.
Share your thoughts with other customers: Create your own review
Want to see more reviews on this item?
|
Most recent customer reviews |
Listmania!
Look for similar items by category
Look for similar items by subject
Feedback
Would you like to update product info or give feedback on images?
|
