-
Notifications
You must be signed in to change notification settings - Fork 52
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
Is InfluxData.Net still being maintained? #83
Comments
Yes, I would also like to know this |
The startup I worked at is now bankrupt. As I now work at a company that does not use the .NET ecosystem (nor InfluxDB) I won't be contributing to the project. I can't speak for @pootzko but I remember him telling me that he also does not work with InfluxDB primarily. In the end open source libraries only stay maintained as long as someone steps up to do the dirty work. I made a few small contributions to this project but stopped after I didn't use it anymore. If anyone uses this library and is prepared to dig in I believe @pootzko is willing to allow access to the repo and/or accept pull requests from your forks. But you will have to allow him to allocate some of his free time to this. |
Hi all, I was actually planning on creating a new build the next week as I'm on annual leave this and the next week. I was planning on sorting out PR's which exist and checking what people did on their forks and merging some of that back in to master as well. And perhaps look at the low-hanging fruit in terms of reported issues. Unfortunately I don't have too much free time on my hands and I don't have any personal incentives to develop new features actively (mainly because I don't need anything new on the project on which I use Influx) so I won't put much of my time into the lib. If people are willing to develop new features and fix bugs, I will commit to at least publishing them. And besides a few (what I would consider) minor bugs and missing features, I feel the lib is pretty stable (it's been running non stop in my production for more than 3 years now without issues) and performant so I don't think there's a real reason to not use it. But that's my personal opinion. Hope that answers the question? :) |
@pootzko I'm really happy how well your library have currently been behaving in my projects, but I'm afraid if it were to break right after InfluxDB 2.0 release (which is in alpha stage now), I would have to search for an alternative (InfluxDB.Client.Net looks promising). This saddens me, as I really like your API and performance. |
agree that influxDB 2 APIs have priority to be supported now. |
Hi. Unfortunately I don't really need this much at work and I don't have the time or incentive to work on it in my free time (I don't use it anywhere else). If the old API is being deprecated, I will probably have to update the project at work where this has been quietly doing its job for the past few years. At that stage I will probably update the library to support the latest API. So I'm afraid I can't promise anything, sorry. |
@pootzko it has been over a year since your last commit to master, and there are a number of open issues here on GitHub that have not been attended to. I just want to kindly ask if you plan on maintaining this library in the future or not? Thanks :)
The text was updated successfully, but these errors were encountered: