aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorlthms <contact@thomasletan.fr>2017-12-26 18:06:02 +0000
committerThomas Letan <contact@thomasletan.fr>2018-01-24 08:11:18 +0100
commit9d80bf00711a937908675c89584ea36c0328e297 (patch)
tree13e6854529d83a8e9d8b3b283391ab410541de09
parentchore: Document the Puppet module (diff)
chore: lkn is using pijul and only pijul
-rw-r--r--README18
1 files changed, 5 insertions, 13 deletions
diff --git a/README b/README
index 62febca..65c135b 100644
--- a/README
+++ b/README
@@ -21,27 +21,19 @@ Table of Contents
═══════════════
lkn-core is a Free Software distributed under the terms of the
- AGPLv3+ License. The codebase is hosted at several locations,
- including a Github repository[1] and a self-hosted
- repository[2]. There also is a pijul repository[3], because I
- believe using pijul for lkn is a good way to contribute to pijul
- without having to write code.
+ AGPLv3+ License. The codebase is mainly hosted at the Nest[1], using
+ the pijul vcs[2].
If you want to submit a patch, feel free to do so in the manner you
find the more appropriate. For instance, you can:
- · open a Github pull request if you have an account.
- · send me a git remote I can fetch
· send me a patch using the Nest (pijul)
- · send me an email with your patches
+ · send me an email with your (binary) patches
The most important thing is: by providing me a patch, you agree it
may become available to the lkn-core users under the terms of the
AGPLv3+ license. Moreover, consider lkn-core will soon be published
to Hex.mp and so will be your contributions if they find their way
- to the master branch. Finally, regarding the fact that the codebase
- is kept under two DVCS, know that I might create a patch of your
- changes with the tool you didn't use.
+ to the master branch.
- [1] https://www.github.com/lkn-org/lkn-core
- [2] http://git.lthms.xyz/lkn/lkn-core
[3] https://nest.pijul.com/lthms/lkn-core
+ [3] https://pijul.org