uxmeeting http://default/ en UX meeting recap http://default/pieces/ux-meeting-recap <div data-history-node-id="257" class="h-entry node node--type-piece node--view-mode-fulltext ds-1col clearfix"> <div class="clearfix text-formatted field field--name-field-sub-title field--type-text field--label-above"> <div class="field__label">Sub title</div> <div class="field__item"><p>Topics du jour, how we work, where you can help, the usual</p> </div> </div> <div class="field field--name-field-image field--type-image field--label-hidden field__item">/sites/default/files/styles/large/public/200160823-hangouts.png?itok=VHwGyUK1</div> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>Two meetings every week since <a href="https://groups.drupal.org/node/509798">end of march</a> this year. Safe to say we’ve found a consistent rhythm.</p> <p>And it’s working. It’s become a useful way to check in on current priorities, review patches while screensharing (visuals, transitions, flows!), decide on next steps and generally discuss hard problems without having to type so much.</p> <h2>The agenda for today was</h2> <ol> <li><a href="https://www.drupal.org/core/roadmap">Roadmap</a> – The core roadmap was updated to current state of things. Use this page to get a bird’s eye view on where Drupal core is moving towards.</li> <li><a href="https://www.drupal.org/node/2785735">Ideation process</a> – The first part of going from idea to plan got positive feedback and helpful questions and suggestions. Maybe a few words from actual maintainers and then we can make it so.</li> <li><a href="https://www.drupal.org/node/665790#comment-11535849">Status page</a> – We have a beautiful new design that now needs review and more code to create a complete patch. If you know your core markup and CSS, go have a look!</li> <li><a href="https://www.drupal.org/node/2739079#comment-11542211">Block place design update</a> – An issue that iterates the design of an initial commit. We quickly discussed what the feedback should be and I added a comment to that effect right then and there. It’s an example of managing scope, pushing to focus on the actual fix first, and defer new, potentially good ideas to a followup discussion.</li> <li>Sample content – Kevin shared his initial <a href="https://docs.google.com/document/d/16QCGgWwm1s9krcuObcCym5qk4bsAhXgEq3DEt-ePhUE/edit?pref=2&pli=1#heading=h.xtk523o4ws2h">thoughts and ideas for adding sample content, structure and configuration to core</a>. More questions then answers but that’s just where we’re at for now. You are welcome to add your questions and ideas, please do.</li> </ol> <p>As always, most welcome to join if you’re interested. Find us in the ux channel of the <a href="http://drupalslack.herokuapp.com/">Drupal Slack</a> room, or follow <a href="https://www.twitter.com/drupalux">@drupalux</a> on the twitters.</p> </div> <div class="field field--name-taxonomy-vocabulary-1 field--type-entity-reference field--label-inline"> <div class="field__label">Tags</div> <div class="field__items"> <div class="field__item"><a href="http://default/tag/drupal" hreflang="en">Drupal</a></div> <div class="field__item"><a href="http://default/tag/ux" hreflang="en">ux</a></div> <div class="field__item"><a href="http://default/tag/uxmeeting" hreflang="en">uxmeeting</a></div> <div class="field__item"><a href="http://default/drupal" hreflang="en">drupalplanet</a></div> </div> </div> <span class="hidden"><a href="https://brid.gy/publish/twitter"></a></span> <div class="node__links"> <ul class="links inline"><li class="comment-forbidden"></li></ul> </div> </div> Tue, 23 Aug 2016 21:58:26 +0000 Roy 257 at http://default