Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: RE: [OE-core] [PATCH 2/2] oe-setup-builddir: Do not hardcode invalid paths for templates
Date: Tue, 27 Sep 2022 19:22:26 +0000	[thread overview]
Message-ID: <6abf4530302c415fab1356d820757237@axis.com> (raw)
In-Reply-To: <CANNYZj-c_z73wttGbAUv7FyKA5oGW6AaohuxMjoV6vEnmPg2wQ@mail.gmail.com>

> -----Original Message-----
> From: Alexander Kanavin <alex.kanavin@gmail.com>
> Sent: den 27 september 2022 19:05
> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> Cc: Richard Purdie <richard.purdie@linuxfoundation.org>; OE-core
> <openembedded-core@lists.openembedded.org>
> Subject: Re: [OE-core] [PATCH 2/2] oe-setup-builddir: Do not hardcode
> invalid paths for templates
> 
> On Tue, 27 Sept 2022 at 18:06, Peter Kjellerstedt
> <peter.kjellerstedt@axis.com> wrote:
> > I (and the small team I am part of) is the proxy between them and Yocto.
> > Thus I try to address their needs by making sure new versions of Yocto
> > continues to work for them without having 500+ developers facing the
> > same problems. I.e., it is my job to work with upstream, which is what
> > I am trying to do here.
> 
> Excuse me, but your job is not to 'work with upstream'. Your job is to
> make damn sure 'upstream' continues to exist. Which means: go to your
> management, describe the situation we're in (you have the numbers),

Which is exactly why I have worked on and finally convinced my 
management that it is important for us to become a Yocto member, 
which we now are.

> and ask that they allocate at least one developer to work in upstream
> full time. 

That is harder. We have a hard enough time to recruit people to 
our tools team (which includes the build team that I am part of) 
as it is. For some reason, working with tools and build systems 
apparently is not as sexy as working with web development and AI.

> Not drive-by patches to fix your specific product problems,

I'm sorry to hear that you think all I do is drive-by patches. 
I thought my contributions were a little bit more appreciated 
than that. :(

> but upstream proper: something that makes the project sustainable,
> e.g. fixing medium+/high bugs, working on new features, upgrading
> recipes, sending pending patches upstream. This works never ends, and
> no one wants to do it.

And I can assure you that everyone appreciate the ungrateful 
work you and others do to keep things running. We really do.
 
> If you can do this, I promise to be more sympathetic to your
> particular issues, but as things stand, it's rather difficult.
> 
> Alex

//Peter


  reply	other threads:[~2022-09-27 19:22 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 12:47 [PATCH 1/2] .templateconf: Mark "meta/conf" as an invalid path for templates Peter Kjellerstedt
2022-09-22 12:47 ` [PATCH 2/2] oe-setup-builddir: Do not hardcode invalid paths " Peter Kjellerstedt
2022-09-22 13:14   ` [OE-core] " Richard Purdie
2022-09-22 13:25     ` Peter Kjellerstedt
2022-09-22 15:52       ` Alexander Kanavin
2022-09-22 19:56         ` Peter Kjellerstedt
2022-09-22 20:32         ` Richard Purdie
2022-09-22 21:53           ` Alexander Kanavin
     [not found]           ` <17174D5BCC8D1164.8129@lists.openembedded.org>
2022-09-26 17:09             ` Alexander Kanavin
2022-09-27 14:56           ` Peter Kjellerstedt
2022-09-27 15:29             ` Alexander Kanavin
     [not found]             ` <1718C14CEB633922.9698@lists.openembedded.org>
2022-09-27 15:42               ` Alexander Kanavin
2022-09-27 16:06                 ` Peter Kjellerstedt
2022-09-27 16:16                   ` Alexander Kanavin
2022-09-27 18:53                     ` Peter Kjellerstedt
2022-09-27 19:58                       ` Alexander Kanavin
2022-09-27 21:31                         ` Peter Kjellerstedt
2022-09-27 21:50                           ` Alexander Kanavin
2022-09-28  9:54                             ` Peter Kjellerstedt
2022-09-28 10:59                               ` Alexander Kanavin
2022-09-28 12:45                                 ` Peter Kjellerstedt
2022-09-28 13:24                                   ` Alexander Kanavin
     [not found]                               ` <17190128C53AF22E.9603@lists.openembedded.org>
2022-09-28 11:05                                 ` Alexander Kanavin
2022-09-27 17:04                   ` Alexander Kanavin
2022-09-27 19:22                     ` Peter Kjellerstedt [this message]
2022-09-27 20:39                       ` 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=6abf4530302c415fab1356d820757237@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox