Design meeting notes Feb. 15

This is the design meeting summary of February 15, 2018 (Slack log)

Housekeeping

  • @Karmatosed shared a new proposal for an onboarding team. If anyone has time to contribute there, please do.
  • We also discussed better ways to welcome new design people to this channel
    • team reps, come up with a standard answer when we see new people in the channel.@Boemedia suggested for instance, asking people to fill out their expertise in our google drive overview. And just let them know if they have any questions, they can address them here? Also point them to the meeting times?
    • Automatic Slackbot could be set up too. Usually something like:
      > Welcome to [Slack]! Here are some handy links to get started in our community: [Links]. If you have any questions, please ping [people]!
    • an automated welcome is worth setting up because it’s immediate, but team reps should follow up whenever possible too.
    • @mizejewski will draft a content and bring back to the group to finalize and be turned into a Slackbot

Calls for Design

  • No new calls, but Marketing team Jargon Glossary still needs a featured image, as well as a nicely formatted PDF. If you’re interested, comment on the card.

Items labeled ready for meeting discussion

Requests to review existing tickets

  • #41143 Theme/plugin editing by @xkon
    @melchoyce will leave a comment that the solution proposed looks good.

Triage items from Inbox

  • nothing this week

If time allows

Revisited Plan a “new contributors buddy system” 

  • There’s a central initiative to create a new central onboarding team with reps from various teams. Let’s see how this is executed and maybe archive this card when successful?

Revisited Consider planning a “WordCamp for Designers”

  • people like the cross-pollination of the big WordCamps, but a smaller, more specialized even could be great too
  • @Boemedia suggested the possibility of an online Design WordCamp, the way WordCampus does it?
  • We could think about setting up local/online events small scale and maybe (e.g. Global Translation Day) organized on the same day under one flag, to benefit from presenting it as a global event. Action for all: talk to local designers in own communities and see how we can initiate this on a small scale?

#meeting-notes

Design meeting agenda for Februari 15

Hello everyone! Today we’re having our weekly meeting at 18.00 UTC. We will discuss the topics below. If you have any other design related questions, please feel free to join us.

Housekeeping

Design team related

Calls for design

See column in Trello roadmap. Requests via the Make blog, Slack, etc. 

Items labelled ready for meeting discussion

Filter Trello roadmap for ‘meeting’ label

Requests to review existing tickets

#41143 Theme/plugin editing by @xkon

Triage items from Inbox

See Inbox column in Trello roadmap.

If time allows

See Trello roadmap.

  • Triage other columns or follow-up on older cards

 

Feel free to leave a comment and we can discuss anything people want.

See you in the #design channel in Slack

#meeting-agenda

Design meeting notes Feb 8

This is the design meeting summary of February 8. 2018 (Slack log)

We pushed Housekeeping to the end this week, since @Karmatosed had an item but knew she’d be late.

Calls for Design

Marketing team Jargon Glossary needs a featured image, as well as a nicely formatted PDF. No one was able to jump on this immediately, but @Boemedia may revisit next week.

Items labeled ready for meeting discussion

Illustrations for wordpress.org requested by @cathibosco. Lots of feedback on increasing inclusiveness of illustrations and also about design specs.

Requests to review existing tickets

@Rileybrook requested feedback on Gutenberg issue Language around transformations inconsistent #4416. Consensus from roundtable was Transform into is more descriptive and easier to translate to other languages, as opposed to Turn into.

Triage items from Inbox

nothing this week

Housekeeping

@Karmatosed shared the fact that the Design Team may soon have access to and InVision account. A shared tool like that will really help, so she’ll keep us posted on progress.

Also, the process for asking for feedback on an existing issue or ticket was clarified on Trello by @Mizejewski.

If time allows

We looked at Suggestions for Design Resources page on the Handbook. We talked about how to periodically review this for updates, as well as how to make it more usable/scannable. For example, links to WPTV with a short description rather than embedding videos.  Discussion will continue in the card, and we will review outcomes next week.

#meeting-notes

Design meeting agenda for Februari 8

Housekeeping

Design team related

Calls for design

See column in Trello roadmap. Requests via the Make blog, Slack, etc. 

Items labelled ready for meeting discussion

Filter Trello roadmap for ‘meeting’ label

Requests to review existing tickets

Typically from Trac

Triage items from Inbox

See Inbox column in Trello roadmap.

If time allows

See Trello roadmap.

  • Triage other columns or follow-up on older cards

 

Feel free to leave a comment and we can discuss anything people want.

See you in the #design channel in Slack

#meeting-agenda

Design meeting summary February 1

Housekeeping

This is the design meeting summary of February 1. 2018 (Slack log)

Team Reps were updated to cycle in some fresh faces.

Calls for design

Nothing discussed during the meeting, but see the related Trello column for the latest progress on recent calls. If you see something you want to help with, leave a comment.

Items labeled ready for meeting discussion

The card on improving the copy and layout of the grey box at the top of all Make/Design pages was archived as done.

We also discussed edits to clarify and finalize the How To Use This Board card and the labels. The Start Here column is now complete.

Requests to review existing tickets

  • ticket #40985 @melchoyce will comment: ask for a patch and some testing — also maybe create a new ticket for the help section
  • ticket #42778 @Boemedia commented: The design team discussed the solution given in @chetan200891 ‘s video and we all agreed to this being a really good solution. Looking forward to seeing the patch implemented!
  • ticket #596 @cathibosco commented: a lot of interest in completing the headers and getting designers to adopt a plug-in at an upcoming contributor day as well as online here too. The specs for the graphics can be found here: https://developer.wordpress.org/plugins/wordpress-org/plugin-assets/

Triage items from Inbox

No time today, but post-meeting @Boemedia and @Mizejewski discussed and moved the weekly meetings skeleton to the Team Structure column and created a Templates and style guides column for items like the featured image template the made by @Dotrex.

#meeting-notes

New design team reps

Please join me in congratulating @boemedia, @joshuawold and @mizejewski on becoming team reps for design. You all have been doing an awesome job focusing and improving the communication of the design team. Thank you and let’s join in welcoming them officially as team reps!

Design meeting agenda for February 1

Housekeeping

Design team related

  1. Team Reps

Calls for design

See column in Trello roadmap. Requests via the Make blog, Slack, etc. should be transferred there each week.

Items labelled ready for meeting discussion

Filter Trello roadmap for ‘meeting’ label

  1. If all is well, this card can be archived as complete: Improve content of Grey Box
  2. Let’s finalize what to share about how to use the Design team roadmap

Requests to review existing tickets

Typically from Trac

  1. @afercia requests review of a11y ticket #40985
  2. @afercia requests review of a11y ticket #42778
  3. @melchoyce requests review of #596

Triage items from Inbox

See Inbox column in Trello roadmap.

  1. What’s the best place to store useful design assets and reference materials?

If time allows

See Trello roadmap.

  • Triage other columns or follow-up on older cards

#meeting-agenda

Design meeting summary for January 25

This is the design meeting summary of January 25, 2018. (Slack log)

Present at the meeting were: @Karmatosed (lead), @Boemedia, @Mizejewski, @Dotrex, @Rileybrook, @melchoyce, @cathibosco, @mapk, @joyously, @joshuawold

We had a good meeting, getting more and more structured with the new and growing group of involved design volunteers that attend the meetings, so yay for us!

Housekeeping

  • Please note that ticket triage on Monday now starts at 17:30 UTC!
  • As the meeting was a little chaotic this time, we decided on creating a skeleton structure for future meetings to give more direction during meetings.Weekly recurring meeting topics are:
    • Housekeeping: any information or things to share we all need to know.
      • Sub 1
      • Sub 2
    • Calls for design
      • Sub 1
      • Sub 2
    • Specific meeting agenda items from comments and Trello board ‘meeting’ label (only this one)
      • Sub 1
      • Sub 2
    • Tickets that need eyeballs
      • Sub 1
      • Sub 2
    • Trello triage of inbox
    • (If time )Trello triage of older columns, this will happen as we will have no other topic

Now the structure is basically set, meetings can be run by anyone. Call for meeting leads and note takers, whoever is interested, please step up!
That being said, @Rileybrook might be interested in helping run once we have a solid structure/process in place. Also, @Mizejewski offers to join the note-taking team, woohoo!

Calls for design

The Marketing team requested another featured image and a design for a glossary page. These are now posted on the Trello board. Feel free to step up and make a design for these calls.

Trello Meeting topics

A new content suggestion for the Grey BoxTM was done by Michele first needs pre-meeting discussion on Trello before presenting it in the Meeting. So go ahead and ventilate your opinion on Trello!
It was decided that Trello cards are only labelled meeting topic after a-sync pre-discussion was done on Trello.

Tickets that need eyeballs

Joyously again requests eyes on the ticket for search, sorting and filtering in the plugin directory. There’s no filtering in the plugin directory now, so ux-feedback for that is requested: where should it go, what should be in it. If this is a topic that suits you, please feel free to pick up the glove.

Finally we discuss a call for a UX designer for a page for collecting data of compatibility of plugins with Gutenberg by Daniel Bachhuber. This raises a lot of questions within the design team. For now, @Boemedia is the first designer contact for Daniel Bachhuber. Back up discussion partners are Joshua Wold and Jayman Pandya.

#meeting-notes

This week’s design meeting agenda for January, 25

This week’s #design meeting is happening Thursday, January 25 18:00 UTC.

This weeks agenda is:

Feel free to leave a comment and we can discuss anything people want.

See you in the #design channel in Slack

#meeting-agenda

Design meeting summary January 18

TL;DR – We just had a really productive meeting where we touched on design needs, adding some structure to the work the design team is doing, as well as reporting on all the awesome stuff getting done. Interested in helping? There’s something here for you!

Below are the exciting things we covered in the meeting!

Calls for design

We’re looking for help, if you think you’re a match please reach out! If you have a call for design yourself you can add it as a comment on this post or join the weekly #design meeting and we can discuss after covering other items.

  • Design a featured imageA new blog post is will spread the word about make.wordpress.org to encourage folks jumping in and helping. The marketing needs someone to design a featured image for the blog post.
  • Design interface for plugin/theme compatibility with Gutenberg in WordPress admin – Now that Gutenberg is getting closer we need a way to reflect in the WordPress admin whether a plugin or theme is compatible with Gutenberg. This is a perfect ticket for a designer who’s interested in supporting a few hours a week for the next month on UX work related to sketching out ideas and figuring out how this would look.
  • PHP Servehappy project – Servehappy had been officially approved as a feature project for WordPress. We need a designer to work with the development team on what a page would look like talking about this project. In particular the design needs to present this linked content. The person doesn’t have to be technical as that could ensure the target market is reached correctly. However, it’s important that they are able to connect with the development team to bridge the gap of communication between what the team is building create and what users need.
  • Create a dashicon for WordPress Coding Standards. We need someone to create a new dashicon! That’s a ton of fun for the right person. You can more about dashicons here and here and here’s a tutorial on making one. If you’re interested this could be perfect for you.
  • Improve the content of the Grey Box™ on the Design page – It’s supposed to be a welcome to the team and sharing more about how to get started. Link to edit screen.
  • Plugin search – The team is working to identify what information will be good to use for filters and how to present that information. The plugin directory has been recently redesigned, so it will be important to take that into consideration (and not undo all that work) when helping the team add search filtering to the design.

If you’re interested in helping reach out to Tammie Lister or Mel Choyce and they can connect you. Or you can comment in the Slack channel on the specific request (make sure to checkmark “also send to #design” if you do, so that it doesn’t get missed: https://d.pr/i/ExTJ3o)

Structure of the design team

  • Trello board – We’ve created a Trello board to handle any issues that aren’t in Trac or Github. We had a great discussion about how the Trello board can be structured, how cards can be labeled, etc and ended on a good point for today. We’ll also discussed the need for folks to post to it. This board could ultimately replace the calls for design page on Make, with that page linking back to the Trello board.
  • We also have a Start Here card that will need some love. Then whatever happens here should get updated back into the design handbook.
  • It was also noted that it could be helpful for handbooks to start looking more like the Gutenberg one.

Monthly recaps

We’re going to start moving from weekly calls for design updates to instead posting a monthly summary based on the weekly #design meetings.@joshuawold and @boemedia will post the summary, and if a third person wants to help out we won’t say no! 🙂

Next steps

If you’re still reading this, and haven’t yet felt you can make a contribution to the design of WordPress, we can emphatically answer that you can! It might feel a bit overwhelming on where to start, the easiest way is to join the next #design meeting and look for an opportunity to give your support, or grab one of the calls for design issues above and jump in.

#meeting-notes