Looking for new maintainers

[orhun]

ratatui needs more love thus more people to take care of it. For now, me, @sayanarijit and @mindoodoo are responsible for reviewing the pull requests, organizing meetings and creating releases. However, as you might have guessed, we are not always enough for a project at this scale. So we need more developers to take care of the following tasks:

• Reviewing pull requests for quality code.
• Maintaining the codebase.
• Creating issues & release milestones.
• Providing comments & help.

If you are interested in maintaining ratatui, feel free to comment below and we're happy to consider things! 🐭

P.S. For this role, it would be nice to be present on Discord, but it is not strictly needed.

[orhun]

I would like to propose @sophacles and @joshka for the maintainer role since they are actively contributing and providing code review for the pull requests.

Let us know if you would like to volunteer!

[lthoerner]

I'm not sure whether I have the skills to do it but I would be interested in getting involved if you guys need me.

[joshka]

I'm happy to help out with PRs etc., but probably not too much on discord.

[mindoodoo]

Yeah to be fair help with PRs is the main thing we need so... awesome ! Are you on the discord server ? (Just so we get in touch with you)

edit: Way too many typos lmao

[orhun]

Awesome, what is your preferred way of communication? We can work something out.

[joshka]

I have discord and joined the Ratatui server. Happy to use it sporadically, but I'm just well aware of what a time suck (for my brain) idling on slack/discord/etc. can be. If there was maybe 1 or two channels, perhaps it would be ok, but there's 20 or so, which I found a bit overwhelming.

I'd much prefer to see support type issues end up being public where possible (discussions / issues / PRs instead of discord messages) as it means that future users benefit from the answers etc whereas discord generally has a discoverability problem.

[Nickiel12]

It is certainly better for documentation/future bugs to have them on GitHub where anyone can see them, but the response time in conversations is a lot longer on GitHub. It might be worth looking into tools that will create issues and automatically log discord messages to GitHub issues? Discord thread=issue? Maybe?

But, right now discord seems to be the main hub of communication, but GitHub is the secondary. We are encouraging all users with actual crate issues to make GitHub issues though.

[orhun]

Just sent you a collaborator invite @joshka

[sophacles]

I'd be happy to help out!

(Sorry for the slow reply I was taking long weekend.)

[orhun]

Sent you a collaborator invite!

[kdheepak]

I would also like to help out in any way I can!

[joshka]

Hey @Valentin271 and @a-kenji would you be interested in being added to the maintainer's list?

[Valentin271]

Gladly yes! I'm already on the discord server.

[a-kenji]

I am also willing to contribute, tough my bandwidth varies. I have grown fond of the project and want to help out.

[joshka]

Sweet - we're mainly looking for a few extra eyes on reviews when you can spare some time. Many hands make light work.

[orhun]

Hey @a-kenji, are you on Discord? What is the best way to reach out if there is anything urgent?