Call for maintainer(s)

Hi all, it’s been four years now since I released next-i18next@0.1.0, and I feel truly privileged to have contributed to the NextJs ecosystem, and hopefully helped save some other devs’ precious time.

Due to other projects and a sheer lack of time, I’ll now pass the torch. Hopefully we can find a committed and competent maintainer to continue active development, otherwise I will put the project into archival.

Alternatively, there are several other NextJs i18n packages which are popular these days, so another option would be to simply merge projects, or create an easy migration path for users. I do hope that eventually, NextJs as a framework will support i18n first-class.

Pinging some relevant names, but feedback from anyone is appreciated!

@adrai @kachkaev @aralroca @amannn

[jamuhl]

Just discussed this with @adrai - if people agree we would suggest moving next-i18next to the i18next organization and start maintaining it like we do for react-i18next.

We (i18next and locize team) could help with issues, support and documentation - any help from devs using this module would be helpful and could be compensated through sponsoring coming through our locize.com).

This way we could assert this module stays well maintained in the years coming.

[adrai]

Thank you Isaac for all your work and all your patience. It saddens me to hear you made that choice, but that’s just the nature of things.

Since I’m one of the i18next maintainer, I would be very happy if someone would agree to continue with next-i18next. I am still available for support on topics related to i18next. Additionally, if necessary I may also offer a small sponsorship (GitHub sponsors or similar).

btw: If there’s no new maintainer, I’m ready to take over on a PR based approach. I would move it to the i18next organization, similar to react-i18next.

Wishing you all the best Isaac.