From: Thang Nguyen <thang@os.amperecomputing.com>
To: Joel Stanley <joel@jms.id.au>, pvo@amperecomputing.com
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Any convention on putting source codes into openbmc/openbmc repository
Date: Thu, 18 Feb 2021 14:42:52 +0700 [thread overview]
Message-ID: <c0dc2002-0196-b086-4af4-b7f13a847a16@os.amperecomputing.com> (raw)
In-Reply-To: <CACPK8XdFxB4JQR09tNvV-DN4V4fiUmbY2_7+MArh_jdAs1YVkQ@mail.gmail.com>
On 18/02/2021 12:23, Joel Stanley wrote:
> On Thu, 18 Feb 2021 at 01:31, Thang Nguyen <thang@os.amperecomputing.com> wrote:
>>
>> On 18/02/2021 06:46, Nancy Yuen wrote:
>>
>> Code should be put into an appropriate repo, and repos created where necessary. Then referenced in recipes from openbmc/openbmc metalayers.
>>
>> Thanks Nancy for the feedback. Do we have requirement for this or just a recommendation?
> It's a requirement.
>
> OpenBMC uses a project called yocto, which is itself based on
> openembedded (OE). OE is a set of build scripts and configuration
> files for building a filesystem. The filesystem will contain
> applications, such as ipmi daemons, web servers, sensor monitoring
> code, etc. The source code for those applications comes from the
> application's repository. For example, our ssh server (dropbear) comes
> from dropbear's website.
>
> For applications that are developed exclusively for openbmc, we host
> their source code as part of the openbmc organisation on github. But
> the source code lives outside of the main yocto-derived repository,
> and is checked out at build time.
>
> If you have application code that you wish to be part of your system,
> you should first see if it makes sense to contribute that code to an
> existing repository. If it is unique, or deserves it's own repository,
> then you can mail the list to request the creation of a new repository
> for your code.
>
> Apologies if I've covered something you already understood. Once
> you've been around the project for a while it becomes second nature,
> but it was hard to describe the concepts from scratch!
>
> Cheers,
>
> Joel
Thanks Joel for your feedback.
BR/ThangQ.
next prev parent reply other threads:[~2021-02-18 7:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 8:54 Any convention on putting source codes into openbmc/openbmc repository Thang Nguyen
2021-02-17 23:46 ` Nancy Yuen
2021-02-18 1:31 ` Thang Nguyen
2021-02-18 5:23 ` Joel Stanley
2021-02-18 7:42 ` Thang Nguyen [this message]
2021-02-20 17:04 ` Patrick Williams
2021-02-22 8:25 ` Thang Nguyen
2021-02-22 14:26 ` Andrew Geissler
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=c0dc2002-0196-b086-4af4-b7f13a847a16@os.amperecomputing.com \
--to=thang@os.amperecomputing.com \
--cc=joel@jms.id.au \
--cc=openbmc@lists.ozlabs.org \
--cc=pvo@amperecomputing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).