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.
Design team related
- On our about page for make.wordpress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://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 UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it.. 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 Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the make.wordpress.com/marketing team uses for example: https://trello.com/b/8UGHVBu8/wp-marketing. would be a good place to store assets, but we revisited that idea. We talked about integrating Github GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/, 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 Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., etc. should be transferred to Inbox each week, along with any new cards that need to be acknowledged.
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.
Requests to review existing tickets
Typically from Trac or GitHub
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.
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
