All of lore.kernel.org
 help / color / mirror / Atom feed
From: krtaylor <kurt.r.taylor@gmail.com>
To: Nancy Yuen <yuenn@google.com>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: OpenBMC Office Hours
Date: Wed, 23 Sep 2020 10:32:11 -0500	[thread overview]
Message-ID: <bb31004c-7f6a-e71e-c336-f75272e48913@gmail.com> (raw)
In-Reply-To: <CADfYTpFQoiQ6BcoVeT1Mi2oF+tORtjvbkmSkvyFB4FA_nR3p3Q@mail.gmail.com>

On 9/22/20 12:17 PM, Nancy Yuen wrote:
> Hi Team OpenBMC,
> 
> As Sai stated in his learning series post, OpenBMC can appear complex
> to people learning or evaluating OpenBMC.
> 
> I propose office hours, staffed by experienced volunteers where
> newcomers can dial in and ask questions.  The reasoning is newcomers
> aren't always sure what questions to ask and/or are intimidated by
> IRC.  Office hours would be a more direct, 1:1 forum for newcomers to
> get answers.  And of course volunteers would encourage the use of the
> mailing list and IRC for follow up discussions.

Thank you Nancy, this is great!

Kurt Taylor (krtaylor)

> I would like this to be low overhead for volunteers and I'm hoping to
> have enough volunteers to do monthly office hours, in the volunteer's
> local timezone.  Please sign up here if you're willing to volunteer.
> Ideally we would have 6-12 volunteers so it would just be one hour
> once or twice a year for everyone.  Please sign up by 10/16 @
> https://docs.google.com/spreadsheets/d/1hOzYDq6kRl8RCj9Kk_kzpiUjt5bABxVRH87StK2oKnY/edit?usp=sharing
> if you're interested in volunteering!
> 
> I'd also like each office hour to have signups, to make efficient use
> of everyone's time.  If there are no signups within 24hrs, the office
> hour would be canceled.
> 
> Thanks,
> Nancy
> 


  reply	other threads:[~2020-09-23 15:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22 17:17 OpenBMC Office Hours Nancy Yuen
2020-09-23 15:32 ` krtaylor [this message]
2020-10-20 19:43   ` Nancy Yuen

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=bb31004c-7f6a-e71e-c336-f75272e48913@gmail.com \
    --to=kurt.r.taylor@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=yuenn@google.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.