From: Patrick Williams <patrick@stwcx.xyz>
To: Brad Bishop <bradleyb@fuzziesquirrel.com>
Cc: OpenBMC List <openbmc@lists.ozlabs.org>
Subject: Re: OTP-5: "OpenBMC TOF Proposal" Process
Date: Fri, 29 Oct 2021 14:07:12 -0500 [thread overview]
Message-ID: <YXxGYJbw1CDlWIp7@heinlein> (raw)
In-Reply-To: <20211029163720.ztct456rqf7tmezj@cheese>
[-- Attachment #1: Type: text/plain, Size: 1867 bytes --]
On Fri, Oct 29, 2021 at 12:37:20PM -0400, Brad Bishop wrote:
> On Wed, Oct 20, 2021 at 11:33:51PM -0500, Patrick Williams wrote:
>
> >## Definitions
> >
> >* OTP: An "OpenBMC TOF Proposal". Any request to the TOF should be framed as
> > an OTP as documented by this process.
> >
> >* Author: The individual(s) who write the initial draft of the OTP.
> >
> >* Champion: A member of the TOF, confirmed by the current TOF chair, who will
>
> What does confirmed mean here? The chair will document the champion
> somewhere? Also what if nobody on the TOF wants to volunteer to
> champion the proposal? One will be appointed and try their hardest to
> represent the interests of the person making the proposal?
This might need to be worded differently.
I anticipated a few scenarios:
1. Multiple individuals are all so excited about a proposal that they want
to volunteer to be the champion.
2. Only one individual is excited enough to volunteer to be a champion.
3. No one is excited enough to volunteer.
In #2, the "confirmation" is easy. In #1, the chair should pick one of them.
In #3, the chair should pick someone, yes, and as you said: try their hardest to
represent the interests of the person making the proposal. I recollect we've
discussed that others would be invited to the TOF discussions for their own
proposals, but I don't see where that is documented. If that is so, acting as
champion shouldn't even require buy-in to the proposal itself and means more of
coordinating the after-effects of the decision(s).
>
> > work with the Author while this process is being followed to ensure that
> > appropriate updates to the OTP are being made. If the Author is a member of
> > the TOF it is expected that they will also act as Champion to their own OTP.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-10-29 19:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 4:33 OTP-5: "OpenBMC TOF Proposal" Process Patrick Williams
2021-10-21 4:47 ` Patrick Williams
2021-10-29 16:29 ` Brad Bishop
2021-10-29 18:40 ` Patrick Williams
2021-10-29 18:49 ` Brad Bishop
2021-10-29 16:37 ` Brad Bishop
2021-10-29 19:07 ` Patrick Williams [this message]
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=YXxGYJbw1CDlWIp7@heinlein \
--to=patrick@stwcx.xyz \
--cc=bradleyb@fuzziesquirrel.com \
--cc=openbmc@lists.ozlabs.org \
/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.