Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
	Yoann Congal <yoann.congal@smile.fr>
Cc: Yocto Mailing list <yocto@lists.yoctoproject.org>,
	 ",openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [yocto] [OE-core] Yocto Project Status 11 Feb. 2025 (WW07)
Date: Thu, 13 Feb 2025 09:45:21 +0000	[thread overview]
Message-ID: <2c1bcbb1d5b75b925d9af2bd300d376a973e314e.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj_8o=SHOn-kRBxzwc8vp3omCL290SA-jKkL_En1m2SWEA@mail.gmail.com>

On Thu, 2025-02-13 at 09:48 +0100, Alexander Kanavin wrote:
> On Thu, 13 Feb 2025 at 00:04, Yoann Congal <yoann.congal@smile.fr>
> wrote:
> 
> > I did not find a magic silver bullet that would solve everything (I
> > discovered that Gitlab is way more flexible on this subject).
> > I guess we need to find a compromise between what a github user
> > sees and the effort we are willing to put into it.
> 
> So as I understand, there are no 'settings' in github openembedded
> organization we can tweak and everything is through repos?

As I understand it.

> Then here's the plan:
> - someone with rights to manage overall
> https://github.com/openembedded org creates an empty .github repo and
> gives Yoann rights to manage it.
> - Yoann opens pull requests to that repo, and notifies of them here
> - any needed github specific tweaks to individual repos are proposed
> and merged through the standard mailing list process.

I don't think the github repo is going to work for either YP or OE
since there are repositories in both that use pull requests and we
can't have a one size fits all message. I think that means we would
have to do this with a .github directory in the repos themselves.

Also note, the global repos probably need TSC agreement. On a per repo
basis it would fall to the maintainer.

Yoann: Thanks for looking into this!

Cheers,

Richard



  parent reply	other threads:[~2025-02-13  9:45 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
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 [this message]
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=2c1bcbb1d5b75b925d9af2bd300d376a973e314e.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=yoann.congal@smile.fr \
    --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