:octavia-wave: Hi team! When contributing, what's ...
# connector-contributions
y
octavia wave Hi team! When contributing, what's the process to start involving the Airbyte team? Do they regularly check issues and PR, or should we ping them in this channel or somewhere else?
p
I recommend reading this doc https://docs.airbyte.com/contributing-to-airbyte/ You found a good Slack channel 👌🏻 From my experience, it depends on contribution and timing (during hackathons there might a bigger delay). Some pull requests are checked faster, some slower, but my approach is to create pull request and drop a link here.
u
I’m responsible and have quite a backlog 😆. What contribution are you considering?
y
I sent one yesterday: issue, PR.
In the "contributing to Airbyte" doc, I was not seeing a clear link between:
Copy code
8. Write a PR title and description that follows the Pull Request Handbook.
9. An Airbyte maintainer will trigger the CI tests for you and review the code.
I went with a "quick fix", considering Zendesk has introduced a hard deadline end of February for migrating to the zendesk-chat v2 API. The pip install command installs a version of the cdk that is too high.
Copy code
pip install airbyte-source-zendesk-chat
Another way to solve this would be to upgrade the connector to the latest version of the cdk. With the deadline from Zendesk, going to a quick fix seemed better to me, but I could understand if we want to upgrade the connector entirely.
u
Looks the right path for now. @Yohann Jardin do you mind filing an issue to upgrade the cdk dependency to latest? So we don’t loose track of it?
y
Sure, I'm on it
Done: https://github.com/airbytehq/airbyte/issues/52085 (+ added in answer to your comment in the PR)
Small followup: I was able to test the new version with PyAirbyte, and it works perfectly now. Thanks a lot for the quick feedback on this.