What I Learned Contributing to Prefect, dbt, and Airflow (An Honest OSS Retrospective)

For ninety days, the author ran parallel tracks of portfolio releases, Dev.to writing, and OSS contributions to Prefect, dbt docs, Airflow, and Meltano. The portfolio sites were br413.github.io and the 90-day plan was available at github.com/br413/br413. The author followed the rule of commenting on the issue before opening a PR, which resulted in merges of several upstream PRs such as Prefect #22500 for Kubernetes readiness, dbt docs #9606 for prefixed custom schema troubleshooting, and Airflow #71158 for approval with the need for a second reviewer.

The author identified four PRs still open after mid-August 2026: Airflow #71158, dbt docs #9781, Meltano #10253, and Prefect #22533. The author learned that Airflow #71158 needed a second reviewer, dbt docs #9781 waited on maintainer bandwidth, Meltano #10253 was waiting for a PR tied to a maintainer-requested issue, and Prefect #22533 had changes requested that were addressed.

The author advised against opening too many open PRs simultaneously and suggested rebasing early to avoid CI breakage from unrelated upstream changes. The author also recommended maintaining a consistent weekly rhythm of at least three public commit days per week for both contribution graph and maintainer trust.

The author connected portfolio and OSS work through a production-data-pipeline, data-quality-observability, lakehouse-platform-starter, Dev.to articles, and upstream fixes. Each layer addressed different reviewer questions, ultimately demonstrating the ability to design, explain, and improve production-style stacks. The author emphasized the importance of never backdating commits, preferring data-platform repos, and ensuring that portfolio, portfolio site, and resume agree.