flyteorg / community Goto Github PK

Add a proposal providing structure for more focused collaboration in the Flyte community, indicating the criteria and process to start and operate Special Interest Groups and/or Working Groups

Han-Ru has consistently demonstrated exceptional dedication in contributing to the Flyte project, making invaluable contributions to the community.

Highlighted contributions

• ChatGPT agent
• Databricks agent
• Sync plugin
• FlyteChatGPTSummaryBot
• Email notification in the sandbox
• Improve test coverage
  • flyteorg/flyte@033276d
  • flyteorg/flyte@ac4ec7d
• Added Flyte sensor example.
• Added GPU enabled sandbox image
• Tons of PRs to improve the Flyte agent
• Tons of PRs to improve the Kubeflow plugin
• Flyte blog, tutorial, video.

Developing an LLM app with Flyte Agents

More detail

• https://github.com/flyteorg/flyte/commits?author=Future-Outlier
• https://github.com/flyteorg/flytekit/commits?author=Future-Outlier

Have you been an elected Contributor for at least 6 months?

flyte (monorepo), flytesnacks

What SIG/WG are you part of?

Any other context you wish to share?

Highlighted contributions

• Flytekit timeline deck
• Flytekit runtime metric
• Real-time flyte deck
• bug fixes for the Ray plugin
• https://github.com/flyteorg/flytekit/pulls?q=is%3Apr+author%3AYicheng-Lu-llll

What repositories do you expect to keep contributing to?

flyteadmin, flytekit, flyteidl, flyteplugins, flytepropeller

What is the name of your current organization?

UIUC / Influxdata

Any other context that you wish to share?

cc @Yicheng-Lu-llll

Highlighted contributions

Plugin:

• vscode plugin: flyteorg/flytekit#1922 (done, in review)

• Improve data persistence:

• Rust: flyteorg/flytekit#1936 (in progress)

• Python: flyteorg/flytekit#1869 (in progress)

Flytekit:

• Add type transformer for datetime.date: flyteorg/flytekit#1786 merged
• Add support for execution name prefixes: flyteorg/flytekit#1803 merged
• add default project domain in execute launch plan: flyteorg/flytekit#1894 merged
• Fix remote integration tests: flyteorg/flytekit#1896 merged
• Add support for execution of reference entities: flyteorg/flytekit#1808 done, in review
• local cache ignore portion: flyteorg/flytekit#1914 done, in review

Flyte:

• Provide a way to ignore portions of the signature for cache key calculation: flyteorg/flyte#4324 done, in review
• fix the compatibility to Mac: flyteorg/flyte#4260 merged

Flytesnacks:

• add type datetime.date: flyteorg/flytesnacks#1084 merged
• fix execution name: flyteorg/flytesnacks#1095 merged
• add execution name prefix examples: flyteorg/flytesnacks#1098 merged

What repositories do you expect to keep contributing to?

• flyte (monorepo), flytesnacks

What is the name of your current organization?

Any other context that you wish to share?

Nominated by @ByronHsu

Currently, the Contributor role privileges include direct branching into the repo.

In order to establish a gradual assignation of permissions, Contributors should only be allowed to submit PRs from forks, while keeping the branching permissions for Maintainers and above

Highlighted contributions

Just a sample: flyteorg/flyte#3620

What repositories do you expect to keep contributing to?

flyteadmin, flytekit, flyteidl, flyteplugins, flytepropeller

What is the name of your current organization?

LinkedIn.

Any other context that you wish to share?

Currently, Flyte's governance model include the Contributor role. Nevertheless, the term Contributor is not unique in OSS and using it for this role remains confusing. As a workaround, the community has been adding the Core prefix to it.

Adopting a more standard role name like Committer, to indicate an individual with Write permissions in the repo, could be better aligned with the structure of other projects and organizations.

To vote, just add a thumbs up/thumbs down reaction to this issue.

Voting will be open until December 1st 2023.