Discussing the future of Paket

[fpellet]

Hello,

I can see that the PR is piling up. I wanted to know if you were looking for help and how I could help you?
Even if nuget has improved, I think this project is still relevant and it would be sad to see it abandoned.
cc @forki @agross @cloudRoutine @matthid @isaacabraham @theimowski

[smoothdeveloper]

@forki, to clarify, in case of dire need, is there people from @fsprojectsgit that would be able to take over the delivery pipeline to publish new versions? (I understand the implications are not low, given what paket is).

I think this is first thing that needs to be sorted.

Overall, I think the community can handle having just a couple of releases a year, with conservative and needed changes, per your own ability to judge when you can allocate the time to batch PR merges, handle a release, and probability there is a bit of back and forth post-release, related to some PRs.

One thing that could help also, is to have clear guidelines, on how to use your own fork of paket, for people who contribute a PR to work around their own issue, but that it doesn't fit with the review / merge / release schedule we currently have.

The other aspects related to assemble a team of maintainers, is also to be considered, but not a big issue (as @fpellet, paket is still very much used and useful, no matter nuget improves).

One of the biggest thing a contributor could do, I think, is to make the solution more convenient to work with outside of windows development environment, starting with having an open issue that lists all current issues that makes that difficult.

[dsyme]

@smoothdeveloper - The role of @sergey-tihon and I would be to help find new maintainers for this project.

Are any people with maintainer status currently active in the project and are there new volunteers to contribute to maintenance?

@fpellet Would you be interested in being a co-maintainer on this repo? (nb. Given the role of the tool in the ecosystem we'd need to do some diligence on this)

[dsyme]

cc some people with current status in the repo (in addition to @forki, the originator). Note we will likely reduce the number of people with status, so please reply if you definitely want to continue to have status!

• @agross
• @enricosada
• @mavnn
• @mexx
• @cloudRoutine
• @isaacabraham
• @matthid
• @Krzysztof-Cieslak
• @theimowski

[mexx]

@dsyme: I likely will not contribute, I removed myself from the teams.

[forki]

currently I only have time to merge and release the big .NET updates. If someone wants to do more then I'm happy to give them access. Over the years we had multiple people who contributed loads at a certain time. For me personally the project does everything we need - I still use it all the time. But I don't have energy to create new stuff

[fpellet]

@dsyme If it helps, I'm willing to do it. However, I don't have much experience with this code base. But even though I'm not a co-maintainer, I'm willing to help to prepare PR (review, etc.) if someone can merge from time to time.

[smoothdeveloper]

@dsyme & @forki, thanks for giving an overview of our situation.

If none of the historical main maintainers are interested, I'm ok to be a maintainer that would:

• engage in PR and issues (to similar extent as so far)
• review / try / merge those that I find conservative
• for docs website, if I'm given access, publish a new version
• contribute to the docs when we identify bottleneck in community engagement that promotes maintaining this repository (to similar extent as so far)
• review new tickets more closely than right now

But given the implications of releasing paket, how it is used, security and delivery attack implications, I'd prefer @forki to remain the responsible person, knowing that the community is likely going to be fine with a once in a year update.

So the main delta with now would be:

• less pending PRs
• I troubleshoot with issue/pr owners, how they can workaround their issue, pending a release, and document this
• managing the tickets
• new release would have a bit more of churn, than major .NET version support

This is first measure, but I think it would be good to have a pair more of people, given the scope of the project, and me only being familiar with my own use cases.

Hope this is progress, however meager.

[smoothdeveloper]

@forki:

I still use it all the time

Could you also attest you don't use #r "nuget: , but the tried and tested #r "paket: ?

[Numpsy]

Is there anyone with access to AppVeyor around? It looks like the CI isn't running on the recently updated PRs?

[gdziadkiewicz]

Hi @smoothdeveloper @dsyme , I'm also willing to help. All the commercial stuff I do currently is on Paket, wants net10.0 in the nearest future and I really don't want to port to NuGet.

[dsyme]

Hi @forki

I suggest we make @gdziadkiewicz and @fpellet co-maintainers, and @smoothdeveloper if you like

At the same time remove any previous co-maintainers

Thanks
Don

[smoothdeveloper]

@forki let's move forward for all of this, but the publishing of new versions?

[smoothdeveloper]

@forki, thanks for my birthday present :)
and same to Microsoft for new release of dotnet.

[forki]

Happy birthday. 😅 Could you please confirm that the new alpha is working with .NET 10? Gauthier Segay ***@***.***> schrieb am Di., 11. Nov. 2025, 23:14:

…

*smoothdeveloper* left a comment (fsprojects/Paket#4300) <#4300 (comment)> @forki <https://github.com/forki>, thanks for my birthday present :) and same to Microsoft for new release of dotnet. — Reply to this email directly, view it on GitHub <#4300 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAOANDQR7DUAGMFJW4LCQL34JNVHAVCNFSM6AAAAAB7HPVYIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMJYHEYTQOJWHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>