From: Nancy Yuen <yuenn@google.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: OpenBMC Fix-It
Date: Tue, 8 May 2018 12:28:45 -0700 [thread overview]
Message-ID: <CADfYTpFfoEe2SvvBAsjL-UAPocC02Z49o-rTDxA7JwA9OagHnw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
Please join my team for an OpenBMC community "fix-it" event in June!
My team is devoting the week of 6/11/-15 to a Google OpenBMC "fix it" as
part of a larger fix-it initiative. OpenBMC is a large part of our project
so I'd like to spend part of the week on a fix-it on OpenBMC.
I propose to have the fix it on Tues and Wed 6/12 & 6/13. We could set up
an IRC channel for the fix it where everyone participating would hang out
for the day. We could pick one or two areas to focus on for those days,
put together a list of things to "fix" in those areas ahead of time. On
the day, we all tackle things on the list (or something not on the list),
discuss over IRC and do code reviews. Inevitably, people have meetings or
things they can't get out of, but if you can be available for most of the
day, that would be enough!
Anyone interested in participating?
----------
Nancy
[-- Attachment #2: Type: text/html, Size: 1373 bytes --]
next reply other threads:[~2018-05-08 19:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 19:28 Nancy Yuen [this message]
2018-05-10 12:43 ` OpenBMC Fix-It Joel Stanley
2018-05-18 19:13 ` Nancy Yuen
2018-05-21 2:59 ` Lei YU
2018-05-21 14:26 ` krtaylor
2018-05-10 13:59 ` krtaylor
2018-05-18 19:15 ` Nancy Yuen
2018-05-22 2:19 ` Andrew Jeffery
2018-05-31 16:10 ` Devender Rao
2018-05-31 16:57 ` Nagaraju Goruganti
2018-06-07 16:22 Jayashankar Padath
2018-06-07 17:54 ` Nancy Yuen
2018-06-07 18:17 ` Jayashankar Padath
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=CADfYTpFfoEe2SvvBAsjL-UAPocC02Z49o-rTDxA7JwA9OagHnw@mail.gmail.com \
--to=yuenn@google.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 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.