-
Notifications
You must be signed in to change notification settings - Fork 37
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
Pull requests / updates? #24
Comments
Hi @hansmbakker i'm currently maintaining this fork as I use it at work. If you want to improve the library you can make a PR there and i'll have a look at it and push the changes to nuget. |
@vestervang great that you continued the work! Please see some updates in ProrepubliQ#7 Could your repo somehow take over the "lead role" in the sense that the issue reporting is here but the most recent updates are in your repo? |
So I've just cloned the repository that @vestervang holds, it looks like this was updated to .NET 7, not a huge deal but is there a reason we want to target that as opposed to netstandard like this upstream project does? FWIW out of the box the current Ubuntu LTS (Jammy) does not have I also noticed that the branch doesn't have the ability to open issues; do we want to still try an coordinate with this upstream project or do we want to attempt a hard fork? EDIT: I went ahead and took the initiative to retarget the library itself back to |
Hi @aolszowka, I have enabled issues on the repo now and there is no reason as far as i can see that we should target dotnet7 specifically. |
Ok I am going to start coordinating work over there on that repository, please let me know if it becomes too much. I've got some free time today to grind this! |
Hi @hashtagchris, I was wondering whether you'd be willing to review the work that @gvheertum and @vestervang have been doing, and merge it?
I mean the caching PR (#15) and the commits in @vestervang's fork (main...vestervang:DotNet-BlueZ:main)
I'd like to look into a dotnet 7 upgrade, and am wondering whether a PR would be accepted?
The text was updated successfully, but these errors were encountered: