Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

Hello contributors:

A few initiatives are in progress to try to handle the Issues/PR backlog in both flyte and flytekit repos:
1. A <https://github.com/flyteorg/flyte/blob/master/.github/workflows/stale.yml|stale bot> that's going through open Issues and PRs with the following criteria:
    a. Issues inactive for 90+ days
    b. Feature requests inactive for 270 days+
    c. PRs open, inactive and not ready for review for 270+days
2. Configured <https://github.com/google/triage-party?tab=readme-ov-file|triage-party> to analyze the backlog. The instance is available <https://flyte-triage-mqfitfefya-uc.a.run.app/s/daily|here> for anyone to take a look.
The first time you open it, it populates the cache pulling from a DB. Any of you Go wizards are welcome to improve its responsiveness :slightly_smiling_face:
How does it work? The config <https://github.com/flyteorg/community/blob/main/triage-party-config.yaml|is here> and relies significantly on labels. I've summarized the labels in <https://github.com/flyteorg/community/blob/main/MAINTAINING.md|this doc>.
:arrow_right: If you have triage permissions or higher, you're welcome to help us label open issues/PRs accordingly, or at least label your own work to feed this tool.

Any question let us know!