openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: George Liu <liuxiwei1013@gmail.com>
To: Ivan Mikhaylov <i.mikhaylov@yadro.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Brad Bishop <bradleyb@fuzziesquirrel.com>
Subject: Re: Request new repo for Audit function
Date: Fri, 13 Aug 2021 17:14:10 +0800	[thread overview]
Message-ID: <CANFuQ7BXy1s6SKLLgwah5p2EpX7_yBK4CUOHxi4J+LQ6r2OuCw@mail.gmail.com> (raw)
In-Reply-To: <916fc23f02ec749ecccf70dff356daa400026b28.camel@yadro.com>

On Fri, Aug 13, 2021 at 4:31 PM Ivan Mikhaylov <i.mikhaylov@yadro.com> wrote:
>
> On Fri, 2021-08-13 at 14:09 +0800, George Liu wrote:
> > On Fri, Aug 13, 2021 at 11:22 AM Milton Miller II <miltonm@us.ibm.com> wrote:
> > >
> > >
> > > Reply below
> > >
> > > -------- Original Message --------
> > > From: George Liu
> > > Date: Thu, August 12, 2021 7:52 PM -0500
> > >
> > >
> > > Hi Brad:
> > >
> > > We have a requirement to implement an Audit function, I found that
> > > there is a design doc[1], but there is no code to implement it.
> > >
> > > Could you create a new repo for Audit function?
> > > eg: phosphor-audit
> > >
> > > [1]: https://github.com/openbmc/docs/blob/master/designs/phosphor-audit.md
> > >
> > > thx - George Liu
> > >
> > > -------- End of Original Message --------
> > >
> > > Hi George.
> > >
> > >
> > > Please update the design with consideration for inclusive naming[2] before
> > > submitting code for it, as it uses depreciated terminology in it's external
> > > control interface.
> > >
> > > I see this design was merged almost 2 years ago before this policy was in
> > > place but as you said it hasn't been exposed by the community yet so we won't
> > > need to maintain compatibility with prior implementations.
> >
> > Thanks for your advice.
> > I will read and update this design doc ASAP :)
> >
> > >
> > >
> > > [2]
> > > https://github.com/openbmc/docs/blob/master/CONTRIBUTING.md#inclusive-naming
> > >
> > > Thanks,
> > > Milton
> > >
> > >
>
> George, there is answer about same question in this thread
> https://lists.ozlabs.org/pipermail/openbmc/2020-March/020839.html .
> Should be part of phosphor-logging.

Okay, Let me check, thanks so much

>
> Thanks.
>

  reply	other threads:[~2021-08-13  9:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-13  3:21 Request new repo for Audit function Milton Miller II
2021-08-13  6:09 ` George Liu
2021-08-13  8:41   ` Ivan Mikhaylov
2021-08-13  9:14     ` George Liu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-13  0:51 George Liu
2021-08-16 14:25 ` Patrick Williams
2021-08-17  0:51   ` George Liu

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=CANFuQ7BXy1s6SKLLgwah5p2EpX7_yBK4CUOHxi4J+LQ6r2OuCw@mail.gmail.com \
    --to=liuxiwei1013@gmail.com \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=i.mikhaylov@yadro.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 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).