Make community resources more discoverable
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github
- Domain
- documentation
Research direction
Open the linked wolfi-dev organization and wolfi-dev/os pages first, and inspect where community information is currently presented. Update those pages so the monthly community meeting and other community resources are clearly mentioned, then verify that a visitor can discover Wolfi's community participation from both URLs.
Written by the indexing model from the issue text.
Description
If you are not already aware that there is a Wolfi community, you are not going to find it. Specifically, the following pages should mention that there is a monthly community meeting and other community resources:
Otherwise folks might get the wrong idea about Wolfi not being open to community participation.
- Dominant language
- No language data
- Stars
- 24
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·