Upstreaming downstream Google BMC repositories

[Benjamin Fair]

Hi Paul,

On Thu, 7 Jan 2021 at 00:09, Paul Menzel <pmenzel at molgen.mpg.de> wrote:
>
> Dear Brandon,
>
>
> Am 07.01.21 um 02:49 schrieb Brandon Kim:
>
> > We're exploring ways of upstreaming some of the downstream repositories
> > from Google to openbmc/* .
> >
> > Half, if not most of the downstream repositories are C++ daemons that are
> > specific to Google so we didn't want to create a bunch of new
> > openbmc/<repo> that no one would use.
> >
> > An idea that Ed gave me was having something like openbmc/google-misc
> > repository for all these repositories and if there are any that seem useful
> > to others, we can break it out into a different, separate repository in
> > openbmc/* layer.
> >
> > Please let me know if this seems like a good idea and I'm open to other
> > suggestions!
>
> Thank you very much for putting in the effort to make these repositories
> public.
>
> Using the openbmc/google-misc approach, how would the git history
> (commit log) be handled?
>
> Personally, I would prefer having small repositories as git makes that
> very easy to handle. Also it might save you time, as you do not have to
> think about what to do with the git history, and do not have to merge it.

We would most likely squash the history together, in case there's
something confidential or private in the earlier commits.

Many small repos would be easy to handle for us, but OpenBMC may not
want to have lots of small Google-specific repos in their org as this
may make it more cumbersome for others to find the relevant repos that
they're interested in. There's also overhead for the project
maintainers to create the relevant groups and permissions for each new
repo.

>
>
> Kind regards,
>
> Paul