Official Bevry Support Channels

Tags: #<Tag:0x00007ff8c449ab50>


We currently have several support mediums, which one should you use?

  • For technical support, Bevry's Stack Overflow Guide should be your first stop, it will let you leverage the tremendous Stack Overflow community with our recommended tags.

  • For general discussions, Bevry's Discourse Forum is a good place to visit, it also includes many sub-categories including ones for general Problems, Suggestions and Guides. Support Guidelines.

  • For instant chat, or if you're unsure, Bevry's Slack Community is a great pit-stop. It provides camaraderie for online team and community members about a wide range of topics, including updates and quick support. We also have official IRC and Gitter rooms, however they are unsupported.

  • GitHub Issues was one of our recommended support mediums, however it is no longer the case. What did go to GitHub Issues, should now go either to the Discourse Forum (if general) or to Stack Overflow (if technical), with GitHub Issues being reserved only for project collaborators.

Members are from all different time zones, so while hopefully someone will be around right then and there to answer your question, sometimes it may take a while, so waiting patiently will be awesome. Time zone calculator

Official Telegram Chat Rooms
Official IRC Chat Rooms
Discussion: Which chat room?
How to use the Problems Category (README before posting)
Pull Request Merge Days
Official Gitter Chat Rooms

I think we should support both Stack Overflow (mostly community supported), GitHub (intimate with the code, therefore good for bug reporting/referencing. People are use to and expecting to report bugs here and lookup solutions in GitHub Issues) and IRC (people are going to be looking for help in the IRC either way).

It's not an issue of trying to use a single tool to rule them all. This is simply the nature of the net in it's current state. All of the above provides value in their own ways if the community wants/can support it but the three I mentioned should be our official channels. Internally we can pipe GitHub Issues into another tool to help us better manage issues (zapier: github issue -> trello card for example).


@mikeumus good feedback, agreed. I've updated the guide to incorporate that smiley


@mikeumus we should probably mention our Trello board here too, as it is not mentioned anywhere else.

Update: is mentioned here:


We should also do up a guide for posting a support request - what information do they need to provide, etc. I thought we had one, but is just for providing support, not for posting a support request. And doesn't go into any detail about this either.

We should also consolidate all of our guides, as they are all over the place: