dbmate
dbmate copied to clipboard
amacneil
Call for maintainers
Hi everyone,
As you can see, I haven't had a lot of time to work on dbmate lately. It is stable and works great for most use cases, so doesn't need a lot of ongoing development, but there are occasional questions or feature requests that come up in GitHub.
I'm looking for people to help with triaging issues and/or coding.
- For issues, we need help responding to questions, asking for more information, closing issues that aren't relevant, etc.
- For coding, we're not looking to make major changes. Dbmate has a "keep it simple" philosophy, and is largely feature complete. That said, if small features can be introduced without breaking existing users or making big refactors, then we're open to it. PRs need to be reviewed and either merged or closed with appropriate reasoning. I'm happy to continue to provide high level guidance on what is/isn't appropriate from a feature perspective, but I don't have time to review and merge PRs.
If you're interested in helping with either of these, please reach out via this thread, or just jump in and start helping. Commit access will be granted as needed. Thanks!
I might try to help with some issues. I'm using dbmate on daily basis in my lab with students :-)
I don't know how much time I will have in next months, but I'll try :-D
Would love to help - I've been using dbmate in a few projects, and recently published a buildpack for using it on Heroku: https://github.com/codecrafters-io/heroku-buildpack-dbmate.
Added notifications for all activity on this repository - will keep an eye out!
@amacneil mind granting me triage access? I'd like to close resolved issues, example: https://github.com/amacneil/dbmate/issues/275
I known too little about GO lang, but I will try to help, as long you can review my PRs. I can tackle some small issues/features. What do you think?
Hi @amacneil. We're making use of dbmate at work. I would love to help out. There a few features we would like to at add in the coming months so more than happy to help.
It looks like there are plenty of volunteers, but in just in case more are needed, I can help out as well. 👋
@amacneil I left comments on issues and PRs. It looks like there are several PRs open that would be backwards compatible and straightforward to merge. I think we could ask those on this thread to try out a beta release.
To help with maintenance I would suggest trying to find a maintainer for each individual driver and trying to hand over the reigns for the driver code as quickly as possible. It's quite difficult to maintain a driver that you aren't actively using.
@amacneil do you want to make @FatherCandle the maintainer of the ClickHouse driver?
@gregwebs I agree with your idea. I do think we should have some sort of coordination to avoid breaching to much.
I am using ClickHouse driver as well
This project could be re-structured so that there would be a new repo dbmate-clickhouse. That way the maintainer can have full rights there. The repos could exist under a dbmate organization.
@gregwebs Sounds excellent to me. How do you think we should proceed with it?
Calling a fork of the repo dbmate-clickhouse and developing the clickhouse driver there seems like a pragmatic approach right now. Publish builds there called dbmate-clickhouse.
When the dbmate maintainers are ready they can either pull the latest clickhouse driver code in or decide to delete the code from dbmate and direct clickhouse users to dbmate-clickhouse. They could also decide to move much of main.go under pkg/ so that it can be imported as a go package.
Separate repos sounds overly complicated imo (any changes to core will require potential changes in all the driver repos).
If we're all sensible adults, people can maintain drivers in this repo. Let's try to get community consensus on any larger changes though.
@gregwebs @FatherCandle @dossy I gave you guys commit access, use it wisely :)
@amacneil, 👋🏻 I'm willing to help. I actively use dbmate in all my Go projects related to PostgreSQL. I have some features in mind that would benefit many devs, particularly in the realm of integration tests.
