From: "Jörg Rödel" <joro@8bytes.org>
To: svsm-devel@coconut-svsm.dev, linux-coco@lists.linux.dev
Subject: Development Plan Document
Date: Fri, 10 May 2024 12:17:26 +0200 [thread overview]
Message-ID: <Zj30Nqq3OS58DwpP@8bytes.org> (raw)
Hi,
As announced in the last meeting I am sharing a development plan
document which lists the in-progress and future work items to get
COCONUT-SVSM to the envisioned point.
The list is very likely incomplete and I am sure the document still has
a lot of room for improvement to become more useful, but I share it in
this initial state to discuss it early and align everyone on what is
planned.
The starting section lists the first priniciples I apply when thinking
about design choices. All following sections list work items.
The document is on GitHub in Markdown and PDF format:
https://github.com/joergroedel/svsm-governance/blob/dev-plan/draft-development-plan.md
https://github.com/joergroedel/svsm-governance/blob/dev-plan/draft-development-plan.pdf
The PDF version has a TOC which I find very useful. I encourage everyone
to have a look and bring any suggestions and questions to the next SVSM
development call on May 15th.
Regards,
Joerg
P.S.: The PDF file was created with pandoc from the Markdown file, so
the later contains some special markup which is not compatible
with GitHub Markdown.
next reply other threads:[~2024-05-10 10:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 10:17 Jörg Rödel [this message]
2024-05-14 9:06 ` [svsm-devel] Development Plan Document Jörg Rödel
2024-05-15 10:20 ` Reshetova, Elena
2024-05-15 11:59 ` Carlos López
2024-05-15 12:04 ` Reshetova, Elena
2024-05-15 12:14 ` Jörg Rödel
2024-05-17 10:01 ` Reshetova, Elena
2024-05-23 9:52 ` Jörg Rödel
2024-05-16 7:49 ` Jörg Rödel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zj30Nqq3OS58DwpP@8bytes.org \
--to=joro@8bytes.org \
--cc=linux-coco@lists.linux.dev \
--cc=svsm-devel@coconut-svsm.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.