Design meeting summary March 22, 2018

Find the transcription here on Slack.  The links on the main topics will jump straight to where this item was discussed in the meeting.


Design team related

  • Lack of feedback from Calls for design
    A few designers had a negative experience when callers for design never properly got back after designs were delivered. As a team, we feel the need to inform people who call for design how we’d like to proceed.
    We’re opting on setting up a guide on how the design process takes place and what can be expected from the designers, but also what we expect from the one who calls for the design. @boemedia will start a draft in Google docs, and after iteration it will move over to the handbook so we can point to this document when someone calls for design.

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.

Requests to review existing tickets

Typically from Trac or GitHub

  • no requests this week

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.

Final question by @boemedia about the Invision licenses. What’s the status? @karmatosed says we have it and she will write a post and explain how designers can get a license.