Request for clarity on stewardship or archival of KuduSync.NET

[devlead]

Hello maintainers,

First, thank you for the work that has gone into KuduSync.NET over the years. It has been a useful tool for many people, myself included.

I wanted to raise a concern about the current state of the project. From what I can see, there has been little recent activity, and it’s unclear whether the repository is still being actively maintained. This creates uncertainty for users who continue to rely on KuduSync.NET.

With that in mind, I’d like to suggest two possible paths forward:

1. Archival – If the project is no longer being maintained, it might be best to formally archive the repository and communicate that status clearly (README, NuGet page, etc.), so users can make informed decisions.
2. Transfer of stewardship – If there is interest in keeping KuduSync.NET alive, perhaps ownership of the repository and/or NuGet package could be transferred to someone willing to maintain it.

If the latter option is viable, I’d be happy to volunteer. A while back, I started some of the work to bring the project forward with PR #27, which updates dependencies and moves it toward modern .NET support. I’d be glad to continue that effort and help ensure the tool stays usable for the community.

I fully understand that maintainers’ time is limited and priorities shift. My main hope is simply for clarity so the community knows the direction of the project.

Thank you for considering, and I look forward to hearing your thoughts.

[davidebbo]

I think that would make sense to have a proper maintainer. But I don't work there anymore, so just an opinion :)