Differences

This shows you the differences between two versions of the page.

--- opu:repository [2017/11/26 03:14] – vagabond
+++ opu:repositories:repositories [2021/03/29 23:12] (current) – [Version Control Rules of thumb] leeor_net
@@ Line 5: / Line 5: @@
 **Index**
-  * [[opu:repositories:subversion|Subversion Repository Specifics]]
   * [[opu:repositories:Git|Git Repository Specifics]]
   * [[opu:repositories:SVNToGit|Transferring SVN to Git Repositories]]
 ===== The Outpost Universe on GitHub =====
+{{ opu:repositories:octocat_smaller.png?130}}
 Outpost Universe on GitHub is the newer repository and is becomming the primary repository for projects that do not directly contain the game download. Ongoing work is occurring to migrate appropriate projects from the SVN repository to the GitHub repository. You can find the GitHub site at https://github.com/OutpostUniverse.
@@ Line 17: / Line 18: @@
 ===== Outpost 2 SVN Repository =====
-{{ opu:repositories:subversionlogo.png}}
+{{ opu:repositories:subversionlogo.png?130}}
-Outpost 2's SVN repository is hosted online through VisualSVN Server. Version controlled documents may be browsed using any web browser. There are no restrictions on who can pull a copy of the repository. To write files into the repository, contact an Outpost Universe Admin about gaining write access.
-To access and manipulate the SVN repository, a lot of community members use TortoiseSVN, however SVN works great on the command line as well.
-Before posting content to the repository, read through the guidelines below. Remember all data in the Outpost Universe repository is meant for public access.
-Outpost Universe SVN Repository: [[https://svn.outpostuniverse.org:8443/!/#]].
+Outpost 2's SVN repository was hosted online through VisualSVN Server. The repository is no longer maintained and users are encouraged to use GitHub for source code control instead. See above for Outpost Universe's official GitHub site.
 ===== Version Control Rules of thumb =====
@@ Line 41: / Line 36: @@
   * When committing code, attempt to separate each new feature into a separate commit.
-  * Spend time writing quality commit messages that discuss why the changes were made. (https://chris.beams.io/posts/git-commit/)
+  * Spend time writing quality commit messages that discuss why the changes were made. (https://web.archive.org/web/20210326041439/https://chris.beams.io/posts/git-commit/)
     * Include a subject line in the commit
     * Capitalize the subject line