Blob


1 <!doctype html>
2 <html lang=en>
3 <head>
4 <meta charset=utf-8>
6 <title>Game of Trees (Got): Frequently Asked Questions</title>
7 <meta name="description" content="Game of Trees (Got) Frequently Asked Questions">
8 <meta name="viewport" content="width=device-width, initial-scale=1">
9 <link rel="stylesheet" type="text/css" href="openbsd.css">
10 <link rel="canonical" href="https://gameoftrees.org/faq.html">
11 </head>
13 <body>
14 <h2>
15 <a href="index.html">
16 <i>Game of Trees</i></a>
17 Frequently Asked Questions
18 </h2>
19 <hr>
21 <h3>Quick Links:</h3>
23 <table>
24 <tr>
25 <a href="#special" >What makes Got special?</a><br>
26 <a href="#replacegit" >Does Got aim to replace Git?</a><br>
27 <a href="#code" >Does Got contain GPL-licensed Git code?</a><br>
28 <a href="#openbsd" >Why is Got OpenBSD-specific?</a><br>
29 <a href="#replacecvs" >Will Got replace use of CVS in OpenBSD?</a><br>
30 <a href="#pointless" >What's the point of all this? Why not just use Git?</a><br>
31 </tr>
32 </table>
34 <p>
35 <hr>
37 <h2 id="special"><a class="permalink" href="#special">What makes Got special?</a></h2>
39 <p>
40 Got has a number of properties that make it unique among version control
41 systems:
43 <ul>
44 <li>The code base is easy for OpenBSD developers to read, audit, and develop,
45 because it employs coding and design conventions familiar to those developers.
46 <li>The command-line interface is consistent and minimal. It has the least
47 amount of options possible while still being usable. We strive for sane
48 defaults that fit our workflow, instead of offering configurability for
49 every possible use case.
50 <li>Got is compatible with "bare" Git repositories, and thus integrates with
51 any tool built around the same format. Got is not a "Git porcelain".
52 Got is a new system which relies on prior art and takes what makes Git's
53 design great, leaves out the parts that make Git hard for us to use, and
54 invents new parts for an end result which serves our needs.
56 </ul>
58 <h2 id="replacegit"><a class="permalink" href="#replacegit">Does Got aim to replace Git?</a></h2>
59 <p>
60 No. Got does not aim to replace Git.
61 Got can be used instead of Git (for some tasks), or in addition to Git.
62 If you are already using Git and are happy with it, you don't need Got.
64 <p>
65 Anyone attempting to push an agenda of replacing Git with Got where Git
66 is already established would be highly delusional.
68 <h2 id="code"><a class="permalink" href="#code">Does Got contain GPL-licensed Git code?</a></h2>
70 <p>
71 No. We respect the copyright and licensing decisions of Git's authors,
72 just as we expect them to respect our own.
74 <p>
75 Most of Got's code was written from scratch, carries the copyright of its
76 authors, and is released under the ISC licence. Some parts of Got code
77 were lifted from existing code in the OpenBSD base system.
79 <p>
80 There is no truth in claims about GPL violations.
82 <p>
83 <h2 id="openbsd"><a class="permalink" href="#openbsd">Why is Got OpenBSD-specific?</a></h2>
84 <p>
85 Got's developers are OpenBSD developers who prefer to use a version
86 control system as part of their workflow which does not have the
87 inconveniences of CVS, with code internals that are as accessible to
88 them as most of the other code they touch while working on OpenBSD.
90 <p>
91 Anyone is free to use Got for any purpose they wish (provided they comply
92 with the licence) and provide feedback. But we will give much higher
93 priority to the requirements of OpenBSD developers over anyone else's.
94 Writing a classic general-purpose version control system is hard and
95 requires a lot of resources.
96 Limiting Got's scope strictly to our own requirements makes it much easier.
98 <p>
99 It is not uncommon for version control systems to be written with specific
100 target audiences in mind. Another example is
101 <a href="https://fossil-scm.org">fossil</a> which was written specifically
102 for the SQlite project.
104 <h2 id="replacecvs"><a class="permalink" href="#replacecvs">Will Got replace use of CVS in OpenBSD?</a></h2>
106 <p>
107 There is no way to know. It depends on how well Got will develop
108 and how well it will be received by the OpenBSD project at large.
110 <p>
111 Regardless, Got already serves the needs of its authors quite well,
112 and that is a benefit in itself.
114 <h2 id="pointless"><a class="permalink" href="#pointless">What's the point of all this? Why not just use Git?</a></h2>
115 <p>
116 If you are wondering why Got even exists, you can just ignore it.
118 <p>
119 You may have first learned about Game of Trees when visiting this web site.
120 This web site was published in August 2019, when Got was imported into the
121 OpenBSD ports tree to make it easily available for installation on OpenBSD
122 systems. The OpenBSD ports tree is public and hence this import brought
123 public attention to the Game of Trees project.
124 So from that point onward, it made some sense to publish a web site for it.
125 Before then, the project was already humming along quietly for 2.5 years.
126 We don't need to hear your opinion that our project is pointless because
127 Git is superior. Thank you!
128 </body>
129 </html>