diff options
| -rw-r--r-- | issues/README.gmi | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/issues/README.gmi b/issues/README.gmi index 0e3875f..4b7dd35 100644 --- a/issues/README.gmi +++ b/issues/README.gmi @@ -1,9 +1,30 @@ # Designing an issue tracker on gemini +Why do we want to consolidate issue trackers and kanban boards using gemini+git? Several reasons: + +* Get rid of web service dependencies (in our case github issue tracker and trello kanban) +* Track issues in text files - edit with your favourite editor +* Provide our own viewer - the github issue tracker and trello boards are not very configurable, e.g. what to do with a stale issue - why do we need to run an action? +* Own the trackers + +Now the last one may be the most important. Currently anyone can post on our issue trackers and you get issues like + +=> https://github.com/genetics-statistics/GEMMA/issues/250 Not read the docs example + +Where someone posts who has not read the manual (sorry for the exposition). Or from another project I am involved in + +=> https://github.com/vcflib/vcflib/issues/206 Rude example + +where someone is very rude and lacks obvious knowledge about the free software effort (not sorry about exposing this one - luckily this is a small minority). 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 fork and clone in github. The downside may be that some normal users feel they need to do too much. In that case send an E-mail instead - that is what they do anyway. We can file E-mails as issues ourselves. + +## Example + I added a first issue here: => https://github.com/genenetwork/gn-gemtext-threads/blob/main/issues/database-not-responding.gmi +## Process + I am thinking we just use git to pull out dates and people contributions (pjotrp wrote ...) for display in a document/web page. Assuming people add to the doc at the bottom that should not be too hard. |