[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openembedded-core
Subject:    Re: [OE-core] [PATCH 05/17] kmscube: update to latest commit
From:       "Alexander Kanavin" <alex.kanavin () gmail ! com>
Date:       2020-04-30 21:01:42
Message-ID: CANNYZj8bEssDO0D56boqmTHt+G=nSf9-ziOarnHoR7zqsg3JzA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Thu, 30 Apr 2020 at 22:46, Andre McCurdy <armccurdy@gmail.com> wrote:

> AUH is a great tool but it does seem to create a division between
> those in the exclusive little club of recipe maintainers and the rest
> of us. If you want to reduce your workload then maybe you could remove
> yourself as maintainer for some of your recipes? If that leaves
> recipes without a maintainer then maybe they should default to
> "community support" with AUH emails being sent to the mailing list
> instead of the named individual?
>

Actually that may not be a bad idea. Listing maintainers explicitly and
sending them private email just doesn't seem to work out: many of the
currently listed ones just silently ignore AUH mails, and don't bother to
unlist themselves, and those who do act are an exception. So those many can
be replaced with the oe-core mailing list email, so the patches (or
information about why smth couldn't be updated) end up here, where
interested parties could pick it up. There'll be a monthly avalanche of
proposed patches. Thoughts?

Alex

[Attachment #5 (text/html)]

<div dir="ltr"><div dir="ltr">On Thu, 30 Apr 2020 at 22:46, Andre McCurdy &lt;<a \
href="mailto:armccurdy@gmail.com">armccurdy@gmail.com</a>&gt; wrote:<br></div><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> AUH is a great tool \
but it does seem to create a division between<br> those in the exclusive little club \
of recipe maintainers and the rest<br> of us. If you want to reduce your workload \
then maybe you could remove<br> yourself as maintainer for some of your recipes? If \
that leaves<br> recipes without a maintainer then maybe they should default to<br>
&quot;community support&quot; with AUH emails being sent to the mailing list<br>
instead of the named individual?<br></blockquote><div><br></div><div>Actually that \
may not be a bad idea. Listing maintainers explicitly and sending them private email \
just doesn&#39;t seem to work out: many of the currently listed ones just silently \
ignore AUH mails, and don&#39;t bother to unlist themselves, and those who do act are \
an exception. So those many can be replaced with the oe-core mailing list email, so \
the patches (or information about why smth couldn&#39;t be updated) end up here, \
where interested parties could pick it up. There&#39;ll be a monthly avalanche of \
proposed patches. Thoughts?<br></div><div><br></div><div>Alex<br></div></div></div>



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#137674): \
https://lists.openembedded.org/g/openembedded-core/message/137674 Mute This Topic: \
https://lists.openembedded.org/mt/73372190/4454766 Group Owner: \
                openembedded-core+owner@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/leave/8023720/1801066118/xyzzy \
                [openembedded-core@marc.info]
-=-=-=-=-=-=-=-=-=-=-=-



[prev in list] [next in list] [prev in thread] [next in thread]