openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: krtaylor <kurt.r.taylor@gmail.com>
To: Sai Dasari <sdasari@fb.com>, Openbmc <openbmc@lists.ozlabs.org>
Subject: Re: OpenBMC Learning Series
Date: Thu, 11 Jun 2020 08:04:20 -0500	[thread overview]
Message-ID: <e1dc043d-9250-7c81-9af6-30dc60fdc4bb@gmail.com> (raw)
In-Reply-To: <14ED9A00-19D1-43BF-ACFE-5B9937188DD4@fb.com>

On 6/3/20 1:10 PM, Sai Dasari wrote:
> Team,
> 
> Our OpenBMC community continues to grow at rapid pace as can be observed 
> by various metrics like number of CCLAs, industry adoption rate, 
> design/code contributions, numerous technical conversations over Mailing 
> List/IRC/Gerritt, and more. Because of this rapid growth the project 
> might appear to be a bit complex for a new contributor evaluating our 
> stack. I believe there are multiple ongoing efforts of reducing this 
> barrier for a potential contributor to ramp them up quickly on this 
> stack that includes documentation, wiki pages, tutorials in our github repo.
> 
> In addition to these ongoing efforts, I propose to start a video based 
> learning series that aims to introduce OpenBMC stack for a potential 
> contributor.  I hope such video series will help disseminate tribal 
> knowledge that we built in this community over a period of time and ramp 
> up the new contributors quickly. To make this series useful, I seek

Thanks Sai!

I think this is a great idea. Feel free to reference the Community Best 
Practices video series I recorded - available here:

https://github.com/openbmc/openbmc/wiki/Presentations

Kurt Taylor (krtaylor)

> volunteer speakers who are interesting in sharing their expertise and 
> help plan this series to be more effective. For those of you who are 
> interested, please add yourself as speaker with title/description before 
> 6/17 @ 
> https://docs.google.com/spreadsheets/d/1RRO5cgutKE7zRPcjcFjrNn-GI5AYoW0FivEZJe_EyWs/edit?usp=sharing
> 
> Some topics for consideration include OpenBMC project overview, Software 
> stack architecture, community developer guidelines, Repo structure and 
> guidelines, Usage of Yocto in OpenBMC,  Usage of D-Bus in OpenBMC, C++ 
> coding standards in OpenBMC,  IPMI sub-system, Redfish sub-system, Using 
> QEMU effectively, Sensor sub-system, Best practices in debugging, 
> Logging, metrics/telemetry etc. And this is not an exhaustive list and 
> feel free to add any topic that you plan to share with community.
> 
> I will reach out to volunteer speakers and facilitate logistics and 
> update the ML with next steps. Please let me know for any info regarding 
> this effort.
> 
> Thanks,
> Sai.
> 

  reply	other threads:[~2020-06-11 13:04 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 18:10 OpenBMC Learning Series Sai Dasari
2020-06-11 13:04 ` krtaylor [this message]
2020-06-11 13:11 ` Joel Stanley
2020-08-19 17:46 Sai Dasari
2020-08-22  5:48 ` Sai Dasari
2020-08-26 19:11   ` Sai Dasari
2020-08-26 19:19     ` Vijay Khemka
2020-08-26 19:22       ` Sai Dasari
2020-08-26 19:25         ` Vijay Khemka
2020-08-27 21:10     ` Sai Dasari
2020-08-28 16:14       ` Vijay Khemka
2020-09-02 16:56     ` Sai Dasari
2020-09-03 22:16       ` Sai Dasari
2020-09-09 16:58         ` Sai Dasari
2020-09-10 18:33           ` James Feist
2020-09-10 20:49             ` Andrei Kartashev
2020-09-11 15:52               ` James Feist
2020-09-11 17:20                 ` Andrei Kartashev
2020-09-10 19:49           ` Sai Dasari
2020-09-16  7:36             ` Sai Dasari
2020-09-23 16:10               ` Sai Dasari
2020-09-30 17:00                 ` Sai Dasari
2020-10-07 15:53                   ` Sai Dasari
2020-10-14  6:48                     ` Sai Dasari
2020-10-21  2:07                       ` Sai Dasari
2020-10-28 16:39                         ` Sai Dasari
2020-11-04 17:33                           ` Sai Dasari
2020-11-05 11:37                             ` Thomaiyar, Richard Marian
2020-11-05 16:58                               ` Sai Dasari
2020-11-11 17:43                                 ` Sai Dasari
2020-12-16 17:26                             ` Sai Dasari

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=e1dc043d-9250-7c81-9af6-30dc60fdc4bb@gmail.com \
    --to=kurt.r.taylor@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=sdasari@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 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).