Skip to content

Dev Advocacy content: Update maintained talks (Duo Agent Platform use cases, OSS AI, CI/AI/Embedded)

Michael Friedrichrequested to merge
dev-adv-content-maintained-talks-update into main

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

Please add the details saying why, not just what in this section. Example: We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.

This change updates a documentation page that tracks presentation materials used by the developer advocacy team. The main updates include:

  • Removed the word "golden" from the description of talk slide decks and added instructions for team members to reach out via Slack for questions
  • Reorganized the table of presentations by moving older content to a new "Archive" section
  • Added three new presentation entries with updated information, including links to recordings, slides, and demo materials
  • Updated the table header from "Last updated" to "Updated" for consistency
  • Enhanced the resource links and descriptions for several presentations, particularly those focused on AI and development workflows

The changes make the documentation more current and better organized, separating active presentations from archived ones while providing clearer guidance on how team members can get help with the materials.

DAuthor and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct
    • The when to get approval handbook section explains when DRI approval is required
    • The who can approve handbook section explains how to identify the DRI
    • If the MR does not require DRI approval, consider asking someone on your team, such as your manager.
    • The approver may merge the MR. If they approve but don't merge, you can merge.
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Division: If the update affects your division, share the MR in your division Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR

Commits

  • Dev Advocacy content: Update maintained talks

Merge request reports