summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2022-04-03 20:04:10 +0300
committerLars Wirzenius <liw@liw.fi>2022-04-03 20:04:10 +0300
commitf254abf7a9831fb42b7272d7b6120f7db93a0efb (patch)
tree3a6515d01ec94fdbc32dcaecc7b0de055c07f4dc
parent3ea47108720b845a3f2e7e83e58394f7595fb897 (diff)
downloadobnam.org-f254abf7a9831fb42b7272d7b6120f7db93a0efb.tar.gz
proposed meeting minutes for new iteration
Sponsored-by: author
-rw-r--r--blog/2022/04/03/planning.mdwn130
1 files changed, 130 insertions, 0 deletions
diff --git a/blog/2022/04/03/planning.mdwn b/blog/2022/04/03/planning.mdwn
new file mode 100644
index 0000000..5ca7217
--- /dev/null
+++ b/blog/2022/04/03/planning.mdwn
@@ -0,0 +1,130 @@
+[[!meta title="Iteration planning: April 4 &ndash; 17"]]
+[[!meta date="Sun, 03 Apr 2022 19:45:24 +0300"]]
+[[!tag meeting]]
+
+[[!toc levels=2]]
+
+# Assessment of the iteration that has ended
+
+[previous iteration]: /blog/2022/03/21/planning
+
+The goal of the [previous iteration][] was:
+
+> The goal of this iteration is to add a "root object" for a user's
+> backups, which lists the backup generations in order.
+
+This was completed.
+
+# Discussion
+
+## Current development theme
+
+The current theme of development for Obnam is **convenience**. The choices
+are performance, security, convenience, and tidy-up, at least
+currently.
+
+## `cachedir` utility
+
+Lars created a simple `cachedir` utility, in Rust. It's not yet on
+crates.io, and there's not yet a Debian package, as those are both
+blocked on a Subplot release. The git repository is at
+<https://gitlab.com/obnam/cachedir>.
+
+
+# Repository review
+
+Lars reviewed all the open issues, merge requests, and CI pipelines
+for all the projects in the Obnam group on gitlab.com.
+
+## [Container Images](https://gitlab.com/obnam/container-image)
+
+* Open issues: 0
+* Merge requests: 0
+* Additional branches: 0
+* CI: OK, ran on Monday, March 28
+
+## [obnam.org](https://gitlab.com/obnam/obnam.org)
+
+* Open issues: 0
+* Merge requests: 0
+* Additional branches: 0
+* CI: not defined
+
+## [obnam-benchmark](https://gitlab.com/obnam/obnam-benchmark)
+
+* Open issues: 11
+* Merge requests: 0
+* Additional branches: 0
+* CI: not defined
+
+## [cachedir](https://gitlab.com/obnam/cachedir)
+
+* Open issues: 0
+* Merge requests: 0
+* Additional branches: 0
+* CI: not defined
+
+## [summain](https://gitlab.com/obnam/summain)
+
+* Open issues: 0
+* Merge requests: 0
+* Additional branches: 0
+* CI: not defined
+
+## [obnam](https://gitlab.com/obnam/obnam)
+
+* Open issues: 54
+* Merge requests: 2
+ - [[!mr 226]] - _Log some performance measurements_
+ - to be merged on Monday
+* Additional branches: 0
+* CI: OK
+
+# Goals
+
+## Goal for 1.0 (not changed this iteration)
+
+The goal for version 1.0 is for Obnam to be an utterly boring backup
+solution for Linux command line users. It should just work, be
+performant, secure, and well-documented.
+
+It is not a goal for version 1.0 to have been ported to other
+operating systems, but if there are volunteers to do that, and to
+commit to supporting their port, ports will be welcome.
+
+Other user interfaces is likely to happen only after 1.0.
+
+The server component will support multiple clients in a way that
+doesn’t let them see each other’s data. It is not a goal for clients
+to be able to share data, even if the clients trust each other.
+
+## Goal for the next few iterations (not changed for this iteration)
+
+The goal for next few iterations is to have Obnam be easier and safer
+to change, both for developers and end users. This means that
+developers need to be able to make breaking changes without users
+having to suffer. User shall be able to migrate their data, when they
+feel it worthwhile, not just because there is a new version.
+
+## Goal for this iteration (new for this iteration)
+
+The goal for this iteration is to further improve our ability to make
+changes to Obnam safely.
+
+# Commitments for this iteration
+
+Lars intends to work on the "root object" change, as described above.
+This will affect, and hopefully resolve the following issues:
+
+* [[!issue 202]] - _Server HTTP API is not versioned_
+ - Lars will make all the current HTTP API end points be verisoned:
+ `/v1/chunks` etc.
+* [[!issue 203]] - _No migration to new checksum types_
+ - Lars will add a prefix to all checksum, and add a second supported
+ checksum type. User will be able to configure which checksum is
+ used for new chunks, while old chunks are used with whatever they
+ were labelled as.
+
+# Meeting participants
+
+* Lars Wirzenius