About Project Maintenance

[AWeirdDev]

im currently working on something else so i cannot really look into the pull requests/issues, and i cannot update the project everytime google sneakily changes something.

if you'd like to maintain this project, i could give you a quick explanation about the project structure. contacts

the current development branch is: dev

...so don't get it wrong! :)

[dosubot]

Hi, @AWeirdDev. I'm Dosu, and I'm helping the flights team manage their backlog and am marking this issue as stale.

Issue Summary:

• You mentioned being unable to manage pull requests or update the project due to other commitments and frequent changes from Google.
• You expressed openness to transferring maintenance to someone else and offered to explain the project structure to interested contributors.
• The current development branch is named dev.
• There has been no further activity or updates on this issue since your last message.

Next Steps:

• Please let me know if this issue is still relevant to the latest version of the flights repository by commenting here.
• If I do not hear back within 7 days, I will automatically close this issue.

Thank you for your understanding and contribution!

[AWeirdDev]

zip it

[shubhank008]

@AWeirdDev can perhaps a pipeline/automation for merging passed PR changes be setup, or some trusted code-reviewers be added to the repo to merge PRs ?

[AWeirdDev]

yeah, that's a good idea. but i'm still looking for ppl who are active here and are willing to help.

[shubhank008]

yeah, that's a good idea. but i'm still looking for ppl who are active here and are willing to help.

Given the nature of project, I think people would only be active when something breaks and someone decides to fix it and PR, rather than continuously being active as I doubt there are any major features or updates the project will need.
But made the suggestion because there are some active PRs pending merge since some days/weeks which seem to be major fix for current breaking changes, and thus could be merged.

Perhaps just ask one or two of those PR pushers if they want to become maintainers and their git activity is good enough.
I would have offered too but I feel there are better and more experienced devs specially who took the time to submit fixes.

PS: I am thinking to use this codebase as a learning base to create a similar implementation for google hotels too, basically to get pricing data for a hotel and being able to create a graph/map of +-7 or +-30 days pricing for that hotel.