public inbox for ~johnnyrichard/olang-devel@lists.sr.ht
 help / color / mirror / code / Atom feed
From: Johnny Richard <johnny@johnnyrichard.com>
To: ~johnnyrichard/olang-devel@lists.sr.ht
Cc: Johnny Richard <johnny@johnnyrichard.com>
Subject: [PATCH olang v1] docs: remove HACKING section from README file
Date: Mon,  9 Sep 2024 15:53:07 +0200	[thread overview]
Message-ID: <20240909135320.13021-1-johnny@johnnyrichard.com> (raw)

The README file is referencing an absent document (HACKING).  Since we
have the full documentation hosted at olang's website and there you can
find "how to build and contribute to the compiler", we can remove the
contribute section from the README and link the documentation.

The documentation can be found at https://o-lang.org and locally for
offline users.  Perhaps in a future change, we can reference the `info`
document on README file to help terminal users to read manual easily.

Signed-off-by: Johnny Richard <johnny@johnnyrichard.com>
---
 README | 38 +++++++++-----------------------------
 1 file changed, 9 insertions(+), 29 deletions(-)

diff --git a/README b/README
index d8ecde9..a451fe6 100644
--- a/README
+++ b/README
@@ -1,33 +1,13 @@
-olang
-=====
+O programming language
+======================
 
-The olang compiler.
+This project contains the compiler's source code.
 
-This project is licensed under GPLv3, read more on COPYRIGHT doc.
+For instructions on how to build and run the compiler, please read
+the manual on https://o-lang.org.
 
-For instructions on how to build and run the compiler, read the HACKING
-document.  Please don't use this project in production, it's still under
-development.
+In order to build the documentation locally, use `make docs`.  Once the build
+process is complete, you can find the generated documentation in the
+`docs/build` directory.
 
-CONTRIBUTING
-------------
-
-### CODE AND DISCUSSION
-
-This project uses mailing lists as main medium of communication. All mail
-archives can be found at https://sr.ht/~johnnyrichard/olang/lists.
-
-If you want to contribute to the source code, send plain text patch to:
-
-    ~johnnyrichard/olang-devel@lists.sr.ht
-
-Please use git-sendmail to send the patches.  You might want to configure your
-git to prevent silly mistakes:
-
-    $ git config sendemail.to "~johnnyrichard/olang-devel@lists.sr.ht"
-    $ git config format.subjectPrefix "PATCH olang"
-
-### IRC
-
-If you want to keep in contact with the community, feel free to join our
-channel #olang on LiberaChat IRC.
+NOTICE: The source code is licensed under GPLv3, read more on COPYRIGHT.

base-commit: 705f54e830e50d0c069cf1e2c76bda4204bd9dcc
-- 
2.46.0


             reply	other threads:[~2024-09-09 11:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-09 13:53 Johnny Richard [this message]
2024-09-10  3:25 ` Carlos Maniero

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240909135320.13021-1-johnny@johnnyrichard.com \
    --to=johnny@johnnyrichard.com \
    --cc=~johnnyrichard/olang-devel@lists.sr.ht \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.johnnyrichard.com/olang.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox