Meeting on March 27th

Attendees

• Michael
• Oliver
• Nuritzi
• Sri

Agenda

Discuss during meeting

• Announcements:
  • GUADEC 2019 call for bids (Nuritzi)
  • GNOME.Asia announcement (Nuritzi)
• US travel box (Nuritzi)

GitHub Issue https://gitlab.gnome.org/Community/Engagement/General/issues/67

• Engagement hackfest goals (Nuritzi)

  • Sri's mail: https://mail.gnome.org/archives/engagement-list/2018-March/msg00009.html

  • Notes from the last Hackfest :https://wiki.gnome.org/Hackfests/Marketing2013

• GNOME in Peru (Nuritzi)

Do during meeting

• GitLab clean up (Nuritzi)

Notes

Announcements

• GUADEC 2019 call for bids and GNOME Asia announcement

  • Proposed dates for GNOME Asia: 2018/8/11 ~ 2018/8/12 with potentially 2 - 3 days after for BoFs

  • try to get core contributors to join
• Can't figure out who has access to add new people to Wordpress. Sri, Nuritzi, Oliver do not. Maybe Tom does?

• GitLab partnership announcement

  • we need to start drafting this.
    • Ours should talk about:
      • How easy it is to start new projects
      • We have a great relationship with them and they listen to our user feedback
      • Maybe do a two part announcement, more formal part first then more of how we are using it

      • Series of tweets on highlighted projects that are on GitLab:

        • ask people to send responses to 3 questions: 1) link to your project on GitLab 2) how has it impacted your project so far? 3) what's your twitter handle so we can tag you, and are there any hashtags you want us to use?

    • GitLab's post will have:

      • In layman’s terms, what is GNOME? Can you share a bit of its history and contribution to the FOSS community?

      • What are you using GitLab for, and what prompted the move? What were you using before GitLab?

      • How have you chosen GitLab as the next tool for GNOME’s developer workflow? What were the important points for you in choosing the next tool?

      • What does the migration mean for the community? How has migrating to GitLab opened up communication and/or collaboration with other FOSS projects?

      • Why is free and open source software important?
      • How does someone start contributing to GNOME?
      • Any additional information you’d like to share

• ACTION:@Oliver to help draft the news items

• ACTION: @Sri find out who has permission for gnome.org to add people

• ACTION: Give @Michael access to the gnome.org wordpress site

• ACTION: Come up with a list of core contributors to invite to GNOME Asia

• ACTION: Create a ticket on GitLab for the featured projects tweet

US Travel Box

• Yes, accept them both. We could have a stable environment and a dev environment, or demo videos, etc.
• For the small box, just use a cardboard box

GNOME Peru

• FLISOL will be organized in late April in Peru and they have requested:

  • Speakers: Spanish speakers to talk about free software, Carlos Soriano, Florian Mueller, Carlos Granacho, Ismael Olea, Mario Sanchez
  • Establish a SWAG center in Peru
  • Need to get José Pedro Rodríguez Galarreta member signed up with all of the things
  • Michael to reach out to Jose Antonio Rey

Engagement Hackfest

• Possible topics:

Hackfest #1: GUADEC

• Newcomers: build on the newcomers stories
• Website: front page should be changed. Humanize it more. Could go through a whole overhaul. Want to optimize for new contributors.
  • Planet GNOME redesign too!

Hackfest #2: GNOME Asia or LAS GNOME

• Brand guidelines & design story:

• Updating marketing materials:
• Talking points about GNOME: how can people promote GNOME better?

Hackfest #3: maybe a virtual one? before the next release April or May 2018

• PR Issues and how we can avoid them: How can we communicate the changes that are happening and also get people to contribute ideas when the time is right / get people involved in the discussion at the right time

ACTION: @Nuritzi to plan and announce these

PR Issues

• Desktop Icons being removed
  • Issue: we talk about it in blogs but most people don't read blogs. Only enthusiasts read Planet GNOME. We don't have a way to communicate big changes to the users beforehand. We need to communicate, "here are the changes that are going to happen."
    • We can't tell people that we have been telling users for 8 years because a lot of people are just starting to use GNOME. We need to figure out how to deal with regressions.
• GNOME Shell leak