From: Javier Romero <xavinux@gmail.com>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: Yi TZ Li <shliyi@cn.ibm.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: OpenBMC on Raspberry PI 3.
Date: Wed, 11 Oct 2017 16:09:39 -0300 [thread overview]
Message-ID: <CAEX+82KL+N5VCvo+LH20=1paTZvKo2M7PqdXk7=bFq7MdAGeSA@mail.gmail.com> (raw)
In-Reply-To: <1507691159.5452.168.camel@aj.id.au>
> Great! I look forward to you helping us improve our documentation and
> on-boarding of contributors. It might be rocky but it should help those
> coming along in the future.
A starting point to start my contribution, so, how can I help on this?
Javier Romero
E-mail: xavinux@gmail.com
Skype: xavinux
2017-10-11 0:05 GMT-03:00 Andrew Jeffery <andrew@aj.id.au>:
> On Tue, 2017-10-10 at 11:01 -0300, Javier Romero wrote:
>> > Ah - so I don't think you've outlined why you picked OpenBMC for the
>> > job. Can you give us a quick run-down?
>>
>> I'm an individual contributor on the Open Compute Project and follow
>> the Hardware Management Group, OpenBMC is on their project scope and
>> sounds very interesting for me, so decide to participate and see if I
>> can be useful.
>
> Ah, nice. Good to have some background :)
>
>> >
>> > There are going to be easier projects out there than OpenBMC to cut
>> > your teeth with, but if you are keen to learn to program, feel you have
>> > the drive to do so and Yi is happy to help out with your interest in
>> > the Raspberry Pi then by all means stick around :)
>>
>> Have bought the Raspberry PI a few days ago, to start contibuting to
>> the OpenBMC project and try to make it work on the RPI. I can learn
>> what is needed on the way, and that is why I'm here and decide to
>> participate, to contribute while learning new things.
>
> Great! I look forward to you helping us improve our documentation and
> on-boarding of contributors. It might be rocky but it should help those
> coming along in the future.
>
>> But if more
>> programming advanced knowledge is requiered to participate on the
>> OpsnBMC project, maybe I'll have to cut my teeth with other project as
>> you said.
>
> Play it by ear - I just wasn't sure what your motivations were. But
> since you're coming from the OCP background with an interest in
> hardware management, it makes sense to stick around here. As long as
> you get in touch when you get stuck we'll find someone to help answer
> your questions.
>
> Cheers,
>
> Andrew
next prev parent reply other threads:[~2017-10-11 19:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 15:38 OpenBMC on Raspberry PI 3 Javier Romero
2017-10-06 16:59 ` Rick Altherr
2017-10-06 21:28 ` Andrew Jeffery
2017-10-06 23:02 ` Javier Romero
2017-10-08 4:45 ` Javier Romero
2017-10-08 12:44 ` Andrew Jeffery
2017-10-09 2:57 ` Javier Romero
2017-10-09 6:41 ` Andrew Jeffery
2017-10-09 9:39 ` Yi TZ Li
2017-10-09 16:09 ` Javier Romero
2017-10-10 0:14 ` Andrew Jeffery
2017-10-10 14:01 ` Javier Romero
2017-10-11 3:05 ` Andrew Jeffery
2017-10-11 19:09 ` Javier Romero [this message]
2017-10-13 4:56 ` Andrew Jeffery
2017-10-13 14:02 ` Javier Romero
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='CAEX+82KL+N5VCvo+LH20=1paTZvKo2M7PqdXk7=bFq7MdAGeSA@mail.gmail.com' \
--to=xavinux@gmail.com \
--cc=andrew@aj.id.au \
--cc=openbmc@lists.ozlabs.org \
--cc=shliyi@cn.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.