Wyatt Johnson
3.7 KiB
Contributor's Guide
Welcome! We are very excited that you are interested in contributing to Talk.
This document is a companion to help you approach contributing. If it does not do so, please let us know how we can improve it!
By contributing to this project you agree to the Code of Conduct.
Product Roadmap
You can view what the Coral Team is working on next here https://www.pivotaltracker.com/n/projects/1863625.
You can view product ideas and our longer term roadmap here https://trello.com/b/ILND751a/talk.
Contribute to the documentation
Clear docs are a prerequisite for a successful open source project. We value non-code and code contributions equally.
We are looking for documentarians to:
- make clarity, grammar and completeness updates,
- create new / missing sections, and
- take the lead in making sections, or the over all structure better.
But how?
- Our public docs site can be updated here.
- Let us know if you'd like permission to update our wiki.
- Update any of our .md docs files by following this guide.
- Our API docs need to be kept honest. Update them here.
Integrate into your environment
First, set up a dev environment. Please let us know how this goes!
Talk is designed to integrate into existing environments in a variety of ways:
- Auth integrations
- Push assets into Talk
- Monitoring Hooks (coming in 2017)
If you're considering deploying Talk, please let us know! We are quite literally doing this for you and want to help you succeed any way we can.
If you are writing custom integration code in your fork of Talk, please consider keeping it generic and filing a Pull Request to contribute it back to the project! See our forking and merging guidelines for more info.
Write some code
First, set up a dev environment. Please let us know how this goes!
Build a New Feature / Plugin
Talk is beginning life as a Commenting Platform, but is architected to support many varieties of community engagement.
Please contact us early and often if you'd like to help. We would love to hear your ideas for features and plugins and help you find a way to productively engage the project.
To get an idea of where the Coral Team is going, see:
- our product/design Trello board,
- our current stories, and
- our issues.
Examples:
Work on the Core
There is always more work to be done to make an application more stable, scaleable and secure.
If you see issues in the code or have ideas on how we may improve Talk, please consider:
- contributing a fix,
- filing an issue, or
- or otherwise letting us know.