Differences

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

--- tools:vcs:index [2019/01/29 22:23] – [Version control] till
+++ tools:vcs:index [2020/09/29 16:30] (current) – till
@@ Line 1: / Line 1: @@
+~~NOTOC~~
 {{fa>code-fork?48&align=right}}
  ====== Version control ======
@@ Line 7: / Line 9: @@
 <WRAP column 32px>{{fa>key?32}}</WRAP>
 <WRAP column 85%>
-  * Version control liberates software development.
+  * Version control has a liberating effect on software development.
-  * Version control is an essential prerequisite to unequivocally identify the version of a routine employed.
+  * Version control is an essential prerequisite\\ to unequivocally identify the version of a routine employed.
-  * Distributed version control systems facilitate using them and reduce external dependencies.
+  * Distributed version control systems facilitate their use\\ and reduce external dependencies.
-  * For a larger project, a clear work flow should be decided on and followed consequently.
+  * For a larger project, a clear work flow should be established\\ and followed consequently.
-  * Version control has the largest impact on how we program -- besides automatic tests.
+  * Version control has the largest impact on how we program --\\ besides automatic tests.
 </WRAP>
 </WRAP>
-  * Why versioning?
+===== Why versioning? =====
-    * Software is //always// subject to change -- that's why it is called "soft".
-    * Routines for data processing and analysis develop, often together with the understanding of the task.
+  * Software is //always// subject to change -- that's why it is called "soft".
-    * Reverting to the last version that "just worked" is an (easy) task.
+  * Routines for data processing and analysis develop, often together with the understanding of the task.
-  * What should be versioned?
+  * Reverting to the last version that "just worked" is an (easy) task.
-    * Basically everthing, from a script for data processing to the final manuscript/thesis/project report
-  * What are prerequisites for ubiquitious versioning?
-    * Open file formats allowing for easy versioning (ideally text formats)
+===== What should be versioned? =====
-    * Minimal infrastructure requirements, as met by a distributed version control system
-    * Possibility to share versioned data with others (via simple-to-use web interfaces)
+  * Basically everthing, from a script for data processing to the final manuscript/thesis/project report
+===== What are prerequisites for ubiquitious versioning? =====
+  * Open file formats allowing for easy versioning (ideally text formats)
+  * Minimal infrastructure requirements, as met by a distributed version control system
+  * Possibility to share versioned data with others (via simple-to-use web interfaces)
 Beware: Versioning without [[..:versionnumbers:|version numbers]] is only half the battle.
@@ Line 50: / Line 59: @@
 For local applications and given a minimum of infrastructure, [[https://gitea.io/|Gitea - Git with a cup of tea]] is highly recommended as a fast and light-weight alternative to services such as [[https://about.gitlab.com/|GitLab]]. Gitea describes itself as a "painless self-hosted Git service" -- and this really //is// true.
+\\
+<WRAP half column leftalign><WRAP button>[[..:|← Tools]]</WRAP></WRAP>
+<WRAP half column rightalign><WRAP button>[[..:versionnumbers:|Version numbers →]]</WRAP></WRAP>