Re: [yocto] [Openembedded-architecture] New mailing list for layer patches

From: Josef Holzmayr <jester@theyoctojester.info>
To: yocto@lists.yoctoproject.org, michael.opdenacker@bootlin.com
Cc: pbarker.renesas@gmail.com,
	 openembedded-architecture
	<openembedded-architecture@lists.openembedded.org>,
	 OE-core <openembedded-core@lists.openembedded.org>,
	 Ross Burton <ross.burton@arm.com>
Subject: Re: [yocto] [Openembedded-architecture] New mailing list for layer patches
Date: Wed, 3 Apr 2024 17:02:13 +0200	[thread overview]
Message-ID: <CAEt6NwrTGcfjYudKCNnMD=kB4mEqQFd2D0kr1Z3vPJK0KWT0pw@mail.gmail.com> (raw)
In-Reply-To: <997ee82c-be16-4562-b196-1aae40bb9284@bootlin.com>

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

Thanks for that initiative Michael and Paul, this is very helpful for the
greater community!

Greets,
Josef

On Wed, Apr 3, 2024 at 4:59 PM Michael Opdenacker via lists.yoctoproject.org
<michael.opdenacker=bootlin.com@lists.yoctoproject.org> wrote:

> Hi Paul,
>
> On 4/2/24 at 10:38, Paul Barker wrote:
> > On 28/03/2024 14:36, Ross Burton wrote:
> >> Hi,
> >>
> >> At the moment if a layer doesn’t have enough volume to justify a
> dedicated mailing list for patches (see, for example,
> meta-arm@lists.yoctoproject.org <mailto:meta-arm@lists.yoctoproject.org>)
> then the convention is that the patches can be sent to
> yocto@lists.yoctoproject.org <mailto:yocto@lists.yoctoproject.org>.
> >>
> >> However, that’s also the list that we encourage users of Yocto to use
> for help, so the list has a mix of patches for various layers and people
> asking for help, which isn’t ideal: users who want help don’t want to be
> flooded with patches for layers they’re not using, layer maintainers may
> not want to see the requests for help, and people who want the status
> reports have to receive patches and support.
> >>
> >> The Yocto TSC has been discussing this, and as a solution to this we’ve
> just created a new mailing list: yocto-patches@lists.yoctoproject.org
> <mailto:yocto-patches@lists.yoctoproject.org>.  This list is specifically
> for Yocto-related projects which don’t have their own mailing list or other
> patch submission process.   We ask that all layers currently using yocto@
> for patches move to yocto-patches@, so that yocto@ can be used purely for
> discussion and other non-patch related subjects.
> > I think this is a great change, along with the new yocto-status@ list
> it will make things easier to follow :)
> >
> > Do you know if yocto-patches@ will be available via lore.kernel.org?
>
> I've just asked them to index the new lists as well as these important
> ones which are missing too:
> https://lists.yoctoproject.org/g/yocto-announce
> http://lists.openembedded.org/mailman/listinfo/openembedded-architecture
> https://lists.yoctoproject.org/g/automated-testing
> https://lists.yoctoproject.org/g/yocto-security
>
> Cheers
> Michael.
>
> --
> Michael Opdenacker, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> You automatically follow any topics you start or reply to.
> View/Reply Online (#62883):
> https://lists.yoctoproject.org/g/yocto/message/62883
> Mute This Topic: https://lists.yoctoproject.org/mt/105284127/4689568
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [
> jester@theyoctojester.info]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

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