Request for a development repo

[Patrick Venture]

On Thu, Dec 21, 2017 at 11:16 AM, Tanous, Ed <ed.tanous at intel.com> wrote:
> In the hope of being more open with our development process, we’d like to
> create a repo for hosting work-in-progress applications, and applications
> that don’t really fit into the other repositories.  Internally, we have such
> a repository, informally named proving ground, where we try to build out
> concepts to test new applications, modes, and put the things that are
> specific to our platform that don’t really fit anywhere else.  An example of
> a component that would be contained in here would be this:
> https://gerrit.openbmc-project.xyz/#/c/8197/
>
>
>
> With the goal of being more open, we’d like to find a way to make these
> prototypes available to the community sooner, and have our machine targets
> build some of the components while still in development.  The options we’ve
> considered thusfar are:
>
>
>
> 1.       Acquire a repository under github/openbmc, possibly called intel,
> possibly called something more company agnostic.  Here we would put our
> prototypes, and things that we would like to enable on our platforms.

I vote for this option with a more generic name.  It would be handy
since a lot of new daemons or work has nowhere to really be staged.

>
> 2.       Start our own repository on 01.org (Intels open source repository)
> and simply make our platform recipes in openbmc point to it.
>
> 3.       Create repositories for each component under openbmc, and define a
> faster SLA and process for requesting new repos.
>
> 4.       Continue with our internal fork, and publish prototypes to
> repositories once they fit some definition of “done”.
>
>
>
> My personal preference would be #1, but I’m curious if anyone has any
> thoughts on other opinions on how this should be done, or have better
> options that we haven’t thought of yet.
>
>
>
> Thanks,
>
>
>
> -Ed