Commit 782ef2ba authored by John Coghlan's avatar John Coghlan 🏄
Browse files

Update #dev-advocacy-team Slack channel to #developer-advocacy in marketing handbook

parent 710950e6
Loading
Loading
Loading
Loading
+1 −1
Original line number Diff line number Diff line
@@ -285,7 +285,7 @@ Over the last few years, GitLab has continued to hold the [ISO/IEC 27001:2013](/

GitLab's [product mission](/handbook/product-development/how-we-work/product-development-flow/) is to consistently create products and experiences that users love and value. Responsible product development is integral to this mission.

We are committed to secure and ethical operations as an organization and, beyond that, strive to set an example by empowering our wider GitLab [community](/handbook/marketing/developer-relations/community-pathway/#how-community-fits-into-gitlabs-strategy) to build and work with the highest levels of security through our DevSecOps platform.
We are committed to secure and ethical operations as an organization and, beyond that, strive to set an example by empowering our wider GitLab [community](/handbook/marketing/developer-relations/) to build and work with the highest levels of security through our DevSecOps platform.

Artificial Intelligence (AI) marks a big industry shift that will make it easier to develop, secure and operate software. GitLab infuses AI throughout the software development lifecycle by incorporating it into our comprehensive enterprise DevSecOps platform. We lead with a customer-centric approach focused on privacy first, helping customers secure their intellectual property.

+1 −1
Original line number Diff line number Diff line
@@ -177,7 +177,7 @@ We use Slack internally as a communication tool. The Marketing channels are as f
- `cmo-staff`: (Private) CMO's private staff discussion room
- `#content`: Questions about blog posts, webcasts, the newsletter or other [marketing content](/handbook/marketing/brand-and-product-marketing/content/)? This is the place to ask.
- `#developer-relations`: A channel for the [developer relations](/handbook/marketing/developer-relations/) team to collaborate.
- `#dev-advocacy-team`: Discuss the latest tech in DevSecOps and Cloud-Native with the [Developer Advocacy](/handbook/marketing/developer-relations/developer-advocacy/) team. You can request speakers, customer consultancy and technical content collaboration and guidance.
- `#developer-advocacy`: Discuss the latest tech in DevSecOps and Cloud-Native with the [Developer Advocacy](/handbook/marketing/developer-relations/developer-advocacy/) team. You can request speakers, customer consultancy and technical content collaboration and guidance.
- `#digital-experience-team`: Channel for connecting with the [website development and design teams](/handbook/marketing/digital-experience/)
- `#digital-marketing`: Channel for all advertising, website analytic and general digital programs.
- `#external-comms`: To collaborate with our external PR (public relations) agency, discuss GitLab media mentions, and evaluate speaking/podcasting/commentary opportunities.
+1 −1
Original line number Diff line number Diff line
@@ -43,7 +43,7 @@ Both the legacy click-through demos and the new sim demos are available from the
- Open the demo executable
- If you have macOS Catalina - follow the steps in the next section, then come back here and continue
- Click Present Demo
- If you need help with the sim demo, contact TMM either by Slack channel #dev-advocacy-team or by opening a [Product and Solution Marketing Request issue](https://gitlab.com/gitlab-com/marketing/product-marketing/issues/new?issuable_template=A-SM-Support-Request).
- If you need help with the sim demo, contact Developer Advocacy either by Slack channel #developer-advocacy or by opening a [Product and Solution Marketing Request issue](https://gitlab.com/gitlab-com/marketing/product-marketing/issues/new?issuable_template=A-SM-Support-Request).

#### MacOS Catalina

+1 −1
Original line number Diff line number Diff line
@@ -40,7 +40,7 @@ Our operational strategy is [documented in our internal handbook](https://intern

Teams within Developer Relations are reachable in these Slack channels:

- [#dev-advocacy-team](https://gitlab.slack.com/archives/CMELFQS4B): the [Developer Advocate](/handbook/marketing/developer-relations/developer-advocacy/) team shares content updates, thought leadership & product ideas, and support community responses, CFPs, etc.
- [#developer-advocacy](https://gitlab.slack.com/archives/CMELFQS4B): the [Developer Advocate](/handbook/marketing/developer-relations/developer-advocacy/) team shares content updates, thought leadership & product ideas, and support community responses, CFPs, etc.
- [#developer-relations-programs](https://gitlab.slack.com/archives/C024ZBWK5KJ): for all inquiries regarding [Developer Relations Programs](/handbook/marketing/developer-relations/programs/)
  - [#developer-relations-engineering](https://gitlab.slack.com/archives/C02R0NE6P6C): for all inquiries regarding [Developer Relations Engineering](/handbook/marketing/developer-relations/engineering/)
  - [#developer-relations-community-contributions](https://gitlab.slack.com/archives/C02R0NE6P6C): for community contribution discussions
+2 −2
Original line number Diff line number Diff line
@@ -144,7 +144,7 @@ Given the Developer Advocate team's understanding of our community and broad kno

The Developer Advocate team plays a key role in supporting events. We work closely alongside [Corporate Event Marketing](/handbook/marketing/integrated-marketing/corporate-events/) to provide strategic content and assistance for both corporate and third-party sponsored events. This collaboration ensures the success and seamless execution of various gatherings. To learn more please refer to the [Events page](/handbook/marketing/developer-relations/events/).

We also help team members prepare for speaking opportunities at local tech events and meetups. If you'd like help preparing for such an event, please reach out to us in the [#dev-advocacy-team](https://app.slack.com/client/T02592416/CMELFQS4B) Slack channel or create an issue using the [Developer Advocate Request template](https://gitlab.com/gitlab-com/marketing/developer-relations/developer-advocacy/developer-advocacy-meta/-/issues/new?description_template=developer-advocate-request).
We also help team members prepare for speaking opportunities at local tech events and meetups. If you'd like help preparing for such an event, please reach out to us in the [#developer-advocacy](https://app.slack.com/client/T02592416/CMELFQS4B) Slack channel or create an issue using the [Developer Advocate Request template](https://gitlab.com/gitlab-com/marketing/developer-relations/developer-advocacy/developer-advocacy-meta/-/issues/new?description_template=developer-advocate-request).

#### Release Advocacy

@@ -166,7 +166,7 @@ Our team maintains projects to provide GitLab use cases for content creation (de

### Find us on Slack

GitLab team members can also reach us at any time on the [#dev-advocacy-team](https://app.slack.com/client/T02592416/CMELFQS4B) Slack channel where we share updates, ideas, and thoughts with each other and the wider team.
GitLab team members can also reach us at any time on the [#developer-advocacy](https://app.slack.com/client/T02592416/CMELFQS4B) Slack channel where we share updates, ideas, and thoughts with each other and the wider team.

We use a dedicated channel, [#dev-advocacy-hangout](https://gitlab.enterprise.slack.com/archives/C01C018V7V3), for recurring Geekbot standups and social conversations.

Loading