Looking for help with Wallaroo? Awesome. We are here to help. Before you open an issue against this repo, we ask you read the following to better direct you to the proper forum.
We ask you to refrain from opening GitHub issues for non-actionable items. We use GitHub issues to track bugs. If you are not sure how to code a particular problem, how to decipher an error message, wondering about a benchmark, or anything of that sort, please use the mailing list or IRC. Also, please check out our frequently asked questions. It's possible it has the answer to your question.
Please check our high-level known limitations document as well as our open issues to see if your problem is already know.
You have a couple of different options on how you can get help from the Wallaroo community. If you are looking for an answer "right now," we suggest you give our IRC channel a try. It's #wallaroo on Freenode. If you ask a question, be sure to hang around until you get an answer. If you don't get one, or IRC isn't your thing, we have a friendly mailing list you can try. Whatever your question is, it isn't dumb, and we won't get annoyed.
Think you've found a bug? It's entirely possible. We do extensive testing of Wallaroo, but bugs do happen. Your best bet is to write to the mailing list with your issue and verify that you are experiencing an issue; once a more knowledgeable member of the community confirms you are experiencing a bug, open an issue.
The Wallaroo community, while small, is helpful and inviting. We think you'll find interacting with us to be an enjoyable experience. You can get a lot more community-related resources in the community section of this site.