mirror of
https://github.com/vmware-tanzu/velero.git
synced 2026-08-21 14:46:07 +00:00
Steve KrissandNolan Brubaker
48792ece1f
* update import paths to github.com/vmware-tanzu/... Signed-off-by: Steve Kriss <krisss@vmware.com> * update other GH org refs to vmware-tanzu Signed-off-by: Steve Kriss <krisss@vmware.com> * site and docs: update GH org to vmware-tanzu Signed-off-by: Steve Kriss <krisss@vmware.com> * update travis badge links on docs readmes Signed-off-by: Steve Kriss <krisss@vmware.com>
22 lines
1.3 KiB
Markdown
22 lines
1.3 KiB
Markdown
## Start contributing
|
|
|
|
### Before you start
|
|
|
|
* Please familiarize yourself with the [Code of Conduct][1] before contributing.
|
|
* Also, see [CONTRIBUTING.md][2] for instructions on the developer certificate of origin that we require.
|
|
|
|
### Finding your way around
|
|
|
|
You may join the Velero community and contribute in many different ways, including helping us design or test new features. For any significant feature we consider adding, we start with a design document. You may find a list of currently in progress new designs here: https://github.com/vmware-tanzu/velero/pulls?q=is%3Aopen+is%3Apr+label%3ADesign. Feel free to review and help us with your input.
|
|
|
|
For information on how to connect with our maintainers and community, join our online meetings, or find good first issues, start on our [Velero community](https://velero.io/community/) page.
|
|
|
|
Please browse our list of resources, including a playlist of past online community meetings, blog posts, and other resources to help you get familiar with our project: [Velero resources](https://velero.io/resources/).
|
|
|
|
### Contributing
|
|
|
|
If you are ready to jump in and test, add code, or help with documentation, please use the navigation on the left under `Contribute`.
|
|
|
|
[1]: https://github.com/vmware-tanzu/velero/blob/master/CODE_OF_CONDUCT.md
|
|
[2]: https://github.com/vmware-tanzu/velero/blob/master/CONTRIBUTING.md
|