X-post: WordCamp Block: Speakers

X-post from +make.wordpress.org/community: WordCamp Block: Speakers

Change of design meeting times

As per October 24th, 2018, there will be a change of the weekly meeting times. We’re also adding another more inclusive time meeting.

New meeting times will be:

  • Monday: Triage: 16:30 UTC, won’t change.
  • Wednesday: Team meeting: 18:00 UTC meeting time change.
  • Thursday: Open hours 12:00 UTC to fit more countries.

Monday ticket triage will also start including focus projects, instead of working on the oldest tickets available. This includes releases.

For Wednesday meetings, focus and leads of specific components or areas get time to start giving updates on what’s going on.

Check these new times in your own time zone.

Weekly design meeting notes of Wednesday October 17, 2018

The full transcript of our meeting this week can be found on our Slack channel.

Change of meeting times and format

After a quick round of checking how everyone’s doing, @karmatosed suggests a change of the weekly meeting times and also adding another more inclusive time meeting.

New meeting times will be:

  • Monday: Triage: 16:30 UTC, won’t change.
  • Wednesday: Team meeting: 18:00 UTC meeting time change.
  • Thursday: Open hours 12:00 UTC to fit more countries.

Monday ticket triage will also start including focus projects, instead of working on the oldest tickets available. This includes releases.

For Wednesday meetings, Tammie suggests that focus and leads of specific components or areas get time to start giving updates on what’s going on.

Later on in the meeting, we circled back a bit to this topic because of daylight saving times. We change to the times mentioned here as per the 24th of October and adjust to daylight saving time (DST) in the weeks following.

The new meeting times will be added to the calendar, our Slack channel and the design blog page (P2) on make.wordpress.org. We’ll also post them on our blog in a separate post for better visibility.

Japanese design team meeting

Following WordCamp Tokyo, the Japanese design team actively discusses what’s going on in WordPress design and with the help of translators, they follow up and work on stuff that’s mentioned in the International meetings.

Their findings are usually posted as a comment on the weekly design notes, but it would be nice to create better visibility, probably by turning these comments into separate blogs. Their meeting notes can be found as a comment on the latest international meeting notes.

Calls for design

A quick round of checking on the calls for design that are being worked on. No updates here, which is totally fine. But if people need help on stuff they’re working on, please reach out.

Open floor

What are people working on? Anything inspiration wise to share?

Joshua Wold’s sketch on WP5 user flows

There’s a quick update from the training team regarding learn.wordpress.org. They’ll have updated wireframes ready after the next meeting.

Before we finally close the meeting, Tammie thanks @mizejewski for her work as a team rep, as she’s stepping down for a little while. However, she won’t leave the design team fully and will be back contributing as soon as she can.

Thanks to everyone attending the meeting. If you have anything to add, please feel free to post in our Slack channel or in the comments below.

These notes were posted using Gutenberg. Yay!

Design meeting notes for October 10, 2018

The full transcript of our meeting this week can be found on our Slack channel. For this week we had no housekeeping or inbox items to discuss. Great progress!

Open floor

We started out asking folks to bring up items to discuss. Sarah James jumped in with some exciting news (we then ended early after that great conversation). 

User Testing

Overview: @sarahjames completed a round of user testing that focused on the publisher flow experience. This included 5 unmoderated tests, focused on asking users to go through a preflight checklist tasks for publishing. A quick overview shows great reception, with a system usability score of 85.5 for the tasks that were asked of users.

The scenario: Imagine you are an editor for a fictional travel magazine and you need to publish some articles to you blog. For this user test, users were asked to go through a checklist of items they’d need to do before publishing.

Next steps: Sarah will go through the videos that were generated from the study and create a report of findings to share with the team. In the meantime you can read about a previous round of user testing that was conducted. 

Design meeting notes for October 3, 2018

The full transcript of our meeting this week, based on the previously posted agenda, can be found on our Slack channel.

Issue with Gutenberg callout in IE 11

We discussed an issue that was shared in the channel showing a display problem with the layout for the Gutenberg callout in the dashboard in the 4.9.8 WordPress release. Anyone wishing to look at the problem or validate the issue can jump into the newly related Trac ticket.

Calls for design

We jumped into Trello and discussed the existing calls for design. This is for any design related issues that don’t fit into the usual Trac or Github ticket systems.

  • Privacy badge@boemedia reached out to the privacy team for feedback on the badge that’s been created and is waiting for a response.
  • Design for learn.wordpress.org on Design team – The learning team is looking at the best way to move the design forward for the “Learn” website, in efforts to have it believe more with the other sub pages of w.org. Some changes will likely be coming and support is needed to pull it into a new direction. They will be posting an update with more info on what’s needed.
  • Design for “Create a Website” on WordPress.org – Cathi Bosco shared an update and will plan to have an update on this in soon. The previous work on Create a Blog has been finished, which will help unlock this.
  • PHP meeting on Design team – This is being worked on actively, it’s uncertain if input/feedback is needed from the design team in general.

Open floor

We jumped into a few topics.

  • Contributing to WordPress – It’s important to be sharing the value of design contribution for WordPress. So many wonderful folks are helping with moving WordPress forward, sharing their stories, doing the actual work, and much more. If anyone is on the fence about talking about this (maybe at your local meetup, or at a WordCamp?) take a stab at it and jump in. You won’t regret it!
  • Showing readme info in the installed themes page – We discussed the potential of allowing theme creators to display additional information related to their theme in the admin installed themes page. Right now plugin authors are able to show a link to details about their plugin (linking to the appropriate w.org plugin page). It would be helpful to find out what’s possible here, the next step will be for a ticket to get created identifying where this could go.
  • Tooltips in WordPress – A question was raised related to adding tooltips in WordPress and what’s available. A Trac ticket has been created, and as of now it looks like the work is covered. A new ticket may be opened specifically related to the discussion point about adding a new tooltip into WordPress. See Slack log.

#meeting-notes

Design meeting agenda for Wednesday 3 October, 2018

The weekly design meeting is on Wednesdays at 17.00 UTC (see it in your time here). If you have anything else to add, please comment below or mention it on our Slack channel #design.

  • Calls for design
    follow-ups (if any) on our Trello board
  • Design ticket triage
  • Open floor – anything you’d like to share?

 

#meeting-agenda

Design meeting notes for Wednesday 26 September, 2018

The full transcript of our meeting this week, based on the previously posted agenda, can be found on our Slack channel.

There are no items in the inbox for this week. On the question if anyone wants help on something they’re working on, @joyously mentions that the theme review team has been talking about the need for the themes to show readme files like plugins do. They would need design for core and the repo.

A short discussion on this topic follows, and the proper order to get things going, will be opening a meta-ticket.

Calls for design

Good team work happened on the ‘Create a blog guides content‘. @cathibosco1, @issajohn1 and @hugobaeta have been working on this and Cathi announces it’s a wrap. Pages will be added to w.org soon. John Issa also did a fabulous job and worked on a Sketchfile with styles that can be used and used for other .org pages.

Contributor day guide

@karmatosed and @folletto went to WordCamp Tokyo and they got to try run a new format at the contributor day. They had never had a design table in Tokyo before and it was an incredible experience. The format was written down, the plan that was settled on is one of 2 possible options: with triage and without triage. That last one hasn’t been written yet. But you can comment, add thoughts on the doc that’s already there.

Additionally, @marybaum asks for assistance on trying this format at WordCamp Orlando and Tammie offers to assist remotely.

Open Floor

@joshuawold and @paulbiron are working on a post for the 4.9.8 conclusion. Joshua will add some things from design perspective. The design team is curious to hear about his findings.

 

#meeting-notes

Design meeting agenda for September 26, 2018

The weekly design meeting is on Wednesdays at 17.00 UTC. If you have anything else to add, please comment below or mention it on our Slack channel #design.

  • Triage Inbox
  • Calls for design: follow-ups (if any)
  • Contribution day plan document: opinions and insights.
  • Open floor: we’ve not had one for a while, let’s have one! Bring your questions, thoughts, comments and insights.

#design-agenda

#meeting-agenda

Design meeting notes for September 19, 2018

The full transcript of our meeting this week, based on the previously posted agenda, can be found on our Slack channel.

Triage inbox

  • Meetup Organizer badge – We began by jumping into our triage inbox, and discussed the proposal for a Meetup Organizer badge presented by the Community team.
  • AMP Stories in WordPress – The team organizing for WordCamp New York has been experimenting with a new story format for the meeting schedule using work created by Pratik Ghela. Feedback was requested, and it opened up a conversation about the software used. @postphotos followed up by sharing the work that is happening on the AMP for WordPress plugin to bring AMP Stories to WordPress as an open source solution (it’s still a work in progress).

Calls for design followup

WordCamp discussion

The conversation continued with a brief discussion on recent experiences in WordCamps. You can catch up here.

Design meeting agenda for September 19, 2018

The weekly design meeting is Wednesdays at 17.00 UTC. If you have anything else to add, please comment below or mention it on our Slack channel.

Triage Inbox

See Inbox column on Trello board

Calls for design: follow-ups

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

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.

 

#design-agenda

#meeting-agenda