Contribution process
Last updated
Was this helpful?
v0.42-branch
Last updated
Was this helpful?
After familiarizing yourself with the documentation, the simplest way to get started is to:
Setup your developer environment by following .
Either create a or make a draft PR (following ) to get the ball rolling!
See for more details here
We follow a process of . If you believe you know what the project needs then just start development. As long as there is no active opposition and the PR has been approved by maintainers or CODEOWNERS, contributions will be merged.
We use our , and to communicate development ideas.
Note: There may not always a corresponding CODEOWNER for the affected code, in which case the responsibility falls on other maintainers or contributors with write access to review + merge the PR
Please to the master branch of the Feast repository once you are ready to submit your contribution. Code submission to Feast (including submission from project maintainers) require review and approval from maintainers or code owners.
PRs that are submitted by the general public need to be identified as ok-to-test. Once enabled, will run a range of tests to verify the submission, after which community members will help to review the pull request.
See also for other guidelines on making pull requests in Feast.
for other ways to get involved with the community
for tips on how to contribute
to see what others are working on
for a folder of previously written RFCs