aboutsummaryrefslogtreecommitdiff
path: root/archive
diff options
context:
space:
mode:
authorRasmus Dahlberg <rasmus.dahlberg@kau.se>2021-09-21 14:15:57 +0200
committerRasmus Dahlberg <rasmus.dahlberg@kau.se>2021-09-21 14:15:57 +0200
commit44b530a8ccb3ff6f05c1b4b4ca450f8c60d329c8 (patch)
tree522890b510a08b6bace265c3706bbbc136b45601 /archive
parent2dcedf0a26918eec1da61534e1f1178aa0db0c60 (diff)
persisted meeting minutes
Diffstat (limited to 'archive')
-rw-r--r--archive/2021-09-21--meeting-minutes54
1 files changed, 54 insertions, 0 deletions
diff --git a/archive/2021-09-21--meeting-minutes b/archive/2021-09-21--meeting-minutes
new file mode 100644
index 0000000..5a9feba
--- /dev/null
+++ b/archive/2021-09-21--meeting-minutes
@@ -0,0 +1,54 @@
+Date: 2021-09-21, 1300 CEST
+Meet: membarrier.verkligendata.se/sigsum
+Chair: rgdd
+
+Agenda
+ * Hello
+ * Status round
+ * Discuss
+ * Next steps
+
+Hello
+ * rgdd
+ * rohonk
+ * ln5
+
+Status round
+ * [rgdd] started to think about project announcement
+ * [ln5] www.sigsum.org serves our hugo website
+ * [rohonk] reading up on CM, can it be used to paramerize a security proof?
+
+Discuss
+ * Project announcement ideas
+ * How do other projects announce themselves?
+ * WireGuard announcement was good
+ * Done on the mailing list
+ * Short and down to the point
+ * Max 500 words looks like a good goal.
+ * Decision: rgdd is drafting an email, to go on the mailiing list.
+ * Merits of using GET, as oposed to POST, for the three get-* endpoints
+ * Initial thought was to not have, e.g., a percent-encoding parser too
+ * Only having GET endpoints would make URLs self-describing
+ * Useful if you are storing and/or sharing URLs to refer to data while debugging
+ * Decision: think about this until next week
+ * How about requiring gpg signing of git commits?
+ * How about requring *some* signing of git commits
+ * And of course released tar balls and such?
+ * Because maybe not gpg?
+ * Decision: defer for now, also think about alternatives to gpg
+ * (rgdd mentions that mabye we need to fix contribution guidelines)
+ * Picking a descriptive URL for meeting minutes pads
+ * Decision: <pad-link>/sigsum-YYYYMMDD
+ * RPKI transparency? RIPE discussion, but isn't CF already doing this?
+ * Decision: reach out after project announcement
+
+Next steps
+ * [rgdd] document thoughts that go into project anouncement, propose drafty mail
+ * [ln5] Get mailing list archive up and running, along with jitsi and pads services
+ * [rohonk] review design.md in design-framing branch, continued work on sec proof.
+
+Other useful links
+ * [ln5, rgdd] An RPKI transparency log project?
+ * https://www.ripe.net/ripe/mail/archives/routing-wg/2021-September/004397.html
+ * https://blog.cloudflare.com/rpki-details/
+ * https://ct.cloudflare.com/logs/cirrus