aboutsummaryrefslogtreecommitdiff
path: root/archive/2021-12-21--meeting-minutes
blob: c3fd7c246d5e7ae18881b6b5c32d2bb1e7e89f88 (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
Date: 2021-12-21 1200 UTC
Meet: https://meet.sigsum.org/sigsum
Chair: rgdd

Agenda
	* Hello
	* Status round
	* Decisions
	* Next steps

Hello
	* rgdd
	* ln5

Status round
	* [rgdd] sigsum-lib-go
		* tag v0.0.1
			* pretty much what we had before but cleaner
			* thinking about reverting to a "dumber ascii parser implementation"
	* [rgdd] sigsum-log-go
		* tag v0.3.3
			* added experimental checkpoint endpoint
			* deployed by ln5
		* most recent commits (not yet tagged)
			* picked-up sigsum-lib-go v0.0.1
			* some refactoring as a result
	* [rgdd] milestone 'production log' and associated work packages
		* https://git.sigsum.org/sigsum/tree/archive/2021-12-21-milestone-prod-log
	* [ln5] onboarding, email stack and investigating database failover

Decisions
	* Decision: milestone 'production log' with associated work packages (~5 months)
		* see detailed description in the above status round link
		* 1) rgdd + ln5
		* 2) ln5
		* 3) ln5
		* 4) ln5 (implement minor fixes) + anwesha (sysadmin sides of alerts)
		* 5) rgdd + undecided

Next steps
	* [rgdd] implement ssh signing format in sigsum-lib-go
	* [rgdd, ln5] address open design TODOs that are marked as in-scope
	* [ln5] list manager distributing our list properly
	* [ln5] sigsum-witness-py using the SSH signing format
	* [ln5] continued investigation of database failover and hardware procurement
	* [ln5] git-bug, use it or not?
	* [anwesha] test environment for pads with ansible