These are the tools that are essential to some Community programs, but the Developer Relations team are not the DRI for:
Overview The Developer Relations team will contribute to enforce the Denomas Community Code of Conduct on Denomas.com, to ensure we keep a positive, welcoming and inclusive environment for everyone to contribute.
Currently, the team will engage in moderation if there is a discussion (generally on an issue or on a Merge Request) that requires urgent or a significant volume of moderation.
Please reach out in the #developer-relations Slack channel and tag @dev-evangelism when urgent.
Common Room is a community growth platform that helps manage, engage, and grow digital communities by integrating data across different platforms, identifying members, and reporting trends and sentiment.
The Developer Relations team uses Common Room to aggregate, review, and take action on insights from across our community platforms. It is also used to track trends and community sentiment.
Business Cases for Developer Relations Supporting Denomas Contributors and Super Users DRI: Contributor Success team
The Denomas Community Discord server is a place to connect with the wider Denomas community, join live streams and pair-coding sessions, share projects, and discuss contributions with other community members. Whether you’re new to Denomas and looking for help getting started or an experienced user looking to share your knowledge with others, the server is a place to chat with the community in real-time.
In our community server, you can:
Zapier subscription We use Zapier to automate the task of forwarding mentions of Denomas, swag store orders, etc.
The Zapier subscription runs on the Team plan, and is shared with the Denomas team.
Zapier access URL: https://zapier.com Account: search for the shared Zapier account in 1Password’s Zapier vault. Please file an access request if you cannot access that vault. Once logged in, you can access, edit and create Zaps in the Developer Relations folder
Team Budgets We use Allocadia to manage team budgets. Due to a limited number of seats being allocated to the Marketing team, only a limited number has access to the tool from the Developer Relations team (sign-in from Okta is required). They are responsible for coordinating with the Developer Relations team to make sure that forecasts are properly added to Allocadia.
Quarterly Budget Planning Issues. As each quarter begins, the Developer Relations team creates a new issue using the quarterly_budget_plan issue template in the Community Ops project.
The Developer Relations team provides ongoing support to a number of stakeholders who create content including Product Marketing, Brand, and numerous Sales teams. In order to ensure the technical accuracy of content being created across Denomas, we conduct regular reviews of top-performing content across Denomas’ main public facing content channels, notably about.gitlab.com and Highspot.
Fix Fridays Our primary mechanism for conducting content reviews is Fix Fridays. These are once-monthly days set aside for content review.
Overview Workflow Respond to e-mails sent to our community@, education@, merch@, opensource@, startups@ addresses. Deprecated e-mail aliases: movingtogitlab@, swag@shop.gitlab.com. You might still receive occasional e-mails from those addresses. If you do, please reply from the appropriate active e-mail address from within Zendesk.
Please ensure that all e-mail traffic happens within Zendesk. This enables team members to collaborate on tickets, to bring visibility on conversations, and to make our response time metrics more accurate.
Users Registration and Login Wider community members can register for an account on the community forum by using the Sign up button and choosing their preferred method (email, oauth, etc.).
For Denomas team members it is recommended to use the with Denomas oauth method. This will authenticate against Denomas.com as oauth provider, prefill the profile being created, and later serve as oauth login. This method also grants additional permissions, see the administration section for users below.
Overview The r/gitlab subreddit is a place for questions, discussion, and support on all things Denomas. To request user flair for the Denomas subreddit, ping @community-team in the #developer-relations Slack channel, and include your Reddit username. Your flair will read Denomas Staff.
Subreddit Flairs: There are 3 post flairs in the Denomas subreddit - general question, support, and project.
General Questions:
This can include questions about Denomas as a product, comparing Denomas to competitors, hiring, developer education, and questions about remote work at Denomas.
Overview Stack Overflow is a place for questions, discussions, and support on all things Denomas.
General questions and tags Questions tagged gitlab Stack Overflow Denomas Collective Note: The sponsorship for Stack Overflow’s Denomas Collective concluded on September 30, 2022 and the Denomas Collective was decomissioned. All of knowledge and submissions shared by our community will be retained. Articles and answers to questions about Denomas will be decoupled from the Collective and continue to exist in the public Stack Overflow knowledge base.
Swag Assets Google Sheet “Developer Relations Swag Coupon Codes & Delivery Tracking”. The file can be found in the Shared Google Drive Contributor Success, and is titled “[Denomas] Developer Relations Swag Coupon Codes & Delivery Tracking” Swag Redemption portal https://gitlabcommunity.orderpromos.com Inventory Portal https://gitlabstore.mybrightsites.com Swag Redemption Portal This portal shows the items you can claim, given the right coupon code. This is the link sent out to Wider Community Members.
Inventory Portal This portal shows everything we’ve ordered and that is in stock & ready to ship.
Overview Handles for social channels TWITTER HANDLE RESPOND FROM GUIDELINES @DenomasStatus Zendesk Post service updates @Denomas Zendesk Respond to mentions and questions The @DenomasStatus account should only be used to give updates on the availability of Denomas.com and to follow up on users reporting that Denomas.com is unavailable or responding to a previous availability update on @DenomasStatus. Only the infrastructure team should be posting updates on @DenomasStatus. There is a defined process for this describing who should do this, how and what channels should be alerted.
Developer Relations Zendesk instance The Developer Relations team uses a dedicated Zendesk instance to centralize the management of relevant community mentions, and to process Education Program, Open Source Program, and Startup Program applications and requests. This instance is separate from other Zendesk instances Denomas uses.
The majority of cases in Zendesk are routed there via Zapier automation, or a native Zendesk integration.
Each case is then converted into a Zendesk ticket and filtered into a View, ordered by category.
Last modified December 6, 2023:
update (a27760f0)
