To install click the Add extension button. That's it.

The source code for the WIKI 2 extension is being checked by specialists of the Mozilla Foundation, Google, and Apple. You could also do it yourself at any point in time.

4,5
Kelly Slayton
Congratulations on this excellent venture… what a great idea!
Alexander Grigorievskiy
I use WIKI 2 every day and almost forgot how the original Wikipedia looks like.
Live Statistics
English Articles
Improved in 24 Hours
Added in 24 Hours
What we do. Every page goes through several hundred of perfecting techniques; in live mode. Quite the same Wikipedia. Just better.
.
Leo
Newton
Brights
Milds

From Wikipedia, the free encyclopedia

Code Co-op
Developer(s)Reliable Software
Initial release1996; 28 years ago (1996)
Final release
5.2a / June 4, 2011; 12 years ago (2011-06-04)
Repository
Operating systemWindows
Available inEnglish
TypeRevision control
LicenseMIT
Websiteweb.archive.org/web/20180211130625/http://www.relisoft.com/co_op/index.htm Edit this on Wikidata

Code Co-op is the peer-to-peer revision control system made by Reliable Software.

YouTube Encyclopedic

  • 1/3
    Views:
    2 351 101
    286 582
    589
  • Coding Interview | Software Engineer @ Bloomberg (Part 1)
  • How to ACTUALLY Get an Entry Level Programming Job
  • How To Automate Getting A Software Co-op/Internship (A Unique Method)

Transcription

Distinguishing features

Code Co-op is a distributed revision control system of the replicated type.

It uses peer-to-peer architecture to share projects among developers and to control changes to files. Instead of using a centralized database (the repository), it replicates its own database on each computer involved in the project.

The replicas are synchronized by the exchange of (differential) scripts. The exchange of scripts may proceed using different transports, including e-mail (support for SMTP and POP3, integration with MAPI clients, Gmail) and LAN.

Code Co-op has a built-in peer-to-peer wiki system, which can be used to integrate documentation with a software project. It is also possible to create text-based Wiki databases, which can be queried using simplified SQL directly from wiki pages.

Standard features

  1. Distributed development support through E-mail, LAN, or VPN
  2. Change-based model—modifications to multiple files are checked in as one transaction
  3. File additions, deletions, renames, and moves are treated on the same level as edits—they can be added in any combination to a check-in changeset
  4. File changes can be reviewed before a check-in using a built-in or user-defined differ
  5. Synchronization changes can be reviewed in the same manner by the recipients
  6. Three-way visual merge
  7. Project history is replicated on each machine. Historical version can be reviewed, compared, or restored
  8. Integration with Microsoft SCC clients, including Visual Studio

History

Code Co-op was one of the first distributed version control systems. It debuted at the 7th Workshop on System Configuration Management in May 1997.[1]

The development of Code Co-op started in 1996, when Reliable Software, the distributed software company that makes it, was established. Reliable Software needed a collaboration tool that would work between the United States and Poland. The only dependable and affordable means of communication between the two countries was e-mail, hence the idea of using e-mail for the exchange of diffs. Of course, with such slow transport, using a centralized repository was infeasible. Each user of Code Co-op had to have a full replica of the repository, including the history of changes.

The problem was reduced to that of designing a distributed database that uses slow and unreliable transport for synchronization (later, faster LAN transport was also added). It also followed that the synchronization between multiple sites must use some kind of peer-to-peer protocol.

In 2018, the C++ source code for Code Co-op was released under the MIT License.

Theoretical foundations

Code Co-op is an example of a distributed database. Local repositories are considered the replicas of this virtual database. Each check-in corresponds to a distributed commit—a non-blocking version of a two-phase commit.

References

  1. ^ Milewski, B. (1997). Distributed source control system. ICSE'97 SCM-7 Workshop. Software Configuration Management. LNCS. Vol. 1235. pp. 98–10. doi:10.1007/3-540-63014-7_8. ISBN 978-3-540-63014-2. ISSN 0302-9743.

External links


This page was last edited on 26 February 2024, at 09:43
Basis of this page is in Wikipedia. Text is available under the CC BY-SA 3.0 Unported License. Non-text media are available under their specified licenses. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc. WIKI 2 is an independent company and has no affiliation with Wikimedia Foundation.