Skip to content

Commit 5033bba

Browse files
committed
docs: improve contributing guide with community engagement and getting started info
Signed-off-by: Vishal Anarase <iamvishalanarase@gmail.com>
1 parent b25aa0e commit 5033bba

File tree

1 file changed

+20
-0
lines changed

1 file changed

+20
-0
lines changed

website/content/en/docs/community/contributing.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,26 @@ For reporting vulnerabilities, see <https://github.com/lima-vm/.github/blob/main
1313

1414
## Contributing code
1515

16+
### Getting Involved
17+
18+
We welcome new contributors! Here are some ways to get started and engage with the Lima community:
19+
20+
#### Introduce Yourself
21+
22+
- Join our [community communication channels](https://lima-vm.io/docs/community/#communication-channels) (Slack, GitHub Discussions, Zoom meetings) and say hello! Let us know your interests and how you’d like to help. Also share how your [organization](https://github.com/lima-vm/lima/discussions/2390) is involved with Lima.
23+
24+
#### Learn Where Work Is Needed
25+
26+
- Check the [Lima Roadmap](https://lima-vm.io/docs/community/roadmap/), related [issues](https://github.com/lima-vm/lima/issues), and [discussions](https://github.com/lima-vm/lima/discussions) to see ongoing and planned work.
27+
- Read through the [documentation](https://lima-vm.io/docs/) to understand the project’s goals and architecture.
28+
29+
#### Find Open Issues
30+
31+
- Browse [GitHub Issues](https://github.com/lima-vm/lima/issues) labeled as [`good first issue`](https://github.com/lima-vm/lima/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) for tasks that are great for new contributors.
32+
- If you’re unsure where to start, ask in the community channels or open a new discussion.
33+
34+
We’re glad to have you here, your contributions make Lima better!
35+
1636
### Developer Certificate of Origin
1737

1838
Every commit must be signed off with the `Signed-off-by: REAL NAME <email@example.com>` line.

0 commit comments

Comments
 (0)