We welcome issues, contributions and discussion from all users, regardless of background or experience level. In order to create a positive and welcoming environment, all interactions are governed by Prefect's Code of Conduct.
Please consider Chris White the main point of contact for the Prefect repo.
- for feature requests or bug reports, please open a new GitHub issue
- for realtime discussion or help, please visit our Gitter chat
- important architectural and design decisions are memorialized in Prefect Improvement Notices (PINs)
Prefect encourages users to contribute in any way they can!
There are a number of ways you can get started contributing:
- closing issues: the issue board contains issues with the tag "good first issue" which should be approachable for first time contributors
- documentation: Prefect prioritizes its documentation, as this is usually the first place users go to look for help. If you find any typos, or want to update something for clarity, users everywhere will thank you!
- the task library: Prefect's task library helps users build workflows even quicker by abstracting away common boilerplate. If you know of a common operation that isn't represented, open a Pull Request to add a new task to the library!
See our Development Guide for more information on how to get started.
The Prefect Platform
The "Prefect Core" engine is maintained by Prefect Technologies, Inc. and is the driving engine of the Prefect Platform, which extends Prefect Core to include:
- a full GraphQL API
- a complete UI for flows and jobs
- remote execution clusters
- automatic and asynchronous scheduling
- permissions and authorization
- projects for flow organization
- secure runtime secrets and parameters
- any many more features...
Please get in touch to apply for access.