Welcome! We're very glad you're reading this; Edera is excited for all kinds of contributions! Please read the following to ensure you're aware of our flow and policies.
- Please read our Code of Conduct, which applies to all interactions in/with all Edera projects and venues.
- Before opening an issue or PR, please try a few searches to see if there is overlap with existing conversations or WIP contributions.
- For security or otherwise sensitive topics, please read our Security Policy.
- Ask questions! If you want to ask something, chances are someone else wants to ask it as well.
To get started with technical contributions, please read out [Development Guide]. If you're looking for something easy to tackle, [look for issues labeled good first issue][good-first-issue].
While it's totally fine to simply bring it up on our Discord, we encourage opening an issue on GitHub using the Bug Report template.
- For anything more than simple bug/doc fixes, please open a GitHub issue for tracking purposes.
- Else skip to step 3.
- Discuss the change with the teams to ensure we have consensus on the change being welcome.
- We encourage opening the PR sooner than later, and prefixing with
WIP:so GitHub labels it as a Draft. - Please include a detailed list of changes that the PR makes.
- Once the PR is ready for review, remove the Draft status, and request a review from
edera-dev/engineering. - After the review cycle concludes and we know you are ready for merging, a team member will submit the PR to the merge queue.