summaryrefslogtreecommitdiff
path: root/issues
diff options
context:
space:
mode:
authorPjotr Prins2022-02-02 00:29:10 -0600
committerPjotr Prins2022-02-02 00:29:21 -0600
commit56ee4c68a2893e3803a35f63312256c9f5de2524 (patch)
treeae1f1ac215ecae4e9706b2b5d6815fddeec0ea20 /issues
parent89a382723fb3c785fa674abbb2bd244f7a455068 (diff)
downloadgn-gemtext-56ee4c68a2893e3803a35f63312256c9f5de2524.tar.gz
README
Diffstat (limited to 'issues')
-rw-r--r--issues/README.gmi2
1 files changed, 1 insertions, 1 deletions
diff --git a/issues/README.gmi b/issues/README.gmi
index 434bd2f..6bbff18 100644
--- a/issues/README.gmi
+++ b/issues/README.gmi
@@ -24,7 +24,7 @@ where someone is rude and lacks obvious knowledge about the free software effort
With our new gemini tracker we own the issue reporting space. People can submit a request to report an issue and we can decide whether it belongs there or not. Takes a little more effort on the submitter too! But not too much - you have to know git or edit, fork or clone in github. The downside may be that some normal users feel they need to do too much. In that case one can always send an E-mail to the mailing list instead - or we create a web form that does that. In the next step we can file E-mails as issues ourselves.
-Key point is that the issue tracker is to track issues.
+Key point is that the issue tracker is meant to track issues owned by the project.
## Example