Below are the chat channels we manage and the intended use/etiquette around each. Note that this is by no means a complete list. If you feel there is a channel that is missing here, please let us know.
We are encouraging a community/peer-to-peer support model where community members are expected to participate by sharing their experience and advice, and responding to problems and questions as they are able.
While the platform team will attempt to triage, and moderate discussions, the success and sustainability of the model depends to a large degree on participation from the broader community.
For more information about the the expectations involved with the community support model, please see (insert link to Onboarding Outcomes here)
Note: Our current chat space is on Rocket.Chat at https://chat.pathfinder.gov.bc.ca/
If you're not sure about the purpose of a channel (aka if you're not sure if that channel is the right place to post your question), check the channel description.
If you are responding directly to someone else, use the reply feature (click the little voice bubble next to the post to which you are replying). This helps to keep the context of your posts clear to everyone in the channel and will notify the person you're responding to.
#devops-sos is where you should post when you have one of the issues below:
- a production problem with an OpenShift-hosted app that you can't solve without external assistance from the DevOps platform team or AdvSol.
- an issue with an OpenShift hosted project support tool that has caused a work stoppage that cannot be worked around
Note that normal BC Gov support channels (77000, IMB help desks, etc.) should be used for shared infrastructure such as reverse proxies, SiteMinder, firewall rules, etc.
This channel will be monitored by the platform team and AdvSol during business hours.
#devops-how-to is for asking non-urgent questions about approaches to solving problems, evaluating technical options, getting feedback on different approaches, familiarity with platform features or tools, resources/examples, etc.
#Geo Spatial Web Services How-to, this is the channel you can inquiry how to consume Province provided spatial webservices such as WMS, WFS, ArcGIS REST services with your web applications.
#devops-alerts is where the operations team will provide notices and progress notifications of upcoming or ongoing maintenance activities or incidents.
#labops-alerts is a channel for the lab-ops team to post notifications to other lab residents and the community at large. Notifications about community events can be found here.
Team CoCo is the Common Components team - they can be found here if you're hoping to find a component that you think might already exist, or if you have a component that you want to share with the community.
There are a number of channels dedicated to community support and discussions about the use and development of specific tools. These channels include: (note that this is not a complete list)
- #sso (this is for keycloak)
Anything that might be of interest to the community.
Learn about job opportunities in and around the BC Gov DevOps community.
If someone (or a group of someones!) deserve your public thanks, this is the place to do it.
Jokes (SFW only pls), links, and
cat pug pictures. 'Nuff said.
Teams are always welcome to make new channels for their own use! When doing so, consider the following conventions for creating and naming your channel:
- Is this additional channel necessary? Discussions are a great way to provide a dedicated space for taking about specific topics, especially if the topic will only be relevant for a finite amount of time!
- Is this channel team-specific? If you're interested in making a channel for the use of the wider community, please give our LabOps and/or Platform Services teams a shout about it. This is so we can properly support this community-wide service!
- Is your new channel's name clear? Team-specific channels should include the team's name (or shortname). A new user should be able to tell at-a-glance what this channel is about, even if they're not a member of your team. Consider using a format like this one:
As always, our community is more than welcome to fork this doc and include some recommendations of their own. We'd be particularly interested in hearing about how your team has chosen to organize their channels, so new teams can learn what has worked in the past!