All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Reynolds <jrey@linux.ibm.com>
To: Vijay Khemka <vijaykhemka@fb.com>,
	"Khetan, Sharad" <sharad.khetan@intel.com>,
	krtaylor <kurt.r.taylor@gmail.com>,
	"Matuszczak, Piotr" <piotr.matuszczak@intel.com>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: OpenBMC health statistics
Date: Tue, 30 Jun 2020 13:52:54 -0500	[thread overview]
Message-ID: <02d91b6a-c2ba-0239-a62e-a680f97bb009@linux.ibm.com> (raw)
In-Reply-To: <79C50A42-5BBB-40C0-8578-6659CA3DE1E1@fb.com>

On 6/29/20 3:20 PM, Vijay Khemka wrote:
> We can have a folder "how to" under guidelines and this document should fit there.

That makes sense to me.  I want document stuff for both system 
integrators (who put together firmware images) and system administrators 
(who perform BMC initial configurations, oversee BMC operation, etc.).  
We also need a place for documentation for things like how to use 
BMCWeb's mTLS feature which cuts across system integration and 
administration.  Details: https://github.com/ibm-openbmc/dev/issues/1531

- Joseph

>
> Regards
> -Vijay
>
> On 6/29/20, 11:51 AM, "openbmc on behalf of Khetan, Sharad" <openbmc-bounces+vijaykhemka=fb.com@lists.ozlabs.org on behalf of sharad.khetan@intel.com> wrote:
>
>      I agree. Based on description it appears the best fit is docs/development, as developers will need to provide right hooks.
>
>      If its really end-user focused, then it can perhaps go in userguide - which needs a lot more documentation 😊 for users.
>
>      Thanks,
>      -Sharad
>
>      -----Original Message-----
>      From: openbmc <openbmc-bounces+sharad.khetan=intel.com@lists.ozlabs.org> On Behalf Of krtaylor
>      Sent: Monday, June 29, 2020 10:54 AM
>      To: Matuszczak, Piotr <piotr.matuszczak@intel.com>; openbmc@lists.ozlabs.org
>      Subject: Re: OpenBMC health statistics
>
>      On 6/29/20 10:54 AM, Matuszczak, Piotr wrote:
>      > Hello,
>      >
>      > I would like to upload the OpenBMC health statistics design guide for people that would like to integrate the OpenBMC to their platforms. I would not like to put it into /docs/designs, since this is not exactly design how it will be implemented. This document was meant to guide the OpenBMC users how they can implement BMC health statistics themselves.
>
>      I don't see a problem with a guidelines/best practices type guide living in docs, but prob not in designs. Maybe in architecture or userguide or development? Kind of hard to say without seeing it. You could also always add it to the wiki.
>
>      Kurt Taylor (krtaylor)
>
>      >
>      > The question is, where would be the best place to upload such document?
>      >
>      > Piotr Matuszczak
>      > ---------------------------------------------------------------------
>      > Intel Technology Poland sp. z o.o.
>      > ul. Slowackiego 173, 80-298 Gdansk
>      > KRS 101882
>      > NIP 957-07-52-316
>      >
>
>

  reply	other threads:[~2020-06-30 18:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 15:54 OpenBMC health statistics Matuszczak, Piotr
2020-06-29 17:53 ` krtaylor
2020-06-29 18:49   ` Khetan, Sharad
2020-06-29 20:20     ` Vijay Khemka
2020-06-30 18:52       ` Joseph Reynolds [this message]
2020-06-30 19:51       ` Milton Miller II
2020-07-01 15:05         ` Matuszczak, Piotr
2020-07-01 17:25           ` Vijay Khemka

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=02d91b6a-c2ba-0239-a62e-a680f97bb009@linux.ibm.com \
    --to=jrey@linux.ibm.com \
    --cc=kurt.r.taylor@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=piotr.matuszczak@intel.com \
    --cc=sharad.khetan@intel.com \
    --cc=vijaykhemka@fb.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.
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.