Call for additional Mapster maintainers

[andrerav]

Hi Mapster community,

2024 was rough year. In february, I unexpectedly lost a close family member. I have to admit that this has been tough to deal with on a personal level. Unfortunately, this indirectly affected Mapster, and for that I apologize. As the sole maintainer, I simply haven't been able to keep up with incoming issues, pull requests and getting the contributions pushed out to new releases. In short -- being a single maintainer simply doesn't scale well, and especially when times get tough. So, to ensure that Mapster remains a reliable and up-to-date tool for the .NET community, I’m now looking for additional maintainers to join the project.

Typical responsibilities may include:

• Pull Requests: Reviewing contributions, providing constructive feedback, and merging approved changes.
• Issues: Triaging new issues and, to the extent possible, resolving existing issues.
• Releases: Maintain a reasonable release cycle that meets community expectations.
• Code quality: Continuously improve the code quality.
• New features: Nominate and implement new ideas and features.
• Documentation: Improving clarity, fixing typos, and keeping the wiki up to date.
• Community: Engaging in discussions and questions and fostering collaboration and contributions.

If you have the time and interest, I’d love to hear from you. This invitation is open to anyone passionate about Mapster and open source collaboration. Selection criteria will prioritize relevant skills and past contributions to the project. I am hoping we can onboard at least 2 additional maintainers.

I will of course remain as a maintainer myself and continue to help out as much as I can :)

Please reach out via email at andreas.ravnestad@ramn.no to express your interest.

[andrerav]

I hope that @DocSvartz and @stagep will read this and give it a think :)

[iAmBipinPaul]

sorry for your loss @andrerav 🙏
if possible, please post this on dotnet reddit.
https://www.reddit.com/r/dotnet/

[DocSvartz]

I’m sorry for your loss @andrerav .

I can join Mapster maintainers. But at about the current level as I do it now.

In these areas I most likely cannot help:

Releases: Maintain a reasonable release cycle that meets community expectations.
Code quality: Continuously improve the code quality.

[andrerav]

That's great to hear @DocSvartz :) @stagep has also confirmed that he will step up. I have added you both to the organization and assigned appropriate roles. Should we keep all discussion on this board, or would you prefer a public Discord server to discuss next steps?

[stagep]

Let's keep the discussion here in the repo. We can start a new discussion that deals with the overall direction or just continue it here in this discussion. I spent the last couple of days looking at a range of issues. Some are old and may already be addressed and / or no longer relevant. I would like to close a lot of issues with a comment that if the issue is still active and unresolved then reopen the issue. Alternatively, we do the opposite and comment that this issue will be closed in 7 days unless there is a response back that it is still an issue. Do you have a preference @andrerav ?

[DocSvartz]

@stagep OK

[DocSvartz]

I plan to work on #755 and #723 please don't close them.)

[stagep]

Anything with recent activity will not be closed. I will focus on dormant issues to start.

[stagep]

Do you like the following comment on closing issues:

In order to identify issues that are still active, we are closing issues that we believe are either resolved or are dormant. If your issue is still active then please reopen. Thanks.

[andrerav]

Yep, looks good to me :)

[DocSvartz]

@andrerav @stagep I would like to agree on the format of communication between Maintainers
For example:
In case of agreement, is it enough to put a reaction 👍 or should always give a text response?

[andrerav]

Both are fine with me, just keep in mind that thumbs up won't give the other party a notification in the app or by email :)