[PATCH] sunxi: MAINTAINERS: drop myself
I no longer maintain them.
Signed-off-by: FUKAUMI Naoki naobsd@gmail.com --- board/sunxi/MAINTAINERS | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/board/sunxi/MAINTAINERS b/board/sunxi/MAINTAINERS index 98bbd2dd25..d89a25db7c 100644 --- a/board/sunxi/MAINTAINERS +++ b/board/sunxi/MAINTAINERS @@ -82,8 +82,8 @@ S: Maintained F: configs/A20-Olimex-SOM-EVB_defconfig
A20-OLINUXINO-LIME BOARD -M: FUKAUMI Naoki naobsd@gmail.com -S: Maintained +M: +S: F: configs/A20-OLinuXino-Lime_defconfig
A20-OLINUXINO-LIME2 BOARD @@ -379,8 +379,8 @@ S: Maintained F: configs/nanopi_a64_defconfig
NINTENDO NES CLASSIC EDITION BOARD -M: FUKAUMI Naoki naobsd@gmail.com -S: Maintained +M: +S: F: configs/Nintendo_NES_Classic_Edition_defconfig
OCEANIC 5205 5INMFD BOARD
On Thu, Aug 03, 2023 at 04:50:34PM +0900, FUKAUMI Naoki wrote:
I no longer maintain them.
Signed-off-by: FUKAUMI Naoki naobsd@gmail.com
Thanks for your time on these platforms.
Reviewed-by: Tom Rini trini@konsulko.com
Andre, Jagan, which one of you wants to pick these up? I assume you don't want to drop the defconfigs themselves.
On Thu, 3 Aug 2023 09:13:44 -0400 Tom Rini trini@konsulko.com wrote:
Hi Tom,
thanks for the heads up, somehow the original email didn't reach me.
On Thu, Aug 03, 2023 at 04:50:34PM +0900, FUKAUMI Naoki wrote:
I no longer maintain them.
Signed-off-by: FUKAUMI Naoki naobsd@gmail.com
Thanks for your time on these platforms.
Reviewed-by: Tom Rini trini@konsulko.com
Andre, Jagan, which one of you wants to pick these up? I assume you don't want to drop the defconfigs themselves.
To be honest, I am more inclined to delete that whole file. Given its age and the (natural and understandable) volatility of engagement for those boards I don't think there is much actual information in there anymore than "person originally submitted the *_defconfig" (which we have in the git log). For instance I think that Hans retreated from day-to-day sunxi engagement years ago, and I wonder if he even still possesses all of these boards listed under his name - which was more of a catch-all anyway, IIUC.
So it's either that (which is certainly easier), or I write to everyone on the list and ask for an update on the support situation. Because I also feel that only a small fraction of these boards receives some testing, so wouldn't be surprised to find many of them broken for a while - given the refactoring we did lately.
But please note that I don't intend to drop any of the defconfigs unnecessarily, so just because we *believe* they are unsupported.
Any opinions?
Cheers, Andre
On Thu, Aug 03, 2023 at 02:35:54PM +0100, Andre Przywara wrote:
On Thu, 3 Aug 2023 09:13:44 -0400 Tom Rini trini@konsulko.com wrote:
Hi Tom,
thanks for the heads up, somehow the original email didn't reach me.
On Thu, Aug 03, 2023 at 04:50:34PM +0900, FUKAUMI Naoki wrote:
I no longer maintain them.
Signed-off-by: FUKAUMI Naoki naobsd@gmail.com
Thanks for your time on these platforms.
Reviewed-by: Tom Rini trini@konsulko.com
Andre, Jagan, which one of you wants to pick these up? I assume you don't want to drop the defconfigs themselves.
To be honest, I am more inclined to delete that whole file. Given its age and the (natural and understandable) volatility of engagement for those boards I don't think there is much actual information in there anymore than "person originally submitted the *_defconfig" (which we have in the git log). For instance I think that Hans retreated from day-to-day sunxi engagement years ago, and I wonder if he even still possesses all of these boards listed under his name - which was more of a catch-all anyway, IIUC.
So it's either that (which is certainly easier), or I write to everyone on the list and ask for an update on the support situation. Because I also feel that only a small fraction of these boards receives some testing, so wouldn't be surprised to find many of them broken for a while - given the refactoring we did lately.
But please note that I don't intend to drop any of the defconfigs unnecessarily, so just because we *believe* they are unsupported.
Any opinions?
Reaching out to everyone listed and checking in with them is probably a good first step. Since these boards are just a defconfig, it's not too hard to resurrect them if later on someone has one and wants to maintain it.
On Thu, Aug 3, 2023 at 7:05 PM Andre Przywara andre.przywara@arm.com wrote:
On Thu, 3 Aug 2023 09:13:44 -0400 Tom Rini trini@konsulko.com wrote:
Hi Tom,
thanks for the heads up, somehow the original email didn't reach me.
On Thu, Aug 03, 2023 at 04:50:34PM +0900, FUKAUMI Naoki wrote:
I no longer maintain them.
Signed-off-by: FUKAUMI Naoki naobsd@gmail.com
Thanks for your time on these platforms.
Reviewed-by: Tom Rini trini@konsulko.com
Andre, Jagan, which one of you wants to pick these up? I assume you don't want to drop the defconfigs themselves.
To be honest, I am more inclined to delete that whole file. Given its age and the (natural and understandable) volatility of engagement for those boards I don't think there is much actual information in there anymore than "person originally submitted the *_defconfig" (which we have in the git log). For instance I think that Hans retreated from day-to-day sunxi engagement years ago, and I wonder if he even still possesses all of these boards listed under his name - which was more of a catch-all anyway, IIUC.
So it's either that (which is certainly easier), or I write to everyone on the list and ask for an update on the support situation. Because I also feel that only a small fraction of these boards receives some testing, so wouldn't be surprised to find many of them broken for a while - given the refactoring we did lately.
But please note that I don't intend to drop any of the defconfigs unnecessarily, so just because we *believe* they are unsupported.
Any opinions?
What if we categorize the defconfigs into active and inactive based on the maintainer's activites and give them some release threshold to drop or mark it (re)active like we did it for DM conversion?
Thanks, Jagan.
On Thu, Aug 03, 2023 at 07:16:35PM +0530, Jagan Teki wrote:
On Thu, Aug 3, 2023 at 7:05 PM Andre Przywara andre.przywara@arm.com wrote:
On Thu, 3 Aug 2023 09:13:44 -0400 Tom Rini trini@konsulko.com wrote:
Hi Tom,
thanks for the heads up, somehow the original email didn't reach me.
On Thu, Aug 03, 2023 at 04:50:34PM +0900, FUKAUMI Naoki wrote:
I no longer maintain them.
Signed-off-by: FUKAUMI Naoki naobsd@gmail.com
Thanks for your time on these platforms.
Reviewed-by: Tom Rini trini@konsulko.com
Andre, Jagan, which one of you wants to pick these up? I assume you don't want to drop the defconfigs themselves.
To be honest, I am more inclined to delete that whole file. Given its age and the (natural and understandable) volatility of engagement for those boards I don't think there is much actual information in there anymore than "person originally submitted the *_defconfig" (which we have in the git log). For instance I think that Hans retreated from day-to-day sunxi engagement years ago, and I wonder if he even still possesses all of these boards listed under his name - which was more of a catch-all anyway, IIUC.
So it's either that (which is certainly easier), or I write to everyone on the list and ask for an update on the support situation. Because I also feel that only a small fraction of these boards receives some testing, so wouldn't be surprised to find many of them broken for a while - given the refactoring we did lately.
But please note that I don't intend to drop any of the defconfigs unnecessarily, so just because we *believe* they are unsupported.
Any opinions?
What if we categorize the defconfigs into active and inactive based on the maintainer's activites and give them some release threshold to drop or mark it (re)active like we did it for DM conversion?
Orphaned / unmaintained defconfigs are a CI failure normally, they just aren't right this moment because that got broken a while back (and so I'm trying to fix that now, and prevent new breakage from coming in).
participants (4)
-
Andre Przywara -
FUKAUMI Naoki -
Jagan Teki -
Tom Rini