All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Mihm <james.mihm@gmail.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Fwd: Which repo is more stable, feature complete, most functionality? https://github.com/openbmc/openbmc or https://github.com/Intel-BMC/openbmc
Date: Tue, 24 Mar 2020 11:11:52 -0700	[thread overview]
Message-ID: <CADy_Pt2mZ8E4EgY0y3wRSLh080cBBmoERgJvR7Lk8Rj4ep39-w@mail.gmail.com> (raw)
In-Reply-To: <CADy_Pt3xOgPXungY+nwpYjFVcvCqMek_gHLeFWXOUoSjLom3RQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2278 bytes --]

I meant to include the mailing list on my response.

James.

---------- Forwarded message ---------
From: James Mihm <james.mihm@gmail.com>
Date: Mon, Mar 9, 2020 at 7:11 PM
Subject: Re: Which repo is more stable, feature complete, most
functionality? https://github.com/openbmc/openbmc or
https://github.com/Intel-BMC/openbmc
To: Bruce Mitchell <Bruce_Mitchell@phoenix.com>


Bruce,

The Intel-BMC/openbmc repo is where we (i.e., Intel) pushes our
internal fork externally while in the process of upstreaming. The intent
for this repo is for it to be functional on an Intel development platform
(e.g., Wolfpass) at all times while upstreaming changes to the
openbmc/openbmc repo. The long term goal is for Intel to be pushing all
development upstream to the openbmc/openbmc repo, and using the Intel-BMC
repository for sharing future capabilities that are not yet publically
announced. Where our goal is to push our internal development fork to the
Intel-BMC/openbmc repo every two weeks.

Two exceptions for upstreaming are the webui and linux kernel patches.
Upstreaming the linux kernel patches is challenging and some of the patches
may never make it upstream. With the migration of the webui to vue.js
there's not much point in upstreaming the Intel fork of phosphor-webui.

My answer to your question is to use the openbmc/openbmc repository, but
not for controlling your car brakes.

James.



On Thu, Jan 16, 2020 at 4:27 PM Bruce Mitchell <Bruce_Mitchell@phoenix.com>
wrote:

> Which repo is more stable, feature complete, most functionality?
> https://github.com/openbmc/openbmc or https://github.com/Intel-BMC/openbmc
>
> While the WebUI for https://github.com/Intel-BMC/openbmc may look better,
> presently its functionality for BMC operation seems intermittent compared
> to the functionality of https://github.com/openbmc/openbmc.
> I am referring to basic things such as displaying the BMC's Firmware
> Version, the lack of displaying any NIC for Network Settings, the "hang"
> for Health Hardware Status.
>
> This is not a request about ahead or behind; I am asking about stable,
> feature complete, most functionality.
>
> Using a metaphor here; if you had to select today one of the 2 for
> controlling your car's breaks which would it be?
>
> Thank you.
>
>

[-- Attachment #2: Type: text/html, Size: 3532 bytes --]

  parent reply	other threads:[~2020-03-24 18:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17  0:26 Which repo is more stable, feature complete, most functionality? https://github.com/openbmc/openbmc or https://github.com/Intel-BMC/openbmc Bruce Mitchell
     [not found] ` <CADy_Pt3xOgPXungY+nwpYjFVcvCqMek_gHLeFWXOUoSjLom3RQ@mail.gmail.com>
2020-03-24 18:11   ` James Mihm [this message]
2020-03-25  8:19     ` Fwd: " Alexander Amelkin
2020-03-25 10:32       ` Alexander A. Filippov
2020-03-25 17:18         ` Bills, Jason M

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=CADy_Pt2mZ8E4EgY0y3wRSLh080cBBmoERgJvR7Lk8Rj4ep39-w@mail.gmail.com \
    --to=james.mihm@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    /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.