Welcome to the Flyte community! You'll find here relevant information to get started as a member and potentially a contributor to the Flyte community.
Learn how to stay informed on what's happening in the Flyte community:
-
When: first Tuesday of every month at 9:00a.m. PT
-
How: import the calendar
-
Past meetings (recordings | notes)
| Date | Presenter | Topic |
|---|---|---|
| 09/03/2024 | Sebastian Schulze, Merantix | Introducing the flytekit-omegaconf plugin |
| 09/03/2024 | Devendra Johari | Flyte at Giesecke+Devrient |
| 10/01/2024 | Victor Delepine | Flyte at Wayve.ai |
| 11/05/2024 | Aswanth Krishnan, Xinzhou Liu | Flyte journey at Atomwise and QPIVolta |
| 12/03/2024 | TBC | TBC |
This meeting is open for the entire ML/Data community to share their knowledge. If you want to present, add your name and topic and we'll reach out to coordinate logistics
- When: every other Thursday alternating between 7:00am and 11:00a.m. PT
- Where: Zoom (import the calendar)
- Past meetings: (recordings | notes)
- Subscribe to receive the weekly newsletter
The Flyte community is led by a Technical Steering Committee composed of individuals from different organizations who oversee the future direction of the project, voting on proposals and acting on new initiatives for the benefit of Flyte as a project and community.
The GOVERNANCE model includes additional roles and describes different ways to contribute, earn more privileges and exercise additional responsibilities for the Flyte community.
The following types of groups are part of the Governance model:
Temporary groups formed to address issues that cross SIG boundaries, delivering a concrete result or artifact.
Persistent open groups that focus on a part of the project. The purpose of a SIG is to own and develop a set of subprojects.
See the full governance doc for more details on these groups.
There are many ways to get involved in Flyte, including:
-
Upvoting popular feature requests, influencing the release planning
-
Submitting bugs and feature requests for various components.
-
Reviewing the documentation and submitting pull requests for anything from fixing typos to adding new content.
-
Joining a SIG/WG to learn, give your opinions, and help to build solutions
-
Speaking or writing about Flyte or any other ecosystem integration and letting us know!
-
Taking on a
help wantedorgood-first-issueand following the CONTRIBUTING guide to submit changes to the codebase.