commit 76f4d96c0d35611360f16e50db97eb7066b66ca7
from: Stefan Sperling <stsp@stsp.name>
date: Tue Aug 06 08:12:03 2019 UTC

device goals into guidelines and long-term goals; add current goal

commit - c5a9365dd965a7cfed5a5bae3cc115de98a21894
commit + 76f4d96c0d35611360f16e50db97eb7066b66ca7
blob - 9e6e902a1c1463cf0b045c65c15759e6136c6a51
blob + 016f2cc9edc53ad0251ef1cbac0d8881d8d390b3
--- goals.html
+++ goals.html
@@ -15,7 +15,37 @@ Goals
 </h2>
 <hr>
 
+<p id="callout">
+Current goal:
+<br>
+Find a handful of developers who want to regularly use Got for their
+work on OpenBSD. Improve version control operation based on their feedback.
+
+<h3>Project guidelines</h3>
 <ul>
+<li>
+Follow <a href="https://www.openbsd.org">OpenBSD</a>'s security practices
+and coding style.
+<ul>
+<li>Use a development process based on code review in email.
+<li>Consistently use
+<a href="https://man.openbsd.org/pledge">pledge(2)</a> and
+<a href="https://man.openbsd.org/unveil">unveil(2)</a> across the code base.
+<li>Use privilege-separation when parsing repository data from network or disk.
+</ul>
+<li>
+Keep the entire code base BSD-licenced.
+</ul>
+
+<p>
+<h3>Long-term goals</h3>
+<ul>
+<li>
+Remain on-disk compatible with bare
+<a href="https://git-scm.com">Git</a> repositories.
+<ul>
+<li>Don't bother with Git-compatibility beyond this requirement.
+</ul>
 <li>Provide a complete version control tool suite for OpenBSD.
 <ul>
 <li>Intuitive command line interface for required version control operations
@@ -28,37 +58,20 @@ committed changes (<a href="tog.1.html">tog</a>).
 changes to a cascade of public and private mirrors.
 </ul>
 <li>
-Remain on-disk compatible with bare
-<a href="https://git-scm.com">Git</a> repositories.
+Consider workflow requirements of OpenBSD developers.
 <ul>
-<li>Don't bother with Git-compatibility beyond this requirement.
-</ul>
-<li>
-Consider workflow requirements of <a href="https://www.openbsd.org">OpenBSD</a>
-developers.
-<ul>
 <li>Strong built-in support for a centralized repository model.
 <li>Keep things easy for developers who don't need branches.
 <li>Support local branches for developers who need them.
 <li>Support &quot;-stable&quot; release branches.
 <li>Support features required by the OpenBSD project's build infrastructure.
 </ul>
-<li>Implement authenticated and encrypted network communications only.
+<li>Implement authenticated and encrypted network communications.
 <ul>
 <li>Provide <a href="https://openssh.com">SSH</a> and optional
 <a href="https://libressl.org">TLS</a> support for cloning repositories
 and pulling changes.
 <li>Exclusively rely on SSH for pushing changes.
+<li>Do not implement any support for plaintext network communications.
 </ul>
-<li>
-Follow OpenBSD's security practices and coding style.
-<ul>
-<li>Use a development process based on code review in email.
-<li>Consistently use
-<a href="https://man.openbsd.org/pledge">pledge(2)</a> and
-<a href="https://man.openbsd.org/unveil">unveil(2)</a> across the code base.
-<li>Use privilege-separation when parsing repository data from network or disk.
 </ul>
-<li>
-Keep the entire code base BSD-licenced.
-</ul>