Design meeting summary March 15, 2018

Agenda for the meeting:


Topic: Lack of feedback from calls for design – We held off on this since we’d like Mel and Tammie to be able to weigh in next week on it.

Triage inbox

Documentation for dashicons:  – There’s been back and forth on how to contribute with Dashicons, and we agreed it’d be helpful to pull all that together into a guide on how to contribute.

It would include steps on:

  • How to request a Dashicon
  • How to contribute a Dashicon, including which icons need designs
  • Where to submit final artwork for review, etc.

We hope to have clarity to outline it in the near future.

Next steps are to brainstorm this in TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the team uses for example:, make sure that the team working on Washicons can weigh in, then draft a page in the handbook (

Calls for design

Calls for design cont.

  • Great news! @khleomix did a quick and excellent job for marketing for the TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. ticket overview! The card has now been archived.
  • Going forward we want to find a way to break down large calls for designs into manageable pieces. Great example where this was done:
  • The next step is to ideally write a blog post with tips on how to construct a call for design, and how to break it down into smaller pieces. @cathibosco plans to work on a draft for this.
  • If anyone is interested feel free to own the process of breaking down an existing call for design into smaller pieces.