https://github.com/flyteorg/community
Place for the community to collaborate, co-ordinate, celebrate and grow.
https://github.com/flyteorg/community
Last synced: 4 months ago
JSON representation
Place for the community to collaborate, co-ordinate, celebrate and grow.
- Host: GitHub
- URL: https://github.com/flyteorg/community
- Owner: flyteorg
- License: apache-2.0
- Created: 2023-02-13T17:19:19.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2025-12-03T19:29:06.000Z (7 months ago)
- Last Synced: 2026-01-30T17:54:17.489Z (5 months ago)
- Homepage:
- Size: 146 KB
- Stars: 8
- Watchers: 16
- Forks: 18
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Governance: GOVERNANCE.md
- Maintainers: MAINTAINERS.md
Awesome Lists containing this project
README
# Community
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.
# Communication channels
Learn how to stay informed on what's happening in the Flyte community:
## Community meeting:
* When: first Tuesday of every month at 9:00a.m. PT
* Where: live streaming on [YouTube](https://www.youtube.com/@flyteorg/streams) and [LinkedIn](https://www.linkedin.com/showcase/flyte-oss/events/)
* How: [import the calendar](https://lists.lfaidata.foundation/g/flyte-announce/ics/12031983/2145304139/feed.ics)
* Past meetings ([recordings](https://www.youtube.com/@flyteorg/playlists) | [notes](https://hackmd.io/@flyte-community/r1PDrxkEh))
### Schedule of guest presentations
| 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
## Contributors meetup
* When: every other Thursday alternating between 7:00am and 11:00a.m. PT
* Where: Zoom ([import the calendar](https://lists.lfaidata.foundation/g/flyte-announce/ics/12031983/2145304139/feed.ics))
* Past meetings: ([recordings](https://www.youtube.com/playlist?list=PLmQd1BBY9MWozXmf4NGS8zQK17E5aV8oE) | [notes](https://github.com/flyteorg/community/tree/main/minutes/contributors-meetup))
## Slack
* [Join Flyte workspace](https://slack.flyte.org/)
## Mailing list
* [Subscribe](https://lists.lfaidata.foundation/g/flyte-announce/join) to receive the weekly newsletter
# Community structure
The Flyte community is led by a [Technical Steering Committee](https://github.com/flyteorg/community/blob/main/MAINTAINERS.md) 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](https://github.com/flyteorg/community/blob/main/GOVERNANCE.md) 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:
## Working Groups
Temporary groups formed to address issues that cross SIG boundaries, delivering a concrete result or artifact.
## Special Interest Groups
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](https://github.com/flyteorg/community/blob/main/GOVERNANCE.md) for more details on these groups.
# How to contribute
There are many ways to get involved in Flyte, including:
* Upvoting [popular feature requests](https://github.com/flyteorg/flyte/issues?q=is%3Aopen+is%3Aissue+label%3Aenhancement+sort%3Areactions-%2B1-desc), influencing the release planning
* Submitting [bugs](https://github.com/flyteorg/flyte/issues/new?assignees=&labels=bug%2Cuntriaged&template=bug_report.yaml&title=%5BBUG%5D+) and [feature requests](https://github.com/flyteorg/flyte/issues/new?assignees=&labels=enhancement%2Cuntriaged&template=feature_request.yaml&title=%5BCore+feature%5D+) for various components.
* Reviewing [the documentation](https://docs.flyte.org/en/latest/) and submitting [pull requests](https://github.com/flyteorg/flytesnacks) 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](https://flyte-org.slack.com/archives/C02JMT8KTEE)!
* Taking on a [`help wanted`](https://github.com/flyteorg/flyte/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+) or [`good-first-issue`](https://github.com/flyteorg/flyte/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) and following the [CONTRIBUTING](https://docs.flyte.org/en/latest/community/contribute.html#contribute-flyte) guide to submit changes to the codebase.