Closed ZueffC closed 9 months ago
The author mentioned once that he is done with the project and won't do anything else. That's why I created a fork you might be interested in. It's not actively maintained by me, but I do at least update dependencies and check and merge pull requests, so if you find a bug and have a fix for it, share it with the community :)
https://github.com/go-sqlx/sqlx
Hope that helps you :)
@dtrzepala @TheBotlyNoob @gmdias727 @yudintsevegor @Relvox @lcs86-dev @roger-russel @hirasawayuki @BruAPAHE @guitarpawat @fschuermeyer might also be interested in that 🙂
in #878 I also mentioned the post:
https://www.reddit.com/r/golang/comments/l43wn7/comment/gkm42xz/
The author mentioned once that he is done with the project and won't do anything else. That's why I created a fork you might be interested in. It's not actively maintained by me, but I do at least update dependencies and check and merge pull requests, so if you find a bug and have a fix for it, share it with the community :)
https://github.com/go-sqlx/sqlx
Hope that helps you :)
good job!
Hello! Sorry for the delay in replying. @ardan-bkennedy and I recently stepped in to help maintain the project. We are in the process of triaging all the opened PRs and then issues, and we plan to address outstanding issues and upgrade the library to support generics and new Go versions, among other things.
@dlsniper sounds good :) But what I would like to suggest, is still moving the upcoming development to our fork go-sqlx because it's more convenience for people and SEO to see a project in a GitHub organization instead of a user (no offense).
If you are interested in that, I would invite you to join the organization and even transfer it after some time to you, when I'm convinced updates are continuously merged and it's not just a phase 🙂
We want to keep this project alive, even if it's under a person's account.
The reason is that pretty much everyone knows about the project, it has a lot of community traction already and tooling, such as GoLand, already integrates nicely with it.
We thought about forking the project before asking for permissions to maintain it, but we had the issues as I just mention coming up.
If it turns out we can maintain it properly, we might consider moving this to an organization, but there are a lot of steps and time until we can begin to think about that.
At the moment, we are triaging the PRs, I'm planning to implement proper integration tests in CircleCI, then start merging some of the obvious ones, move some things from @ardan-bkennedy's lib to the project, implement newer Go features such as generics, and a bunch more.
But, all of this will take time and effort and our biggest concern is that we need to make sure that whatever we do we can provide the same level of stability and clarity that @jmoiron had for the project. That, and the fact that the project is fairly stable/complete otherwise.
I don't know yet an answer to all these challenges, so time will tell if we'll do a good job or not.
Ok, works for me 🙂
@dlsniper is this work taking place on the update-dependencies
branch?
Hi folks! As I see there isn't any activity in repository for the whole four years. Is this project closed or moved to another git-like CVS or it's just abandoned?