Interested in helping the Chapel project grow?
Here are some ways to get involved and help nurture the Chapel community:
Easy Actions
- Star the project on GitHub
- Follow us on social media
- Subscribe to our YouTube channel
- Like, repost, and amplify Chapel content you appreciate
- Attend weekly project and/or deep-dive meetings
- Attend the monthly educators meeting
- Ask questions on Chapel discussion forums
- Invite a Chapel community member to…
- speak at a seminar you’re involved with
- run a demonstration for your group
- take part in an interview on your blog/podcast
- Propose some other way to get involved
Use Chapel
- Download and install Chapel
- Compile and run sample codes:
- from the
examples/directory of your installation - from the website’s front page
- from the examples page and repo
- from the
- Reach out to a Chapel developer to explore pair-programming code patterns of interest
- Learn Chapel
- Write your own applications in Chapel
- Report any bugs you encounter or feature requests you wish for as GitHub issues
- Share your work with the community by
- mentioning it on Discord
- doing a 5-minute demo in our weekly project meeting
- proposing a longer introduction in a weekly deep-dive meeting
- proposing and writing a Chapel blog post
- submitting a talk to ChapelCon
- contributing the code back as a Mason package, example, or test1
Help Improve Chapel1
- Improve or extend Chapel’s documentation by editing its sources
- Improve the Chapel website
- Add, improve, or extend Chapel’s standard or package library modules
- Check open Chapel issues for ones labeled good first issue or easy / straightforward
- Browse Chapel’s documentation for contributors
- Compare, analyze, and improve Chapel performance relative to other approaches
- Conduct and publish original research relating to Chapel
- Port Chapel to, support it on, or package it for a new platform
- Help improve the Chapel compiler and/or runtime
Help Fund Chapel
- Fund work you’d like to see done on, or in, Chapel through:
- development and/or support contracts
- the Linux Foundation
-
To contribute back to the Chapel GitHub repository, be sure to familiarize yourself with the Developer Certificate of Origin (DCO) ↩︎ ↩︎