From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: "Richard Purdie" <richard.purdie@linuxfoundation.org>,
"Enrico Jörns" <ejo@pengutronix.de>,
"Marco Felsch" <m.felsch@pengutronix.de>,
openembedded-core@lists.openembedded.org, yocto@pengutronix.de,
barebox@lists.infradead.org
Subject: Re: [yocto] [OE-core] [PATCH 1/2] barebox: add initial support
Date: Wed, 15 Feb 2023 11:59:11 -0300 [thread overview]
Message-ID: <CAP9ODKpNDSBSwwAwfBCFx6gJQqNEb8bPpbiQwAbFwGkn+6WfUQ@mail.gmail.com> (raw)
In-Reply-To: <CANNYZj_jLK-FXrGx+bF6fXrSsc-so6G_kpyZKNTpatqJKxQeRg@mail.gmail.com>
Em qua., 15 de fev. de 2023 às 11:11, Alexander Kanavin
<alex.kanavin@gmail.com> escreveu:
>
> On Wed, 15 Feb 2023 at 14:53, Otavio Salvador
> <otavio.salvador@ossystems.com.br> wrote:
> > I think the Barebox inside OE-Core allows a bigger integration and
> > reuse of existing tooling for signing and other classes currently well
> > integrated with U-Boot. For me, a critical point for decision is if
> > Pengutronix will commit to support it.
>
> You should be well aware there's a history of people contributing
> stuff to core and even assigning themselves as maintainers, then
> disappearing. And then it falls (largely) on me to keep things
> (barely) going. What happens if ptx withdraws its commitment? Can I
> then send a commit that removes barebox from core? Imagine the angry
> lynch mob that will show up after my head.
Yes. If no one maintains, it should be removed. People will get mad
but then we'll see more commitment in future.
> Adding things to core is a decision that cannot be easily reversed, so
> I'd rather have barebox in meta-barebox for a while, with any needed
> fixing to classes and infra in core.
Sure but adding things to the core should still be possible and it is
a place to foster work sharing and contribution.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750
next prev parent reply other threads:[~2023-02-15 15:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230203135011.2061939-1-m.felsch@pengutronix.de>
[not found] ` <12e370a3183d04572da1c5749d8e64dcf5091a0c.camel@linuxfoundation.org>
2023-02-14 9:46 ` Enrico Jörns
2023-02-14 13:56 ` Richard Purdie
[not found] ` <CAP9ODKokQpGL3ttukqRaq3-8m0ci7qp8mckbgudGJx1HOu-fPw@mail.gmail.com>
2023-02-15 13:43 ` Alexander Kanavin
2023-02-15 13:49 ` Enrico Jörns
2023-02-15 13:53 ` Otavio Salvador
2023-02-15 14:06 ` Enrico Jörns
2023-02-15 14:11 ` Alexander Kanavin
2023-02-15 14:59 ` Otavio Salvador [this message]
2023-02-15 15:01 ` Enrico Jörns
2023-02-15 15:12 ` Alexander Kanavin
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=CAP9ODKpNDSBSwwAwfBCFx6gJQqNEb8bPpbiQwAbFwGkn+6WfUQ@mail.gmail.com \
--to=otavio.salvador@ossystems.com.br \
--cc=alex.kanavin@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=ejo@pengutronix.de \
--cc=m.felsch@pengutronix.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=yocto@pengutronix.de \
/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