1 Game of Trees (Got) is a version control system which prioritizes ease
2 of use and simplicity over flexibility.
3 
4 Got is still under development; it is being developed exclusively
5 on OpenBSD and its target audience are OpenBSD developers. Got is
6 ISC-licensed and was designed with pledge(2) and unveil(2) in mind.
7 
8 Got uses Git repositories to store versioned data. At present, Got
9 supports local version control operations only. Git can be used
10 for any functionality which has not yet been implemented in Got.
11 It will always remain possible to work with both Got and Git on
12 the same repository.
13 
14 To compile the Got tool suite on OpenBSD, run:
15 
16  $ make obj
17  $ make
18  $ make install
19 
20 This will install the following commands:
21 
22  got, the command line interface
23  tog, an ncurses-based interactive Git repository browser
24  several helper programs from the libexec directory
25  man pages (only installed if building sources from a Got release tarball)
26 
27 A Got release tarball will install files under /usr/local by default.
28 A build started in Got's Git repository will install files under ~/bin.
29 
30 Tests will pass only after 'make install' because they rely on installed
31 binaries in $PATH. Tests in the cmdline directory currently depend on git(1).
32 
33  $ doas pkg_add git
34  $ make regress
35 
36 To test with packed repositories, run:
37 
38  $ make regress GOT_TEST_PACK=1
39 
40 Man page files in the Got source tree can be viewed with 'man -l':
41 
42  $ man -l got/got.1
43  $ man -l got/git-repository.5
44  $ man -l got/got-worktree.5
45  $ man -l tog/tog.1
46 
47 EXAMPLES in got.1 contains a quick-start guide for OpenBSD developers.
48 
49 
50 Game of Trees Web (Gotweb) is a CGI program which displays repository data
51 and is designed to work with httpd(8) and slowcgi(8).
52 
53 To compile gotweb on OpenBSD, run:
54 
55  # pkg_add kcgi
56  $ make web
57  # make web-install
58 
59 This will create the following files:
60   the CGI program /var/www/cgi-bin/gotweb/gotweb
61   helper programs from the libexec directory in /var/www/cgi-bin/gotweb/libexec
62   several template files in /var/www/cgi-bin/gw_tmpl/
63   html, css, and image files in /var/www/htdocs/gotweb/
64   the directory /var/www/tmp/
65   man pages (only installed if building sources from a Got release tarball)
66 
67 Documentation is available in manual pages:
68 
69  $ man -l gotweb/gotweb.8
70  $ man -l gotweb/gotweb.conf.5
71 
72 
73 Guidelines for reporting problems:
74 
75 All problem/bug reports should include a reproduction recipe in form of a
76 shell script which starts out with an empty repository and runs a series of
77 Got and/or Git commands to trigger the problem, be it a crash or some other
78 undesirable behaviour.
79 
80 The regress/cmdline directory contains plenty of example scripts.
81 An ideal reproduction recipe is written as an xfail ("expected failure")
82 regression test. For a real-world example of an xfail test, see commits
83 4866d0842a2b34812818685aaa31d3e0a966412d and
84 2b496619daecc1f25b1bc0c53e01685030dc2c74 in Got's history.
85 
86 Please take this request very seriously; Ask for help with writing your
87 regression test before asking for your problem to be fixed. Time invested
88 in writing a regression test saves time wasted on back-and-forth discussion
89 about how the problem can be reproduced. A regression test will need to be
90 written in any case to verify a fix and prevent the problem from resurfacing.
91 
92 It is also possible to write test cases in C. Various examples of this
93 exist in the regress/ directory. Most such tests are unit tests; it is
94 unlikely that a problem found during regular usage will require a test
95 to be written in C.
96 
97 Some areas of code, such as the tog UI, are not covered by automated tests.
98 Please always try to find a way to trigger your problem via the command line
99 interface before reporting a problem without a written test case included.
100 If writing an automated test really turns out to be impossible, please
101 explain in very clear terms how the problem can be reproduced.
102 
103 Mail problem reports to: gameoftrees@openbsd.org
104 
105 
106 Guidelines for submitting patches:
107 
108 Mail patches to: gameoftrees@openbsd.org
109 Pull requests via any Git hosting sites will likely be overlooked.
110 Please keep the intended target audience in mind when contributing to Got.
111 
112 
113 Subscribing to the gameoftrees@openbsd.org mailing list:
114 
115 The mailing list is used for patch reviews, bug reports, and user questions.
116 To subscribe, send mail to majordomo@openbsd.org with a message body of:
117 subscribe gameoftrees
118 
119 See https://www.openbsd.org/mail.html for more information.