Feedback for more engagement

[RonaldHensbergen]

Hey! I'd love to understand your experience better to make CDS more welcoming for new contributors like you. Could you share:

• How did you discover CDS? (GitHub search, Awesome list, someone recommended it, etc.)
• What was your first impression? Was the README and documentation clear enough to understand what the project does?
• When you decided to contribute, what was easiest? What was hardest or confusing?
• Are there any barriers that almost stopped you from contributing? (Setup, unclear code, confusing contribution process, etc.)
• What would make it easier for others like you to start contributing?
• What makes you stay?
• Are there other ways for you to find repos to contribute to?

Your feedback is super valuable — it helps me create a better experience for the next contributors. Thanks! 🙏

[RonaldHensbergen]

Especially from you @SemTiOne

[SemTiOne]

Happy to share!

How I found CDS: GitHub Search by is:good-first-issue is:help-wanted language:python

First impression: README was thorough, contract-based wiring clicked fast. Codespaces setup was polished and tidy.

Easiest part: Writing docs or small code changes.

Hardest/most confusing part: Finding a security vuln, reporting it via security advisory, and fixing it. Also bigger changes in general.

Barriers: None that blocked me outright.

What would help other new contributors: The PR template's validation command (python -m unittest discover) doesn't mention docs linting even for docs-only PRs.

What makes me stay: Clear scoping.

Other ways to find repos: https://goodfirstissue.dev

[RonaldHensbergen]

Great, thanks! I really think you stepped up your game with the security advisory and bringing up your own changes (without a connected issue)!