|
Size: 3698
Comment:
|
Size: 4771
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| Version Control Systems (also called Source Control Management (SCM) or Revision Control Systems (RCS)) are a type of software for keeping track of changes to files and merging changes from multiple users (usually developers) into a common tree. There are a number of different VCSs out there. Here we will focus on commonly used open source ones. == Historically relevant == |
|
| Line 10: | Line 11: |
| * Subversion - designed to replace CVS and correct some of its flaws. Similar syntax to CVS. Too much like CVS for many people's taste. | * Subversion - designed to replace CVS and correct some of its flaws. Similar syntax to CVS. Too much like CVS for many people's taste, but probably the most commonly used VCS still. [http://code.google.com Google Code] and [http://sf.net SourceForge] use it for projects they host. |
| Line 13: | Line 14: |
| == Recommended (and installed) == All of these are distributed VCSs, which means that each user has a full tree including revision history; there is no privileged central tree (unless you want there to be). |
|
| Line 17: | Line 20: |
| * Bazaar - a VCS written in Python by Canonical software (makers of Ubuntu Linux) for their needs. It's about as powerful as Git, but with much less jargon and with simpler command syntax. | * Bazaar - a VCS written in [http://www.python.org/ Python] by [http://www.canonical.com/ Canonical] software (makers of [http://www.ubuntu.com/ Ubuntu] Linux) for their needs. It's about as powerful as Git, but with much less jargon and with simpler command syntax. Bazaar is designed in part to integrate well with Canonical's [https://launchpad.net/ LaunchPad] project hosting. |
| Line 20: | Line 23: |
| * Mercurial - VCS written in Python and C. Created when the makers of Bitkeeper (the VCS formerly used by the Linux kernel team) pulled free licenses for open source projects. The kernel team went on to create Git instead, but other projects (e.g. Mozilla) use Mercurial. | * Mercurial - VCS written in Python and C. Created when the makers of Bitkeeper (the VCS formerly used by the Linux kernel team) pulled free licenses for open source projects. The kernel team went on to create Git instead, but other projects (most notably Mozilla) use Mercurial. |
| Line 22: | Line 25: |
| * [http://developer.mozilla.org/en/docs/Mercurial Mozilla Mercurial documentation] (very much a work in progress) | |
| Line 23: | Line 27: |
| == Worth noting == |
Version Control
Version Control Systems (also called Source Control Management (SCM) or Revision Control Systems (RCS)) are a type of software for keeping track of changes to files and merging changes from multiple users (usually developers) into a common tree. There are a number of different VCSs out there. Here we will focus on commonly used open source ones.
Historically relevant
- CVS - essentially the Ur version control system. Very common still, but not recommended for new projects
[http://www.nongnu.org/cvs/ CVS official site]
[http://en.wikipedia.org/wiki/Concurrent_Versions_System CVS wikipedia entry]
Subversion - designed to replace CVS and correct some of its flaws. Similar syntax to CVS. Too much like CVS for many people's taste, but probably the most commonly used VCS still. [http://code.google.com Google Code] and [http://sf.net SourceForge] use it for projects they host.
[http://subversion.tigris.org/ Subversion official site]
[http://en.wikipedia.org/wiki/Subversion_(software) Subversion wikipedia entry]
Recommended (and installed)
All of these are distributed VCSs, which means that each user has a full tree including revision history; there is no privileged central tree (unless you want there to be).
- Git - A VCS designed by Linus Torvalds to meet the needs of the Linux kernel developers. Powerful but complicated.
[wiki:HlpLab/Git Git local page]
[http://git.or.cz/ Git official site]
[http://en.wikipedia.org/wiki/Git_(software) Git wikipedia entry]
Bazaar - a VCS written in [http://www.python.org/ Python] by [http://www.canonical.com/ Canonical] software (makers of [http://www.ubuntu.com/ Ubuntu] Linux) for their needs. It's about as powerful as Git, but with much less jargon and with simpler command syntax. Bazaar is designed in part to integrate well with Canonical's [https://launchpad.net/ LaunchPad] project hosting.
[http://bazaar-vcs.org/ Bazaar official site]
[http://en.wikipedia.org/wiki/Bazaar_software Bazaar wikipedia entry]
- Mercurial - VCS written in Python and C. Created when the makers of Bitkeeper (the VCS formerly used by the Linux kernel team) pulled free licenses for open source projects. The kernel team went on to create Git instead, but other projects (most notably Mozilla) use Mercurial.
[http://www.selenic.com/mercurial/wiki/ Mercurial official site]
[http://developer.mozilla.org/en/docs/Mercurial Mozilla Mercurial documentation] (very much a work in progress)
[http://en.wikipedia.org/wiki/Mercurial_(software) Mercurial wikipedia entry]
Worth noting
- Darcs - designed to replace CVS and SVN. Written in Haskell and "based on a unique algebra of patches".
[http://darcs.net/ Darcs official site]
[http://en.wikipedia.org/wiki/Darcs Darcs wikipedia entry]
- Monotone - another VCS designed to replace CVS and SVN. But like Git, Arch, Bazaar, and Mercurial, it's designed to be decentralized. Not amazingly popular though.
[http://monotone.ca/ Monotone official site]
[http://en.wikipedia.org/wiki/Monotone_(software) Monotone wikipedia entry]
- Arch - a distributed VCS. Mostly superseded by Bazaar, and not under active development, but you might run across projects using it.
[http://www.gnu.org/software/gnu-arch/ Arch official site]
[http://en.wikipedia.org/wiki/GNU_arch Arch wikipedia entry]
Writing Tools
- LaTeX
[http://www.uoregon.edu/~koch/texshop/ TeXShop]
[wiki:HlpLab/AUCTeX AUCTeX]
Reference Management
[http://mekentosj.com/papers/ Papers]
BibTeX / [http://bibdesk.sourceforge.net/ BibDesk]
[http://www.endnote.com/ EndNote] (UR has a [http://www.rochester.edu/it/sitelicenses/endnote.html site-license] for personal and work use.)
[http://www.zotero.org/ Zotero]
Presentation Tools
PowerPoint
[http://www.apple.com/iwork/keynote/ Keynote]
[http://latex-beamer.sourceforge.net/ LaTeX Beamer]
- Templates?
Graphing Tools
R Graphics Packages
[wiki:HlpLab/R/GGPlot2Package GGPlot2Package]
Graphing tasks
[wiki:HlpLab/R/ErrorBars ErrorBars]
[wiki:HlpLab/R/AddingLines AddingLines]
I've made a lot of these things links to their official website. It'd be nice to get pages created explaining the pros and cons for all of them. -- AndrewWatts DateTime(2008-06-09T14:23:20Z)