Posties: a WebDAV application for collaborative work
HYPERTEXT '00 Proceedings of the eleventh ACM on Hypertext and hypermedia
A framework analysis of the open source software development paradigm
ICIS '00 Proceedings of the twenty first international conference on Information systems
Renovating the collected algorithms from ACM
ACM Transactions on Mathematical Software (TOMS)
Specialised agent applications
Mutli-agents systems and applications
Proceedings of the 24th International Conference on Software Engineering
Software release management for component-based software
Software—Practice & Experience
Applications of information agent systems
Intelligent agents and their applications
Specialised Agent Applications
EASSS '01 Selected Tutorial Papers from the 9th ECCAI Advanced Course ACAI 2001 and Agent Link's 3rd European Agent Systems Summer School on Multi-Agent Systems and Applications
Simple maintenance of Beowulf clusters in an academic environment
Journal of Computing Sciences in Colleges
CVSSearch: Searching through Source Code using CVS Comments
ICSM '01 Proceedings of the IEEE International Conference on Software Maintenance (ICSM'01)
How to manage your software product life cycle with MAUI
Communications of the ACM - Homeland security
A Complete Textual Merging Algorithm for Software Configuration Management Systems
COMPSAC '04 Proceedings of the 28th Annual International Computer Software and Applications Conference - Volume 01
LISA '03 Proceedings of the 17th USENIX conference on System administration
The FreeBSD Project: A Replication Case Study of Open Source Development
IEEE Transactions on Software Engineering
Towards a taxonomy of software change: Research Articles
Journal of Software Maintenance and Evolution: Research and Practice - Unanticipated Software Evolution
Socialization in an Open Source Software Community: A Socio-Technical Analysis
Computer Supported Cooperative Work
Computer Supported Cooperative Work
Incremental Maintenance of Software Artifacts
IEEE Transactions on Software Engineering
Free/open source software development
Proceedings of the the 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
Free/open source software development: recent research results and emerging opportunities
The 6th Joint Meeting on European software engineering conference and the ACM SIGSOFT symposium on the foundations of software engineering: companion papers
Software evolution in open source projects—a large-scale investigation
Journal of Software Maintenance and Evolution: Research and Practice
Innovative concept of open source enterprise resource planning (ERP) system
CompSysTech '08 Proceedings of the 9th International Conference on Computer Systems and Technologies and Workshop for PhD Students in Computing
A Case Study in Grammar Engineering
Software Language Engineering
Toward a version control system for aspect oriented software
MEDI'11 Proceedings of the First international conference on Model and data engineering
Incremental workflow mining based on document versioning information
SPW'05 Proceedings of the 2005 international conference on Unifying the Software Process Spectrum
Hi-index | 0.00 |
From the Book:If you're like most programmers, you don't make your living from free software (though it would be nice if you could, wouldn't it?). But chances are you've at least used some free software, and perhaps contributed code or documentation to free projects. In that case, you'll have noticed a couple of things about the free software explosion of the last few years: A culture and a shared set of values are springing up. Among these: Software has maintainers but not "owners," the line between developers and users is deliberately left undrawn, bugs are publicized instead of denied, and information hoarding of any kind is frowned on. Many free projects, and especially those with large, distributed development teams, store their source code in a revision control system called CVS. The second phenomenon is closely related to the first. CVS is flourishing precisely because it supports, and even encourages, the open, evolutionary development methods favored by free software. It allows anyone on the Internet immediate access to the latest version of the source code, it facilitates the creation of the "patch files" so necessary for contributing bug fixes and new features to a project, and it allows active developers to hack away at the same code base without worrying about stepping on each others' toes. Truly, if CVS did not exist, we would have to invent it. This book has two goals, therefore--one social, the other technical. The social goal is to document this new culture and provide concrete advice for people managing or participating in Open Source projects. The technical goal is to tell you everything you need to know to use CVS,with an eye toward using it on Open Source projects. As to the first goal: The operative word here is "advice." It would be presumptuous of me to make authoritative pronouncements on a subject so young and unsettled. Remember all those Web page design books that came out when the World Wide Web was barely a year old? Hindsight now shows many of their suggestions to be questionable or just plain wrong. Anxious to avoid the same pitfall, I will try to stick to what I know from personal experience to be true about Open Source practices. When my personal opinions do break into view, as will happen frequently, please do not take them as proven fact. And as for CVS, note that although it will be taught in the context of Open Source projects, you will learn CVS well enough to use it anywhere. It's not just for managing program source code; people also use it to version-yes, that's a verb now-Web sites, text documents, configuration files, and so on. (You'll also learn how to judge, without resorting to time-consuming experiments, whether CVS is the right tool for a given situation.) Accordingly, the book is arranged loosely into alternating chapters, some about Open Source development, some about CVS. As it progresses, and you become increasingly familiar with both topics and the strong links between them, this division will become less and less strict. It is assumed that you know something about programming or working with online documents, but previous familiarity with CVS is not required. At least a passing familiarity with Unix will prove handy, because the CVS examples are given in a Unix environment. But if you're a quick study you can get by without previous Unix experience. A Word About Terminology Is it "Open Source" or "free software"? This is an old-by Internet standards anyway-and rancorous debate. It has the defining characteristic of a linguistic dispute, namely, that people spend a lot of time arguing about whether there's anything to argue about. In my mind, the two terms are essentially synonymous, and I will use them interchangeably in this book. See Richard Stallman's essay "Why 'Free Software' is better than 'Open Source'" at http://www.gnu.org/philosophy/open-source-or-free.html for a well-written presentation of the case that the terms are not interchangeable. The "free" in free software refers, of course, not to price but to liberty-the freedom to modify and redistribute the source code as one wishes. It is this freedom, not the software's low cost, that has been the key to free software's success. It is unfortunate, then, that English does not have separate words for these two largely separate concepts. I hope it is not reflective of our values that our language associates low prices with liberty.