Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: alex.kanavin@gmail.com,
	Yocto-mailing-list <yocto@lists.yoctoproject.org>
Cc: ",openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	 yocto-status@lists.yoctoproject.org
Subject: Re: [OE-core] Yocto Project Status 11 Feb. 2025 (WW07)
Date: Tue, 11 Feb 2025 23:36:31 +0000	[thread overview]
Message-ID: <d22a4cec5e317e62f1f44d8d9a810cf4745ccb48.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj-PbWQDa5hAc5X6sqHVMvJ0QE01XXwytya8rprwvSsqag@mail.gmail.com>

On Tue, 2025-02-11 at 19:42 +0100, Alexander Kanavin via lists.openembedded.org wrote:
> On Tue, 11 Feb 2025 at 16:57, Stephen Jolley via
> lists.openembedded.org
> <sjolley.yp.pm=gmail.com@lists.openembedded.org> wrote:
> > We’d like to request help to process the open github pull requests for openembedded-core and bitbake:
> > 
> > https://github.com/openembedded/openembedded-core/pulls
> > 
> > https://github.com/openembedded/bitbake/pulls
> > 
> > Having these open doesn’t look good for the projects and we can’t disable them, some have been open for a long time. We did already clean up the poky pull requests.
> 
> I'm sorry but I have to say a couple of unpleasant things. Here goes.
> 
> The only processing I would be willing to do is mass-closing these
> pull requests with a polite note to submit them according to the
> official process. Otherwise this tacitly admits github as a valid way
> to contribute, and we're not ready for that, and possible will never
> be.

There are potentially useful bug reports and fixes buried in there and
I am reluctant to turn people away so I'd prefer to not mass close.

> While we're at it, how were these repositories created in the first
> place, and what was the plan for the pull requests they would attract?
> Should we delete these repositories now?

The repositories were added to try and share bandwidth costs, give
people easier mirrors and various other justifications. I warned
strongly about the pull request problems at the time, I was told it
would get handled and people would help and I was over reacting. Some
of the people who made those offers aren't active with the project any
more, other things just drifted with time. At one point I ended up
having to add those mirrors to my own push scripts and maintain them
because nobody else was willing and we had complaints they were not up
to date.

You used to be able to disable pull requests for six month periods, it
looks like you can no longer do that and it was a pain having to try
and remember anyway.

The bandwidth/mirror/backup benefits are valid and I'd be reluctant to
delete them as some people can only discover things through github too.
Google indexing doesn't work well with our own server.

So I guess I made my own peace with their existence. I know touching
them will make it look more like a condoned submission method but I
really don't see many good options here. Removing them is a simple easy
option but life sometimes isn't easy/simple.

Cheers,

Richard


  reply	other threads:[~2025-02-11 23:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-11 15:57 Yocto Project Status 11 Feb. 2025 (WW07) Stephen K Jolley
2025-02-11 18:42 ` [OE-core] " Alexander Kanavin
2025-02-11 23:36   ` Richard Purdie [this message]
2025-02-12  8:08     ` [yocto] " Yoann Congal
2025-02-12  9:38       ` Alexander Kanavin
2025-02-12  9:46         ` Richard Purdie
2025-02-12  9:51       ` Richard Purdie
2025-02-12 11:19         ` Yoann Congal
2025-02-12 23:03           ` Yoann Congal
2025-02-13  8:48             ` Alexander Kanavin
2025-02-13  9:18               ` Yoann Congal
2025-02-13  9:45               ` Richard Purdie
2025-02-13  9:50                 ` Alexander Kanavin
2025-02-13  9:52                   ` Yoann Congal
2025-02-13  9:54                     ` Alexander Kanavin
2025-02-13 10:03                       ` Richard Purdie
2025-02-13 10:09                         ` Alexander Kanavin
2025-02-13 11:16                         ` Yoann Congal
2025-02-13 19:13     ` Justin Bronder
2025-02-13 21:37       ` [OE-core] " Yoann Congal

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=d22a4cec5e317e62f1f44d8d9a810cf4745ccb48.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=yocto-status@lists.yoctoproject.org \
    --cc=yocto@lists.yoctoproject.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