From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: OpenBMC <openbmc@lists.ozlabs.org>
Subject: OpenBMC community telecon - New time!
Date: Thu, 26 Oct 2017 09:29:10 -0400 [thread overview]
Message-ID: <E6451267-D783-4A1B-A129-419CE483F553@fuzziesquirrel.com> (raw)
In-Reply-To: 242042C5-601B-45C0-B6CA-D9EEB173A753@fuzziesquirrel.com
Hi everyone.
This telecon will be moving to a new time starting this Monday 10/30.
The new time is 10:00PM EDT.
thx - brad
> Begin forwarded message:
>
> From: Brad Bishop <bradleyb@fuzziesquirrel.com>
> Subject: OpenBMC community telecon
> Date: October 23, 2017 at 9:55:17 AM EDT
> To: OpenBMC <openbmc@lists.ozlabs.org>
>
> For the last year or so a small group of technical folks have been
> meeting Monday evenings at 8:30 EDT to discuss the ins and outs of
> working with the code at github.com/openbmc.
>
> Given the announcement made by Chris Austen here:
> https://lists.ozlabs.org/pipermail/openbmc/2017-September/009289.html
>
> the time seems right to open this meeting up to the entire
> community. The meeting information is:
> Mondays, 8:30 EDT
> 888-426-6840
> password: 85891389
>
> Please feel free to join if you have a technical topic or just want to
> listen in. I will send out a weekly request for topics - please reply
> if you have one so I can set an agenda. Some example topics might be
> based around:
>
> - progress of contributions to the repo
> - technical questions on future contributions
> - (brief) code review discussion; additional to anything on the
> mailing list
>
> Going forward I'd like to make our primary medium for discussion of
> topics be the mailing list. So please consider using that rather than
> waiting until the meeting.
>
> The OpenBMC community is hard at work establishing a formal project
> governance model. Once that model is established this meeting will be
> superseded by whatever process is selected for technical
> steering. Additionally, topics raised with any significant impact to
> the future direction of the project will likely be tabled until that
> model is established.
>
> Thx - brad bishop
next prev parent reply other threads:[~2017-10-26 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF59B01BF4.8741B426-ON002581C5.004A38A3@LocalDomain>
2017-10-23 13:55 ` OpenBMC community telecon Brad Bishop
2017-10-23 14:36 ` Brad Bishop
2017-10-26 13:29 ` Brad Bishop [this message]
2017-10-26 14:21 ` OpenBMC community telecon - New time! Sivas Srr
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=E6451267-D783-4A1B-A129-419CE483F553@fuzziesquirrel.com \
--to=bradleyb@fuzziesquirrel.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.