Status of Repository

[kme1018]

Is this project dead? I don't see any new releases tags for over a year and minimal action on new issues since the last release.

[Ga68]

yeah - seems to be
I ended up forking it and then merging the PRs that were useful for me
so I think this one is in personal-maintain-mode
it's a fantastic repo

[aersam]

Agree that it's a great repo, well-designed. We use it for our lakeapi. Migration away from pypika seems harder than initially thought, most other projects are lot more complicated. However we faced some minor issues and will end up with a fork, too. Not a good situation... @Ga68 : we might do a PR to your fork, too

[wd60622]

I reached out to one of the latest contributors on LinkedIn found on their GitHub. No response from them

[inkmix]

hi,
the team with the main contributors had a lot of changes to go through. we've recently talked about the project and aim to slowly! but steadily go through open PRs. no promises though. but we love the project and are happy for the interest in it and see what we can do.

[AzisK]

Hello, I will double down on the maintenance together with @inkmix. Our team inherited a product that uses pypika. We also had a lot of changes and barely have free hands to work on it but I am already here. I already am and will be looking over it. I am new to this repo but happy to see so many excited people about it. Let's go!

[danielenricocahall]

If any assistance is needed with maintenance, please feel free to reach out. I would be happy to assist, as I frequently use this library.

[AzisK]

@danielenricocahall your input into pull requests would be very appreciated. Do you wish to receive a special status or how does it work? Otherwise I could reach out to you if I have some doubts about one or another part

[wd60622]

I have similar relationship to this repo and can keep an eye on any open PRs as well. @AzisK has the contributor team set any contribution guidelines before? maybe a CONTRIBUTING.md

[danielenricocahall]

@AzisK if there is special status I can be added - otherwise I can just be tagged for feedback if needed.

[AzisK]

Good point. CONTRIBUTING.md is a way forward. Feel free to create such a PR

[wd60622]

Good point. CONTRIBUTING.md is a way forward. Feel free to create such a PR

Sounds good. I can draft up a CONTRIBUTING.md file and add a PR

[wd60622]

I've started a PR here: #758
I would appreciate anyone's feedback! especially those that have contributed more!

Also, how much of the original team is still around? Or is it just new Kayak people?

I think it would be good to set up some actions for documentation builds upon, say, merge to main. I don't see that unless I am missing this.

[twheys]

@wd60622 I'm still around just have been working on other projects the last few years and haven't had any bandwidth for this project during that time, but I might be able to get involved more in the near future.

[wd60622]

@wd60622 I'm still around just have been working on other projects the last few years and haven't had any bandwidth for this project during that time, but I might be able to get involved more in the near future.

Awesome! Thats good to hear 😃

Hopefully that contributing file is a good start, but I think it'd be good to be explicit about any standards, expectations, when and where versioning happens, issue labeling, future roadmap, etc

Think taking advantage of as much automation to display such info to a contributor would be great. This might come in form of welcome bot based on various actions etc

Also, have you guys considered taking advantage of the GitHub Discussions too? That could be a location for Question focused issues