Hello Airbyte Community!
I’m Richelle, the new Senior Developer Advocate at Airbyte, and I have good news. We heard your pain about OSS contributions. You’ve contributed a lot of time and energy to submit PRs that sit open for far too long.
We’re working on a plan to better track and review your PRs. The first step is going to be closing PRs we think might be stale or redundant. This work will help clear the way for relevant PRs to be merged into the codebase. Once we do that, we’ll have a much clearer picture of the size of the backlog we need to address.
We'll use our best judgment, and we know we won't get every call right. Closing a PR isn’t a final verdict. Instead, think of it as our best guess that the PR no longer needs a review. If you feel that your PR is still relevant, the PR will still be there for you to re-open. And feel free to DM me to resolve the issue.
If we close your PR, please review the comments or reply when you can. We may close the PR for a number of reasons:
1. We need clarification: From the looks of the PR, we shouldn’t allow the changes to merge at this time. If you disagree, your response will help us reconsider the PR as quickly as possible.
2. A different PR may have resolved the issue: If the PR we point to doesn’t match your use case or ignores an edge case, please let us know.
3. Your PR is for an old version: If the issue persists on the current version of Airbyte or the connector, you will need to update the PR to this new version. (I’m sure the version was current when you submitted the PR; I’m sorry we need to ask you for extra work.)
With these PRs closed, we will have a much better sense of how to tackle the backlog and add a better system moving forward. Thank you in advance for your help!
👍 5
octavia loves 4
airbyte star 3