blob: 0e3875f965caa5d5102e94ebe007e5cdbae5cd94 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
|
# Designing an issue tracker on gemini
I added a first issue here:
=> https://github.com/genenetwork/gn-gemtext-threads/blob/main/issues/database-not-responding.gmi
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.
At the top we could add tags:
* assigned: pjotrp, zachs
* keywords: critical bug, in progress
* milestone: 1.1
Which we can use to generate lists of links.
Make sense?
For the kanban board we can simply use the keywords. Override/add with a separate
* kanban: Brain storm
Keywords are flexible, but common wons are
* request
* bug
* critical bug
* enhancement
* in progress
* testing
* later
* documentation
* help wanted
* closed
the keyword statement may have aliases, such as tag and kanban. To undo a keyword simply remove them from the file.
Can't think of anything more to add to make it really useful :)
## Tracking information
Git can do all of that. A viewer may benefit from serial git information, therefore it is recommended to add information to the end of the file.
## Closing issues
Moving an issue file will disconnect the git record. Therefore simple add
* tag: closed
## Converting
### Converting issues from a github issue tracker
=> https://github.com/mattduck/gh2md Github to markdown dump
|
