Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maintainance #166

Open
kant2002 opened this issue Feb 15, 2025 · 2 comments
Open

Maintainance #166

kant2002 opened this issue Feb 15, 2025 · 2 comments

Comments

@kant2002
Copy link
Contributor

Hi.

I would like to ask, if you have will, stamina and time to maintain with library? I know, that's always possibility to have a fork, and maintain myself, but maybe you can add additional maintainer, or maybe you can transfer project to fsprojects org?

Currently library is slipping behind for no reasons, except lack of ask from community probably.

Would really like to hear your opinion on the matter. Thanks for your work.

@simon-reynolds
Copy link
Collaborator

Hi @kant2002
I have the will, but not the time unfortunately. If you're able to help keeping the project up to date any and all help is appreciated

@kant2002
Copy link
Contributor Author

Heh. I have a really strong headache from updating dependecneis using Packet. Is there possibility that we switch to MSBuild ? I cannot

  • perform cosmetic update of deps, to test water
  • Full update to .NET 8 without EF Core 6 update

i did not try yet yolo to EF Core 8, but I prefer somehow have transition period (even if EF core 6 is outdated)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants