From: Alyssa Ross <hi@alyssa.is>
To: Ville Ilvonen <ville.ilvonen@unikie.com>
Cc: devel@spectrum-os.org
Subject: Re: [PATCH] Documentation: Architecture Decision Record
Date: Wed, 13 Jul 2022 09:53:20 +0000 [thread overview]
Message-ID: <20220713095320.nul2dhfcbw6elgut@eve> (raw)
In-Reply-To: <CAP-nJwGO6xS7+ELsdeN5BkxHY+PGaqXfe=RQKdQ6NdUxiJrr+g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]
On Wed, Jul 13, 2022 at 12:35:47PM +0300, Ville Ilvonen wrote:
> On Tue, Jul 12, 2022 at 9:11 PM Alyssa Ross <hi@alyssa.is> wrote:
> >
> > On Fri, Jul 08, 2022 at 02:02:15PM +0300, Ville Ilvonen wrote:
> > > * ADRs based on discussions with Alyssa
> > > * A note on ADRs to architecture.adoc
> > >
> > > Signed-off-by: Ville Ilvonen <ville.ilvonen@unikie.com>
> >
> > Hi Ville, thanks for taking the lead on these.
> >
> > I've been wondering whether it would be better to only take accepted
> > ADRs into the Spectrum repository, and leave proposed ones for
> > discussion on the list until they're ready to be accepted. I think that
> > would make the distinction between them clearer. What do you think?
>
> I was thinking separation by status when writing the PR.
> Maybe restructuring to folders like
> Documentation/adr/accepted
> Documentation/adr/proposed
> ...
> would make sense?
I've thought about this a bit more, and decided that it's fine to have
proposed ADRs in the repo. I was concerned about the in-between state
an ADR could find itself in when it's been submitted but I haven't
applied the patch yet, but having thought about it more, I don't think
having a stage of "being accepted for discussion" is a bad thing.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-07-13 9:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 11:02 Ville Ilvonen
2022-07-12 18:11 ` Alyssa Ross
2022-07-13 9:35 ` Ville Ilvonen
2022-07-13 9:53 ` Alyssa Ross [this message]
2022-07-13 11:04 ` Ville Ilvonen
2022-07-22 11:32 ` Alyssa Ross
2022-07-22 11:37 ` Alyssa Ross
2022-07-13 10:04 ` Alyssa Ross
2023-01-03 7:03 ` Adam Joseph
2023-01-06 13:27 ` Alyssa Ross
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=20220713095320.nul2dhfcbw6elgut@eve \
--to=hi@alyssa.is \
--cc=devel@spectrum-os.org \
--cc=ville.ilvonen@unikie.com \
/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.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).