Repository navigation
The future of maintaining UnitsNet #1747
angularsen
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
@lipchev @tmilnthorp
Hi guys, I just wanted to chime in and say I'm truly swamped at work and life, have been for a long time and am not sure when and if I can get back to this repo in any sufficient capacity really.
I am not able to follow up on all the incoming stuff, and I am frankly feeling kind of burnt out from this project. Not in life, but on maintaining the project. It's been many years and many long evenings, but since I haven't used UnitsNet in my work or hobby projects for many years, I don't really get to reap the rewards myself or experience the pain points myself. And that puts me in a bad position to contribute meaningfully and makes it harder to put in the attention and love needed.
I'm thinking, either one of you or both take on a core maintainer role and more independently follow up and drive issues and PRs, or we park the repo in maintenance mode and have other forks and nugets naturally rise up and succeed it.
What do you guys think?
By the way @tmilnthorp, to your question in #1745 :
UnitsNet.Modular is not intended as v7, it is highly experimental and a proof of concept. I don't really have any ambition for it other than scratching an itch I'ved had for years, and hopefully someone would find it useful.
All reactions