You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use oxyplot in many of my core projects and have had a great experience, but I've noticed that many pull requests haven't been merged, and the last release is still in 2024. It seems like everyone has lost enthusiasm.
I jest: the problem is just that the trusted maintainers don't have the time/energy to commit, and in many ways OxyPlot is a hard project to work on because it has a large use-base who don't want us to break things by experimenting with stuff. I was hoping to pick things up again after the release of Avalonia 12, but sadly that didn't happen (I actually did the port... but there's an awful lot more to it than that)
Please do keep poking us (or at least me): working on stuff that people actually use is the main motivation for trying to get back on this, and the more voices the more likely I am to actually find some time.
Reacted by Ethan Pedersen, pl-jcarter, Øystein Bjørke and Mark Ridgwell
idk if I offended anyone, and I apologize for my question. I'm also a loyal user of this project, and I only asked because I care about its future. I don't know what I can do to contribute to this open-source project…my coding skills aren't sufficient to make any contribution.
Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: VisualMelon ***@***.***>
Sent: Wednesday, May 13, 2026 1:32:06 AM
To: oxyplot/oxyplot ***@***.***>
Cc: Martin Hung ***@***.***>; Author ***@***.***>
Subject: Re: [oxyplot/oxyplot] Is this open-source project still running? (Issue #2165)
[https://avatars.githubusercontent.com/u/5646475?s=20&v=4]VisualMelon left a comment (oxyplot/oxyplot#2165)<#2165 (comment)>
2024, that recent?!
I jest: the problem is just that the trusted maintainers don't have the time/energy to commit, and in many ways OxyPlot is a hard project to work on because it has a large use-base who don't want us to break things by experimenting with stuff. I was hoping to pick things up again after the release of Avalonia 12, but sadly that didn't happen (I actually did the port... but there's an awful lot more to it than that)
Please do keep poking us (or at least me): working on stuff that people actually use is the main motivation for trying to get back on this, and the more voices the more likely I am to actually find some time.
—
Reply to this email directly, view it on GitHub<#2165 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AH6TYPZPC4RJ4CHZ2FIZDOT42NNZNAVCNFSM6AAAAACYYPL6H2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIMZTGA3DGNBQGY>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
Sorry, I hope that didn't come across negatively! No offence was taken!
I really do appreciate people reaching out and asking what's going on; it is just hard to find the time and energy necessary to do any meaningful work, and it's another whole load of work doing a release, and it's unhelpful to pop-up for 5 minutes to do a release only to find it had bugs and that you don't have time to fix them.
@VisualMelon I would love to join the core team of this open source project to help out when possible. I also have limited time, but I believe that is how it goes with most open source projects. Many small contributions. Feel free to reach out
As many others I want to keep it alive and I don't mind helping once in a while
@AndreCL great to hear; I can't/won't make those sorts of decisions regarding the core team, but if you're happy to do the leg work then I'll continue to try to find time for review and hopefully between us we can try to get a release out at some point with your fundamental fixes and go from there (please continue to ping me when the CI falls over or if I don't respond). OxyPlot hasn't been part of my job for well over a year now, so I'm increasingly ill-placed to make future-looking decisions, but hopefully I can still work out how to push a nuget package from time to time.
@VisualMelon, @AndreCL,I'd be happy to at least help support the WPF implementation (got 15+ years of experience with this platform). We use OxyPlot quite a lot and need to keep this project alive.
I think the project itself is used so many places and has potential to keep being used, but the core team is too small so there are some bottlenecks. This is why there isn't releases for a long time.
It is a shame because that makes new solutions choose alternatives. I hope the core team can be expanded so that this project doesn't die a slow death as many existing projects depend on this project being alive
Thanks for raising the question!
This has gradually turned into a pretty big project, 19 repos, 30-40 nuget packages, 618 issues in the main repo...
I agree core team should be expanded so we can handle PRs and prioritize the issues. I suggest to reset the team who has repo write permissions, then get new candidates (with some kind of vetting).
@oxyplot/admins
@oxyplot/developers
@objorke I'd certainly be in favour of getting people who actively use the library involved in its maintenance (sadly I don't fit in that bucket anymore)
I would like to volunteer to help in whatever role you would like me to help.
I have a personal stake in wanting to keep oxyplot alive 😄 (using it in https://github.com/AndreCL/Oxyplot.DotNetAndroid for a personal project)
Feel free to reach out if you have any task you would like me to look into
Reacted by Ingeborg Andersson, VisualMelon and Martin Hung
Activity
VisualMelon commentedon May 12, 2026
2024, that recent?!
I jest: the problem is just that the trusted maintainers don't have the time/energy to commit, and in many ways OxyPlot is a hard project to work on because it has a large use-base who don't want us to break things by experimenting with stuff. I was hoping to pick things up again after the release of Avalonia 12, but sadly that didn't happen (I actually did the port... but there's an awful lot more to it than that)
Please do keep poking us (or at least me): working on stuff that people actually use is the main motivation for trying to get back on this, and the more voices the more likely I am to actually find some time.
MatinxHT commentedon May 13, 2026
VisualMelon commentedon May 13, 2026
Sorry, I hope that didn't come across negatively! No offence was taken!
I really do appreciate people reaching out and asking what's going on; it is just hard to find the time and energy necessary to do any meaningful work, and it's another whole load of work doing a release, and it's unhelpful to pop-up for 5 minutes to do a release only to find it had bugs and that you don't have time to fix them.
AndreCL commentedon Jun 3, 2026
@VisualMelon I would love to join the core team of this open source project to help out when possible. I also have limited time, but I believe that is how it goes with most open source projects. Many small contributions. Feel free to reach out
As many others I want to keep it alive and I don't mind helping once in a while
VisualMelon commentedon Jun 4, 2026
@AndreCL great to hear; I can't/won't make those sorts of decisions regarding the core team, but if you're happy to do the leg work then I'll continue to try to find time for review and hopefully between us we can try to get a release out at some point with your fundamental fixes and go from there (please continue to ping me when the CI falls over or if I don't respond). OxyPlot hasn't been part of my job for well over a year now, so I'm increasingly ill-placed to make future-looking decisions, but hopefully I can still work out how to push a nuget package from time to time.
MatinxHT commentedon Aug 18, 2026
I’ve come across a few job postings (in China) that specifically require OxyPlot development experience, so the library certainly holds market value.
IngeborgAtRS commentedon Aug 19, 2026
@VisualMelon, @AndreCL,I'd be happy to at least help support the WPF implementation (got 15+ years of experience with this platform). We use OxyPlot quite a lot and need to keep this project alive.
AndreCL commentedon Sep 16, 2026
I think the project itself is used so many places and has potential to keep being used, but the core team is too small so there are some bottlenecks. This is why there isn't releases for a long time.
It is a shame because that makes new solutions choose alternatives. I hope the core team can be expanded so that this project doesn't die a slow death as many existing projects depend on this project being alive
objorke commentedon Oct 17, 2026
Thanks for raising the question!
This has gradually turned into a pretty big project, 19 repos, 30-40 nuget packages, 618 issues in the main repo...
I agree core team should be expanded so we can handle PRs and prioritize the issues. I suggest to reset the team who has repo write permissions, then get new candidates (with some kind of vetting).
@oxyplot/admins
@oxyplot/developers
VisualMelon commentedon Oct 17, 2026
@objorke I'd certainly be in favour of getting people who actively use the library involved in its maintenance (sadly I don't fit in that bucket anymore)
AndreCL commentedon Oct 18, 2026
I would like to volunteer to help in whatever role you would like me to help.
I have a personal stake in wanting to keep oxyplot alive 😄 (using it in https://github.com/AndreCL/Oxyplot.DotNetAndroid for a personal project)
Feel free to reach out if you have any task you would like me to look into
MatinxHT commentedon Oct 20, 2026
I would like to help oxyplot.github.io keep update.Just know that the last updated was 7 years ago.