New mailing list for layer patches

New mailing list for layer patches

[Ross Burton]

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.

Many thanks,
Ross
Yocto TSC member

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

[Paul Barker]

[-- Attachment #1.1.1: Type: text/plain, Size: 1508 bytes --]

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?

Thanks,

-- 
Paul Barker

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3577 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

RE: New mailing list for layer patches

[Peter Kjellerstedt]

> -----Original Message-----
> From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On
> Behalf Of Ross Burton
> Sent: den 28 mars 2024 15:37
> To: openembedded-architecture <openembedded-
> architecture@lists.openembedded.org>; Yocto-mailing-list
> <yocto@lists.yoctoproject.org>; OE-core <openembedded-
> core@lists.openembedded.org>
> Subject: [yocto] New mailing list for layer patches
> 
> 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.
> 
> Many thanks,
> Ross
> Yocto TSC member

To whoever is responsible for updating 
https://www.yoctoproject.org/community/mailing-lists/: the links for the 
two new lists both refer to yocto-announce rather than yocto-status and 
yocto-patches.

//Peter

Re: [yocto] New mailing list for layer patches

[Neal Caidin]

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

Hi Peter,

Fixed by the YPE team (Yocto Project Elves).

Thanks for noticing and reporting!

Best,
Neal

*Neal Caidin*
Program Manager
The Linux Foundation
Durham, NC, U.S.A. - Eastern time zone
+1 (919) 238-9104 (w/h)
+1 (919) 949-1861 (m)
ncaidin@linuxfoundation.org
https://meetings.hubspot.com/ncaidin




On Tue, Apr 2, 2024 at 6:33 PM Peter Kjellerstedt <
peter.kjellerstedt@axis.com> wrote:

> > -----Original Message-----
> > From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On
> > Behalf Of Ross Burton
> > Sent: den 28 mars 2024 15:37
> > To: openembedded-architecture <openembedded-
> > architecture@lists.openembedded.org>; Yocto-mailing-list
> > <yocto@lists.yoctoproject.org>; OE-core <openembedded-
> > core@lists.openembedded.org>
> > Subject: [yocto] New mailing list for layer patches
> >
> > 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.
> >
> > Many thanks,
> > Ross
> > Yocto TSC member
>
> To whoever is responsible for updating
> https://www.yoctoproject.org/community/mailing-lists/: the links for the
> two new lists both refer to yocto-announce rather than yocto-status and
> yocto-patches.
>
> //Peter
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#62880):
> https://lists.yoctoproject.org/g/yocto/message/62880
> Mute This Topic: https://lists.yoctoproject.org/mt/105197684/4445066
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [
> ncaidin@linuxfoundation.org]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

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

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

[Richard Purdie]

On Tue, 2024-04-02 at 22:33 +0000, Peter Kjellerstedt wrote:
> 
> To whoever is responsible for updating 
> https://www.yoctoproject.org/community/mailing-lists/: the links for
> the two new lists both refer to yocto-announce rather than yocto-
> status and yocto-patches.

That should be fixed now, thanks.

Cheers,

Richard

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

[Michael Opdenacker]

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

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

[Josef Holzmayr]

[-- 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 --]