Design meeting summary for Wednesday May 23, 2018

Howdy! Following are a few of the takeaways from our meeting today, based on the previous agenda.

  1. Simpler agenda – The agenda has been streamlined. This is based on recent feedback, and more would be welcome as we try to hit the right balance of making things clear and getting things done.
  2. Defining design – We’re recognizing a trend in a lot of the tickets we’re trying to support on and tackle. We often run across problems that have been called out, but aren’t easily explained. As a design team we can start to won some of these tickets by clearly articulating (and encouraging others outside of the design team to do the same) the problem in a visual way. The ideal is that as someone new to the ticket (or coming back for the 10th time in as many years) I can get the basic gist of the ticket in a 10 second glance. Sketches, videos, screenshots, very simple bulleted lists, these are some of the ways to tackle this.

Calls for design

  1. Future private posts listed as already published with future date specified – We chatted about this issue and recognized that we couldn’t easily explain what was going on (without taking the time to dig in deep). A comment showing the current state of the plugin will go a long way towards helping us to figure out where to take it next. You can follow the conversation we had on Slack.
  2. Tweaks to menu setup page – Similar to the above ticket, we need to make sure we understand the current state, and then propose a better future state. Putting out a call for anyone who is interested in doing that. If it’s your first time please reach out to anyone on the design team and we’ll be happy to guide through that process. Honestly it’s a ton of fun! There are many examples where someone from the design team was able to do that. You can also follow the Slack conversation we had today.
  3. Error 500 when a user has too many sites – Could use some design team love. If anyone can volunteer to make a tl;dr video clip of the problem it might move the conversation forward. View summary.

Housekeeping

  1. Onboarding new contributors – You can follow the Slack conversation. We discussed the best way to onboard new folks, and had some suggestions on how a bot could be used to make that process better (without being obtrusive).

#meeting-notes

Design meeting agenda for Wednesday May 23, 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 you want to discuss, please add it to the comments of this post, 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. 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 labeled 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

Housekeeping

Design team related

  • Onboarding new contributors: After discussion last week, a weekly post by a team rep seems a good balance between an automated Slackbot (which proved a challenge to set up the way we wanted) and individual outreach to every person who joins. See an example. Question: how to divide the work or schedule this so we don’t forget?

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.

#meeting-agenda

Design meeting notes for Wednesday May 16, 2018

Full transcription of this week’s meeting can be found on Slack, or follow the anchor links in the topics below for a detailed conversation.

Housekeeping

Design team related

 

 

  • New volunteer orientation
    We discuss this as a basis for onboarding new contributors. As we love the idea of having an onboarding once a month, we try to be careful planning another meeting. Pinging every new person that signs up for the design channel may be too intrusive. As this is a challenge, we eventually came up with a proactive message, like every few days on the Slack design channel, saying: “Are you looking for a way to contribute? Ping x, x or x and we’ll help you getting started”

 

 

Triage Inbox

See Inbox column on Trello board. Calls 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.

 

  • What belongs in the Design Resources column?
    We’re talking the Trello Column here. Still finding a way to organise our resources while we’re auditing our handbook. @MelChoyce suggests to put WordPress related stuff in the handbook and stuff that supports other tasks in Trello. We agreed on extending the handbook with an Invision page, since we have a sponsored InVision account. We can explain on that page how to request access, how it works and what good add ons are.

 

 

 

Calls for design

See Calls for Design column on Trello board. Anything to be archived? Follow up on in-progress cards, etc.

 

 

  • @Joyously points out that the PHP version support page still needs input.
    After the meeting, @boemedia added the note that designers are working on a new mockup, since the current one was outdated. As soon as this new design is ready, it will be posted on the Trello board for feedback.

Thanks again to all volunteers who took the time to attend this week, your input is very valuable.

 

#meeting-notes

X-post: Design team monthly recap April, 2018

X-comment from +make.wordpress.org/updates: Comment on Design team monthly recap April, 2018

Design meeting agenda for Wednesday May 16, 2018

The weekly design meeting has moved to Wednesday at 17.00 UTC (see it in your time). We’ll be discussing the topics below. If you have anything you want to discuss, please add it to the comments of this post, or mention it on our Slack channel.

Housekeeping

Design team related

Triage Inbox

See Inbox column on Trello board. Calls 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

See Calls for Design column on Trello board. Anything to be archived? Follow up on in-progress cards, etc.

Items labeled ready to be a meeting topic

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 today

Requests to review existing tickets

Typically from Trac or GitHub

  • nothing today

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.

Please join us or leave a comment below this agenda if you have any design related questions.

#meeting-agenda

Design meeting notes for Wednesday May 9, 2018

From this week on, the weekly design meetings occur on Wednesday 17.00 UTC. You can find this week’s design meeting transcript here on Slack, or jump to different topic discussions by using the links in the document following.

Housekeeping

Triage Inbox

Calls for design

  • PHP Meeting is revived
    It was a bit confusing, since this ticket asked for both design feedback on the widget that will appear in the WP-admin dashboard, as well as the page the widget leads to.
    From @flixos90: I’m not sure if this fits in your meeting today, so please let me or the #core-php channel know when there’s time for it. We’re also around to help with contextual questions of course. For feedback, please comment on the meta ticket for the page https://meta.trac.wordpress.org/ticket/3609
    We discussed this call for design in today’s meeting, but it still needs some clarification: has core given feedback on the original design of February 2? Design questions are: What color is good? What icons to use? What illustrations could help?
    Should it match the rest of wp?
    Find the conversation on Slack: https://wordpress.slack.com/archives/C02S78ZAL/p1525887844000224

Thanks everyone for lively conversations again! Hope to see you all again at next week’s meeting.

#meeting-notes

Design meeting agenda for Wednesday May 9, 2018

The weekly design meeting has moved to Wednesday at 17.00 UTC (see it in your time). We’ll be discussing the topics below. If you have anything you want to discuss, please add it to the comments of this post, or mention it on our Slack channel.

Housekeeping

Design team related

Triage Inbox

See Inbox column on Trello board. Calls 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

See Calls for Design column on Trello board. Anything to be archived? Follow up on in-progress cards, etc.

  • Several are in-progress. Any need for discussion?
  • PHP Meeting is revived

Items labeled ready to be a meeting topic

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 today

Requests to review existing tickets

Typically from Trac or GitHub

  • from @flixos90: I’m not sure if this fits in your meeting today, so please let me or the #core-php channel know when there’s time for it. We’re also around to help with contextual questions of course. For feedback, please comment on the meta ticket for the page https://meta.trac.wordpress.org/ticket/3609

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.

#meeting-agenda

Design meeting summary for Thursday May 3, 2018

You can find this week’s design meeting transcription here on Slack.

Housekeeping

  • New meeting time – Wed. 17:00 UTC! 

Triage Inbox

  • Nothing new

Calls for Design

  • Copy for creating a blog
  • Document experience of contributing to design team. Love this!
  • PHP meeting – appears that things have stalled on moving this ticket forward, so we archived it for now.
  • Plugin headers and icons – was mentioned as a need, and then we had a great discussion that pulled into the importance of jumping back into Trello cards to self update them to keep information flowing. Over communicating is a good thing in this case.
  • WordCamp design templates – progress has slowed down on this ticket, and it was discussed to followup again in order to move things forward.

Ready to be a meeting topic

  • Nope, nothing new

Requests to review existing tickets

  • Not really anything new
  • We did discuss adding a Contributor tab to the about page (thanks for sharing @cathibosco1)

If time allows, follow-up on older cards

Hey feel free to jump on in. Would love to have you join our next meeting, and thank you to all the awesome folks making things happen.

#meeting-notes

Design meeting agenda for Thursday May 3, 2018

The weekly design meeting is Thursday at 17.00 UTC (see it in your time). We’ll be discussing the topics below. If you have anything you want to discuss, please add it to the comments of this post, or mention it on our Slack channel.

Housekeeping

Design team related

  • Nothing today

Triage Inbox

See Inbox column on Trello board. Calls 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.

  • Nothing today

Calls for design

See Calls for Design column on Trello board. Anything to be archived? Follow up on in-progress cards, etc.

  • Any calls-for-design need attention?

Items labeled ready to be a meeting topic

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 today

Requests to review existing tickets

Typically from Trac or GitHub

  • Nothing today

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.

#meeting-agenda

Design meeting notes for Thursday April 26, 2018

You can find this weeks design meeting transcription here on Slack, or jump to different topic discussions by using the links in the document following.

Housekeeping

Design team related

  • On our about page for make.wordpress.org it says “pixel perfect designer.” Can we update that as it feels a little outdated?
    We discussed that this term is not very inclusive, and that it would be nice if we could convey “design” a little more broadly, since, besides the visual aspect, there’s also UX. After a short discussion, we decided on just ‘designer’ would do for now. New text is available on make.wordpress.org
  • What belongs in the Design Resources column of Trello?
    After an extensive discussion last week, we felt the need to give this a bit more attention. Initially we thought Trello would be a good place to store assets, but we revisited that idea. We talked about integrating Github, or go back to basis and use the handbook for both assets and resources. @hugobaeta joined the conversation and had some good ideas: If they are static assets – like logos, sketch pattern libraries, etc – they could live in handbook. If it’s a project-based asset – like a .org page redesign, etc – they could be in a repo.
    The team thinks it’s worth exploring a design Github repo under WordPress. @karmatosed will investigate how we can get one.
    We also tried to find out if we could extend the file types we can upload to our handbook, keeping version control and file management in mind. *Incoming:zip and psd were already possible. Added ai and sketch, and svg only for admins.” This means we can add assets to the handbook and keep that as a first to go for designers who want to contribute to the project.

Triage Inbox

See Inbox column on Trello board. Calls 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.

  • Nothing today

Calls for design

See Calls for Design column on Trello board. Anything to be archived? Follow up on in-progress cards, etc.

  • There’s an in-progress one about Design templates related to the Design Resourced discussion above

Items labeled ready to be a meeting topic

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 today

Requests to review existing tickets

Typically from Trac or GitHub

  • Nothing today

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.

  • No time left

Thanks all for attending this weeks meeting and let’s continue on improving our structure and documentation for future reference. It’s not easy, but worth spending time on!

#meeting-summary, #meeting-notes