Any convention on putting source codes into openbmc/openbmc repository

Andrew Geissler geissonator at gmail.com
Tue Feb 23 01:26:45 AEDT 2021



> On Feb 22, 2021, at 2:25 AM, Thang Nguyen <thang at os.amperecomputing.com> wrote:
> 
> 
> On 21/02/2021 00:04, Patrick Williams wrote:
>> On Thu, Feb 18, 2021 at 05:23:56AM +0000, Joel Stanley wrote:
>>> On Thu, 18 Feb 2021 at 01:31, Thang Nguyen <thang at 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.
>>>> 
>>> It's a requirement.
>> My opinion is that there are two reasons that come to my mind on why we
>> follow this convention right now beyond just that Yocto is happier with it:
>> 
>>     1. We like to have a discussion before making a new repository to
>>        make sure we're not fragmenting the codebase more than necessary.
>>        Often problems/solutions overlap more than might seem obvious
>>        when you're looking at it just from your machine or architecture's
>>        perspective.  There may be some existing implementation that
>>        could be modified slightly to make it fit your needs, or it could
>>        be that someone else has the same problem and would like to work
>>        with you on implementation.
> Thanks. It clears for me.
>> 
>>     2. All of our CI infrastructure is set up where machine recipes go
>>        in openbmc/openbmc and code goes in various code repositories.
>>        If you try to put code directly into openbmc/openbmc you do not
>>        gain any of those CI efforts we already have:
>>             * Build of your code and unit tests when someone
>>               makes a code change.
>>             * Unit test execution.
>>             * Code formatting.
>>             * Static code analysis.
>>        We have a lot of support at a repository level that doesn't exist
>>        in openbmc/openbmc directly, because it isn't approriate for what
>>        is there.
> 
> Does the CI setup automatically? if not, how can I set it up?
> 
> It seems I don't have CI setup on the http://github.com/openbmc/ssifbridge repository. How can I have CI for it?

Just need to make a request on mailing list or find me on discord. 
I’ve added it now.

> 
>> 
>> Hopefully this gives you some additional context on why.



More information about the openbmc mailing list