Engagement Team meeting Wednesday 22 April 2026

Teams Engagement
1

Attendees

  • Maria
  • Victoria
  • Allan
  • Hari Rana
  • Proman

Agenda

  • Kick-off discussion: what do we want to talk about?
  • Potential topics:
    • Schedule for future calls
    • Goals for social media
    • Posting guidelines
      • What should we post
      • How should we write it (tone, message etc things like that)
      • Should Mastodon and Bluesky have different tone and overall content?
    • Potentially try to look/think about looking for more people to draft content
    • Who are the editors and how do we decide who they should be?
    • Where should we post our assets to? Gitlab, Nextcloud, something else?

Notes

  • Future calls
    • Let’s start with every other week
    • Allan will run a poll to decide the day and time
  • Social media posting process
    • Mixpost is used for Bluesky and Mastodon
      • Admins must approve posts. Current admins are: Paul, Allan, Maria, Lorenz, Sri
        • In practice Maria is the one doing the approvals. Sri has done a little.
          • Maria checks Mixpost daily. She also reviews on request in #engagement:gnome.org
      • We need more approvers
      • What are the criteria for approvers?
        • Must be a regular contributor
        • Must work with the rest of the team
        • Must demonstrate a history of good judgement
        • Must have done effective reviews
      • Maybe downgrade Lorenz to a regular member for now?
    • Other platforms we manage: LinkedIn, Youtube, Reddit (?)
      • Ideally the editorial team would approve these too
  • Assets
    • Photos from events 2011-19
    • Do we have 2022 anywhere?
    • Flickr contains our official GUADEC photos from 2023-25
      • Archiving these on Nextcloud could be a first step
      • Next step is to find someone to select the best ones before uploading to Gitlab
    • What about GNOME.Asia?
    • ACTION: Allan to ask Kristi about missing photos
    • ACTION: create a ticket to discuss what types of assets we think we need for social media etc
    • ACTION: document the current assets in the README for now.
  • Where to keep our docs?
    • Things we need to document:
      • Who has access to which accounts
      • Process for becoming an approver
      • Posting guidelines
    • Options include: a subpage in the handbook, a GitLab wiki, Markdown files in a GitLab repo
    • ACTION: Allan to open a ticket to get opinions