If you're new to open source, check out our guide on how to add features.
Please join the bridge-troll email list. We need all kinds of help:
- organizers, teachers and students who want to help validate that our new improvements don't negatively affect current behavior, as well as advocating for changes you need
- visual and interaction designers
- developers of Ruby, JavaScript, HTML, CSS
- writers of documentation and important text that helps people understand how to make great events happen!
- If you see a bug in the code (or the running app), check the GitHub issues and comment on the issue if there is one. If you know how to fix it, go for it! If you don't know how to fix it, please create a new issue. We're using GitHub issues for bug tracking and new features.
- Make sure you're writing tests. If you're new to TDD, come to a hack night and pair with someone who's experienced.
- We have awesome notes about from back when Women Who Code was building Bridge Troll. Check them out. Courtesy the amazing Judy Tuan.
- Or, ask the list!
- Or, do the Hartl tutorial!
- Tests. Run all the tests again, just to make sure you didn't break anything.
- You'll want to make sure your fork is totally up to date and squash + rebase your changes on top of it. We have a Git guide to help.
- Documentation. Help us figure out where our documentation can improve.
- Usability testing. What interactions are bad? Where did the app not do what you thought it would do?