Skip to content

Refine speaking resources handbook with required/optional steps

Michael Friedrich requested to merge handbook-speaking-resources-refine-steps into master

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.

I had a coffee chat with @alexander-sosna yesterday, and he pointed out some steps that seem to be required, but are optional (e.g. the becoming a speaker section and the Google form to chat about abstract ideas). This seems to lead to confusion when desiring to speak at events. It is also not clear who should create the CFP issue, where I encouraged to create one with https://gitlab.com/gitlab-com/marketing/corporate_marketing/corporate-marketing/-/issues/8383

This MR improves the speaking resources handbook in the following way:

  1. Add notes markers into the handbook sections to clarify which steps are required, and which are optional.
  2. Rewrite the CFP Submission chapter to force creating the CFP issue, and use it as the SSoT in the process.
  3. Add the CFP issue creation as required step into the Process section. Additionally, encourage to log manager approval into the same issue.
  4. Emphasize on the brand assets: First Google slides, then brand and design handbook. Ensure that team members review the brand guidelines.
  5. Fix the CFP-Meta issue template URL. Somehow it is case sensitive now and pointed to CFP-meta.
  6. Review all URLs and ensure they link to GitLab SSoTs when possible (marketing event calendar, speaking blog, etc.)

The MR does not change the event requirements section which required approval from Ashley last year.

Author 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 Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • 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
    • 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

Merge request reports