All of lore.kernel.org
 help / color / mirror / Atom feed
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 13:40:09 -0500	[thread overview]
Message-ID: <YXxACfWFxZ9MFbSv@heinlein> (raw)
In-Reply-To: <20211029162954.nkwfhzineypitwu5@cheese>

[-- Attachment #1: Type: text/plain, Size: 2609 bytes --]

On Fri, Oct 29, 2021 at 12:29:54PM -0400, Brad Bishop wrote:
> On Wed, Oct 20, 2021 at 11:33:51PM -0500, Patrick Williams wrote:
> >Any member of the OpenBMC community may give feedback by:
> >
> >1. Expressing a vote to the top post of the Github issue.
> >2. Providing grammatical suggestions to the Gerrit commit.
> >3. Responding on the mailing list with opinions on non-grammatical OTP content.
> 
> I think I would just like to see the entire conversation happen on the 
> list.  What would be the difficult parts with that?

I listed voting in Github to avoid emails like "+1", but to allow the TOF to get
a general sentiment.

I put "grammatical suggestions" elsewhere because:
    1. Again, reducing clutter.
    2. The post here is mostly a 'draft' anyhow, which needs a follow-up in
       Gerrit later on for documentation purposes.
    3. I've previously heard sentiment along the lines that "Gerrit is good for
       code review but not for discussions".  Grammar is 'code review'.

The purpose of having proposals on the mailing list, I think, was to give
broader awareness and because it is easier to follow discussions in email.
Having minor comments on the mailing list means others have to sift through
those uninteresting emails which may reduce the visibility into the primary
discussion(s).

If we want to combine 2+3 together to have all community comments on the mailing
list, I don't think it drastically changes the proposal and seems just as fine
an approach.

> 
> >4. (Least desirable) Providing off-line feedback to a TOF member(s).
> 
> If it is undesirable why do we have it?  Maybe we could list that 
> rationale to make sure this option is only used for those special cases?

Even if we don't spell it out it is still going to happen.  You can't stop two
people from talking to each other.  Some people are not going to be comfortable
expressing their opinion in public but they might have an individual on the TOF
they are comfortable confiding in.  The "least desirable" is to spell out that
the preference is for opinions to be expressed in public.

I can certainly drop this or reword it if the consensus is as such.

> 
> >Community members should refrain from:
> >
> >1. Voting on any comment in the Github issues beyond the top post.
> >2. Cluttering the mailing list discussion with grammatical suggestions.
> 
> I would agree this would be a minor annoyance but is it worth splitting 
> the review process across both Gerrit and the list?  My opinion?  no.

I understand.  See above.

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-10-29 18:41 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 [this message]
2021-10-29 18:49     ` Brad Bishop
2021-10-29 16:37 ` Brad Bishop
2021-10-29 19:07   ` Patrick Williams

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=YXxACfWFxZ9MFbSv@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.