Discussion: nerdctl roadmap?

Hey good folks.

If I have not seen you yet in 2025, wishing you all a happy new year, and all the best to you and your loved ones!

I got involved in nerdctl back in spring last year - very egoistically motivated by the fact some bugs were in my way. And I don't like bugs. Or things in my way.

Eventually, because the people here are so nice and straightforward, I stuck around and started sharing what was on my private fork.
Pretty much everybody I interacted with was awesome, but I would like to specially thank @djdongjin @fahedouch and @AkihiroSuda who suffered the brunt of my contributions and had to review obnoxiously large PRs.

Although my fork has now diverged significantly and is pursuing objectives that are not aligned with nerdctl mission, I still want to share back here and help the project as much as I can.

Most of my contributions in the past year have been focused on getting... well, everything I could for 2.0, without much reasoning, besides: "get shit done!".

Now that we are a few bug-fix-releases past 2.0, and it I truly believe it looks a lot better than 1.7, with the most obvious regressions addressed, I was wondering if we should talk about 3.0 in a more explicit way.
Of course it does not have to be committal, but I guess it would be nice to get a sense of what matters to peeps and the project, what are the most important pain points, what kind of new features we would like, etc.

I am not sure what is the best medium for that, but right now maybe we can start with just this ticket, and I can update the description here with items people are proposing.
Maybe we can post one idea / feature / bug per comment, along with a very simple "priority" (P0: MUST!, P1: should get it done, P2: nice to have), and then peeps can thumb up?

Do you folks have thoughts overall? (I have many, but I would rather keep them for myself for now so that I do not flood the conversation).

Tagging @junnplus @ktock @yankay @austinvazquez @Zheaoli @manugupt1 @haytok @sondavidb @xyz-li @TinaMor @jsturtevant (sorry if I forgot you...).