All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sai Dasari <sdasari@fb.com>
To: Andrew Geissler <geissonator@gmail.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Stewart Smith <stewart@linux.vnet.ibm.com>,
	Joel Stanley <joel.stan@gmail.com>, Jeremy Kerr <jk@ozlabs.org>
Subject: Re: OpenBMC Hackathon @ OpenPower Summit?
Date: Tue, 25 Sep 2018 17:16:37 +0000	[thread overview]
Message-ID: <937C5B58-38CB-44C0-8F49-63019A5049B3@fb.com> (raw)
In-Reply-To: <CALLMt=rEH2wBzB5RrHJTG93AgHJB-DaG7pJVs9_UNrktpoau1g@mail.gmail.com>

On 9/25/18, 7:24 AM, "Andrew Geissler" <geissonator@gmail.com> wrote:
 
    I've started the series of doc updates in
    https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.openbmc-2Dproject.xyz_-23_c_openbmc_docs_-2B_12994&d=DwIFaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=D804Bb_g8FkIaCjjb_rg7A&m=yr3JnQxLLUESx16cxXCX4hiQyvLUsXhL5IeDO-om_c8&s=vylILOVOswtaPGyz22ROUwwwn0c7ja3Z2F6CcSPYpss&e=
    
    Feedback always welcome. The goal is to have small tutorials that
    people can follow to get up
    and going with OpenBMC development.  We'll be walking through these
    with people at the upcoming summit.
Thanks Andrew! Love this great effort to onboard new engineers to the community!!
    
    Future docs I'm thinking are:
    - Adding a new systems (bitbake layer, kernel changes)
    - Systemd phosphor service manipulation and usage
    - Debugging
    - Maybe taking someone through the process of a gerrit commit, don't
    want to be redundant with our existing doc though
  


  reply	other threads:[~2018-09-25 17:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-18 19:55 OpenBMC Hackathon @ OpenPower Summit? Sai Dasari
2018-09-18 20:20 ` Andrew Geissler
2018-09-18 21:13   ` Sai Dasari
2018-09-25 14:24     ` Andrew Geissler
2018-09-25 17:16       ` Sai Dasari [this message]
2018-10-04  9:03         ` OpenBMC on OCP Leopard server Jean-Marie Verdun
2018-10-05  0:29           ` 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=937C5B58-38CB-44C0-8F49-63019A5049B3@fb.com \
    --to=sdasari@fb.com \
    --cc=geissonator@gmail.com \
    --cc=jk@ozlabs.org \
    --cc=joel.stan@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=stewart@linux.vnet.ibm.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.