Skip to contentSkip to conversation

sunxi: MAINTAINERS: drop myself

PATCH In review FUKAUMI Naoki 4 participants 6 messages Aug 3, 2023 Arm/Allwinner sunXi SoC support

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 sunxi: MAINTAINERS: drop myself

I no longer maintain them.

---
 board/sunxi/MAINTAINERS | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)
board/sunxi/MAINTAINERS +4 -4
index 98bbd2dd25..d89a25db7c 100644
@@ -82,8 +82,8 @@ S:	Maintained
 F:	configs/A20-Olimex-SOM-EVB_defconfig
 
 A20-OLINUXINO-LIME BOARD
-M:	FUKAUMI Naoki <[email protected]>
-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 <[email protected]>
-S:	Maintained
+M:
+S:
 F:	configs/Nintendo_NES_Classic_Edition_defconfig
 
 OCEANIC 5205 5INMFD BOARD
Signature · 1 line
2.39.2
#2 lore raw

On Thu, 3 Aug 2023 09:13:44 -0400
Tom Rini <[email protected]> wrote:

Hi Tom,

thanks for the heads up, somehow the original email didn't reach me.

Quoted 12 lines · FUKAUMI Naoki
Quoted 4 lines

I no longer maintain them.

Thanks for your time on these platforms.

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

#3 lore raw
Quoted 35 lines · Andre Przywara

On Thu, 3 Aug 2023 09:13:44 -0400
Tom Rini <[email protected]> wrote:

Hi Tom,

thanks for the heads up, somehow the original email didn't reach me.

Quoted 12 lines · FUKAUMI Naoki
Quoted 4 lines

I no longer maintain them.

Thanks for your time on these platforms.

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.

Quoted 4 lines

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.

Signature · 1 line
Tom
#4 lore raw
In reply to Andre Przywara
Quoted 36 lines · Andre Przywara

On Thu, 3 Aug 2023 09:13:44 -0400
Tom Rini <[email protected]> wrote:

Hi Tom,

thanks for the heads up, somehow the original email didn't reach me.

Quoted 12 lines · FUKAUMI Naoki
Quoted 4 lines

I no longer maintain them.

Thanks for your time on these platforms.

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.

Quoted 4 lines

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.

#5 lore raw
Quoted 37 lines · Jagan Teki
Quoted 36 lines · Andre Przywara

On Thu, 3 Aug 2023 09:13:44 -0400
Tom Rini <[email protected]> wrote:

Hi Tom,

thanks for the heads up, somehow the original email didn't reach me.

Quoted 12 lines · FUKAUMI Naoki
Quoted 4 lines

I no longer maintain them.

Thanks for your time on these platforms.

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.

Quoted 8 lines
Quoted 4 lines

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).

Signature · 1 line
Tom