blob: 9e91ff59efb0f2698590d13a3be6c60e5bb60f3d (
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
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
|
Meeting agenda template.
Agenda
* Hello
* Status round
* Discuss
* Next steps
Hello
* <insert nick here>
Status round
* <insert status report here>
Discuss
* <insert discuss item here>
Next steps
* <insert next step here>
Other useful links
* <insert useful link here>
Weekly process.
* Our conversations happen on irc
* Use etherpads if it is helpful, e.g., to summarize a discusison, conclusion, etc.
* Use 60 days expiry
* Add link to meeting agenda if it should be persisted ("status report")
* We keep the next meeting agenda etherpad in our irc channel topic
* Tuesday
* Open video/voice meeting
* Jitsi
* 1300-1400 CEST
* We keep the meeting link in the announced meeting pad
* After the meeting
* Meeting chair persists all etherpad links that were added to the agenda as is
* Meeting chair cleans up the resulting meeting minutes if need be
* Meeting chair persists the meeting minutes etherpad
* Meeting chair posts the link to the next week's meeting agenda / minutes on irc.
fixme: think about git process, issues, PRSs, etc., based on where we move.
* CONTRIBUTING.md?
* defer until after vaccay, stay on github for now
* create new repos there as we see fit
fixme: do we need a mailing list?
* defer until after vaccay
Repos
* sigsum, sigsum-project?
* redirect sigsum.org here for now?
* example structure below
$ tree
.
├── archive
│ ├── 2021-06-22--minutes
│ ├── 2021-06-22-sketch-on-how-we-work-together
│ └── 2021-06-22-witness-timestamp-verification
├── doc
│ ├── api.md
│ ├── claimant.md
│ └── design.md
├── LICENCE.md
├── README.md
└── website
* sigsum-lib-go
* cmd: sigsum-format
* cmd: sigsum-verify
* sigsum-log-go
* Trillian personality
* sigsum-witness-py
|
