Design Meeting agenda for August 1, 2018

Right now we’re keeping things a bit more open. If you want to jump in and discuss things that you’re working on, or if this is your first time, please join us. Also, if you want to suggest a topic ahead of time feel free to add a comment here or mention in our Slack channel.

  • Triage: There are currently no Triage items in our Trello inbox.
  • Topic: We don’t currently have a topic of the week.
  • Open Floor: That means the meeting will basically be an open floor discussion. Bring your super awesome ideas and thoughts and we’ll jump into it together.



Design meeting notes for July 25, 2018

Howdy! A day late but just as interesting as what you’d have read yesterday. Btw, it’s always lovely to have folks jump in, the last few meetings have been tremendous with everyone joining and weighing in, makes for a healthy and lively discussion. And.. if you couldn’t make it, well.. that’s what this summary is for.

There was no triage or topic of the week, so we’ll move right past that.

A topic we did end up discussing was related to outreach:

Topic: Outreach

Led out by @boemedia, we chatted about plans for an online design conference. You can checkout the previous Trello discussion. Monique is working on a document to share with the team on what the conference could look like. Keep an eye out for that on Trello! Or here, we’ll probably share it here too.

So what’s the TL;DR? Well, that’s not quite decided but here’s a stab at it based on what we’ve discussed so far: we’ll have a remote based design conference, probably 1-2 days long, sometime in Spring of 2019. We’ll have speakers, and hopefully lots of awesome attendees! If you’re reading this you’re probably a perfect candidate for joining us.

In the discussion on Slack we also chatted about the potential of doing a small version of the conference this year, and then leading into the well planned out version in the Spring.

This led into a conversation about the types of folks who get involved in Core, the motivations, and how we all want to help.

A topic of the week suggestion came up: if you’re new to the design team, what guidelines could be followed to understand the users we’re designing for?

Open floor

Design tools and sharing designs

During the open floor portion of the meeting we started chatting about the collaboration process as designers within (yeah, that’s a real url, I just found out a few weeks ago!) design projects.

As designers we’re used to working with visual tools, Sketch or Figma being good examples. In fact, there’s some great pattern libraries for WordPress that we’ve been starting to use. The problem we run into is wanting visual version control. We’re not sure if we have a great answer yet, but it was really interesting to discuss. A few options were mentioned from a commercial standpoint.

We discussed a perfect project that could benefit from version control, and acknowledge that it’s hard to find the perfect balance between open source design team needs and industry best practices.

And some great news!

The oldest UI feedback tickets in Trac are now all in 2018! This does include tickets that were mentioned in Slack, which may not have had definitive progress. However, it’s exciting to see that we’re getting closer.


Design Meeting agenda for July 25, 2018

Design meeting agenda for Wednesday July 25 at 17.00. We’re trying a more basic and open agenda, so if there’s anything you want to discuss, please add it to the comments below, or mention it on our Slack channel.

Triage Inbox

See Inbox column on Trello board. New requests for design made via the Make blog, Slack, etc. will be transferred to Inbox each week, along with any new cards that need to be acknowledged.

  • nothing new this week

Topic of the Week

  • Outreach

Open Floor

  • what needs discussion?


Design meeting notes for July 18, 2018

In this new format we introduced a week ago, we kick off with inbox triage. You can read the full transcript of this meeting on our Slackchannel


Triage inbox

We have one incoming on the Trello Board: Create a style guide for future pages based on create a website and recent pages for example ‘Get WordPress’.

: It struck me with all the awesome work @cathibosco1 and others have been doing, we are creating a little design language.

This is really exciting but we haven’t documented it.

@hugobaeta  is willing to share his initial work on Sketch and @jayman is up for documenting this in the handbook, with @cathibosco and new contributor @ninjastar willing to help.

Topic of the week: onboarding

To recap, the idea of focusing on topics is we move projects on by focusing on something larger.

For a few weeks, a few people have been adding their feelings and feedback to a document. It’s not closing so don’t worry you can add even after this.

@karmatosed wants to take some time to discuss what is in the doc.

There are a lot of insights, and we agree on the fact that trac is a huge pain point for contributing. Besides, it’s compounded by fact that there are so many different outlets for discussion + work sharing (slack, trello, make, trac, etc.)

Improving the handbook

The discussion continues and we say improving documentation in the handbook would help.

Therefore we need people to help and review/audit the current content. If you’re in for doing so, you can do so in the Google Spreadsheet we created for this. If you have questions, ping @boemedia on Slack.

Next steps would be restructure, add new content and improve current information (not necessarily in that order).

Mentorship/buddy system

Besides good documentation we can refer to, the buddy system is still a strong wish, since the mentorship/mutual help is incredibly important. For starting, @karmatosed suggests putting up a mentor/mentee spreadsheet in Google and a handbook page to it for transparency. She also suggests some limits to the buddy system, that you can read about in our Slack meeting. There will be links to this sheet in the grey box as well in the front of the handbook.

Checking the buddy sheet will be part of the weekly design meeting agenda.

Open floor

Last five minutes are dedicated to the open floor. Anything people want to bring to attention? Anything someone need help on? What are people working on?

Cathi Bosco continues to work on the ‘Create a blog’ page and wants participants to understand she’s consolidating, since there are multiple cards on this topic on Trello. Therefore she mentions it again.

@karmatosed closes the meeting and @garusky thanks by saying these discussions about the onboarding gave him more context.

We’d like to thanks everyone participating in this lively meeting and hope to see you next week either at Monday’s ticket triage or at Wednesday’s weekly design chat.



Design Meeting agenda for July 18, 2018

The weekly design meeting is Wednesdays at 17.00 UTC (see it in your time). The chat will take place on our Slack channel. Everyone interested is welcome to join us.

Triage Inbox

See Inbox column on Trello board. New requests for design made via the Make blog, Slack, etc. should be transferred to Inbox each week, along with any new cards that need to be acknowledged.

Topic of the week: onboarding

The topic of the week will be something we’d like to spend some extra time on. This week, we’re focussing on onboarding

Open Floor

We’d like to give all contributors space to bring ideas and concepts to the table that are brand new, or that need discussion. Post your comment below, or bring your idea to the table during the meeting.


Design Meeting Notes for July 11, 2018

For all the details, see the conversation in Slack

This week we’re trying a more simplified agenda. This setup should allow us to have more space for everyone’s input. The aim is more discussion and interaction.

  1. Trello inbox
  2. Trello Calls for design: follow up on current projects
  3. Topic of the week
  4. Open floor

Trello Inbox triage

  • nothing new this week

Calls for Design: follow-ups

@estelaris is having a hard time uploading the infographic native files (.ai) to the training GitHub. She requests help after the meeting.

Topic if the Week

The topic of the week will be something we’d like to spend some extra time on. Nothing for today, but will be Onboarding next week

Open Floor

  • people were not sure what to bring up here, but note that it’s ok to bring ideas and concepts to the table that are brand new.
  • reminder about existing cards in Trello: if you see a project on the Trello board you’d like to work on but but status is unclear, check with the person on the card (either there or here in Slack.) They may not have updated it, or have been really busy and would love some help.
  • Filling the time with ticket triage was suggested, but not everyone wants to dive into triage and we already have a separate meeting for that.
  • Don’t forget the triage training for designers happening on Aug. 6, 2018


Design triage learning session on August 6th

During the weekly meeting a week ago, there was interest in having a video learning session using Zoom for design triage. This would be how to contribute using both Trac and also GitHub for Gutenberg. It is aimed at being for designers who want to learn more about what triage is and how to use Trac and GitHub, but anyone is welcome.

Some points suggested to cover are:

  • What the life is of a ticket or an issue.
  • What labelling means: specifically what ones designers need to know.
  • How trac works for tickets.
  • How GitHub works for Gutenberg issues.
  • How design triage sessions work.

The session with be on August 6th at 16:30 – 17:30 UTC. This will run instead of the usual triage session and be an hour long. Zoom will be used for the session over Slack, the idea being to ‘see’ and screen share.

A link will be given as a comment here and in #design before the start of the meeting. You will need to have the Zoom software installed to join.

In order to make this a session that everyone attending gains the most from I would love to know what you would like to see covered in this session. The session itself will have a format but questions along the way are most welcome.

X-post: Revised Gutenberg Landing Page

X-comment from Comment on Revised Gutenberg Landing Page

Design meeting notes for July 4, 2018

There were several items this week that were not on the original agenda, so see the below notes and refer back to Slack

Triage Inbox

Design for page “Create a Website” on on Design team

  • there will be 2 versions of create a website — one longer and more involved and the other with a lot less copy
  • cathibosco will be looking into this and how to reuse some of the ideas from her work for “Create a Blog

#43028: Remove numbers before month in dropdown, it makes user confused when drowdown is not opened

  • comment added: I can see how this could help for scanning and also accessibility. Are there any examples of how other sites do this we can lean on?

Calls for Design: follow-ups

Plugin icons are complete and @cathibosco is doing a review. Last steps:

    • gather everything up and thank the contributors.
    • Also where to send the final package? Ask in #meta Slack and update issue

Create a new trello card for the headers? Same way of working?

@estelaris wonders where to store the Training Team infographic native .ai file she recently finished

  • Should be stored in their GitHub repo. That makes the most sense in this context.

Items labeled ready to review in the meeting

  • Nothing this week


What will be the main focus for the next months for WordPress design?

  • @karmatosed: I wanted to suggest we start each month/ few months focusing on an aspect that needs work. My suggestion is we start with on-boarding. Suggested homework
    • give your feedback at in the shared doc
    • Think of an idea for an onboarding project and bring it to next week’s meeting.

Improve Trello board organization on Design team

  • Do we need this or can we close now? We can iterate later.
  • Some agree, but as part of our onboarding/documentation, the info on the Trello board it shouldn’t be confusing for new people
  • @boemedia: columns onboarding, handbook and outreach refer to the overview in the roadmap card in the team structure column

Triage participation

  • For those of you that haven’t been we do triage at 16:30 UTC in this very channel. We focus through issues for just 1/2hr but it’s a great toe dip into contributing.
  • @karmatosed is happy to train people up who feel ‘hmm leading triage is something I’d like to learn’.

Onboarding for tickets

  • Many people are confused or intimidated by tickets in Trac or GitHub, especially those who are not developers.
  • @karmatosed will be running a ‘non dev’ ticket onboarding session for trac and GitHub – covering Gutenberg also.
  • It will happen in the usual triage slot on Mon Aug 6, but note that it will be an hour long that day. Blog post announcement with details coming soon.


Design meeting agenda for July 4, 2018

The weekly design meeting is Wednesdays at 17.00 UTC (see it in your time). We’ll be discussing the topics below. If you have anything else to add, please comment below or mention it on our Slack channel.


Triage Inbox

See Inbox column on Trello boardNew requests for design made via the Make blog, Slack, etc. should be transferred to Inbox each week, along with any new cards that need to be acknowledged.

Calls for design: follow-ups

See Calls for Design column on Trello board. Anything to be archived? Follow up on in-progress cards, etc. Also, see #needs-design tickets from Trac.

Items labelled ready to review in the meeting

Filter Trello board for ‘meeting’ label which means that some work has gone into the card, and we have enough detail to make a decision on it.

  • Nothing this week


Design team related

  • What will be the main focus for the next months for WordPress design?

If time allows, follow-up on older cards

Filter Trello board for ‘needs discussion’ label. If none, triage any Trello cards that are not yet owned.