meetings http://default/ en One way to find out what’s happening in Drupal http://default/2017/drupal-core-meetings <div data-history-node-id="329" 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>Many channels, but the weekly meetings some teams have are a great way to get started.</p> </div> </div> <div class="field field--name-field-image field--type-image field--label-hidden field__item">/sites/default/files/styles/large/public/20170830-meetings.png?itok=yr-wnW23</div> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>It’s a big project, Drupal is. Many different areas that people are working in. The project is it’s own stack of technologies and skills, from low level framework considerations to the last bit of people-facing interface. <a href="https://www.drupal.org/node/2477789">Composer</a>, <a href="https://www.drupal.org/contribute/documentation">Documentation</a>, <a href="https://www.drupal.org/node/2893640">Accessibility</a>. Each layer in the stack comes with shared considerations about goals, priorities, standards, documentation and getting code written, reviewed, committed.</p> <p>There are whole teams working on specific feature sets. <a href="https://www.drupal.org/node/2825215">Media</a>, <a href="https://www.drupal.org/node/2721129">Workflow</a>, <a href="https://www.drupal.org/node/2735059">Migrate</a>. But how to find out what’s happening inside each of these areas? <a href="https://www.drupal.org/node/2807237">PHPUnit</a>, <a href="https://www.drupal.org/node/2847582">Out of the Box</a>, <a href="https://www.drupal.org/node/2757967">API-first</a>.</p> <p>These links all go to long, dense outlines of <a href="https://www.drupal.org/project/issues/ideas?status=1&categories=5">plans</a> and issues where current state of things and what to work on next is not super obvious. But there is a predictable and reliable way to see and hear people discuss their projects and initiatives. <a href="https://www.drupal.org/node/2762505">Outside-In</a>, <a href="https://www.drupal.org/node/2755613">Admin Information Architecture</a>, <a href="https://www.drupal.org/node/2830668">Progressive Web Apps</a>. Many of the larger initiatives have weekly meetings to discuss progress, status and next steps. <a href="https://www.drupal.org/core-mentoring">Mentoring</a>, <a href="https://www.drupal.org/project/issues/search/drupal?issue_tags=sprint%2C+D8MI&issue_tags_op=all+of">Multilingual</a>, <a href="https://drupaldiversity.github.io/get-involved/">Diversity</a>.</p> <h2>Here’s <a href="https://calendar.google.com/calendar/embed?src=happypunch.com_eq0e09s0kvcs7v5scdi8f8cm70%40group.calendar.google.com&ctz=Europe/Budapest">a calendar with all the core meetings</a> on it.</h2> <p>Where and how these meetings are held differs per team. <a href="https://www.drupal.org/irc">IRC</a>, <a href="https://www.youtube.com/playlist?list=PLjikRPQzSOt3BLREHjyz3zeasWtvbMzjA">Google Hangouts</a>, <a href="https://www.drupal.org/slack">Slack</a>. Many interesting channels on Slack lately, check those out.</p> <p>These meetings are an easy way to start listening in and getting up to speed. The timing is predictable and you can be sure it’s the experts talking about what is happening and important <em>now</em>. <a href="https://www.drupal.org/node/2884601">Layout</a>, <a href="https://groups.drupal.org/security">Security</a>, <a href="https://www.drupal.org/node/2702061">Frontend components</a>. Don’t let that hold you back to ask questions or share your thoughts. They are nice people and always looking for more people to help out. You <em>are</em> welcome.</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/meetings" hreflang="en">meetings</a></div> <div class="field__item"><a href="http://default/drupal" hreflang="en">drupalplanet</a></div> <div class="field__item"><a href="http://default/tag/drupal" hreflang="en">Drupal</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> Wed, 30 Aug 2017 09:09:57 +0000 Roy 329 at http://default UX meeting format is evolving http://default/pieces/ux-meeting-format-evolving <div data-history-node-id="238" 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>50/50 on new ideas and reviewing work in progress</p> </div> </div> <div class="field field--name-field-image field--type-image field--label-hidden field__item">/sites/default/files/styles/large/public/ecape-velocity-1.jpg?itok=KRv-75d9</div> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>After a couple of weeks of setting up with mostly free-format meetings in IRC we’re going to try a more structured format for our weekly UX meetings:</p> <ul> <li>First half hour: people can introduce a problem + proposed (possible) solution</li> <li>Second half hour: we review any work that has progressed over the past week. Often a core committer will be around to provide guidance or even actually commit changes that are good to go.</li> </ul> <p>We did a first ad-hoc version of this last week, including a hangout with screen sharing. It worked really well, was productive and a lot of fun. Seeing the same thing in action is helpful when discussing user interface changes!</p> <p>Next one is coming up and people from <a href="https://www.acromediainc.com/">Acromedia</a> will present on a topic and outline their proposed solution. For the second part I’m hoping we can review the <a href="https://www.drupal.org/node/2724819">“Place block” experimental module patch</a>.</p> <p>The meeting will take an hour. <a href="https://calendar.google.com/calendar/embed?src=jhj7p0u7link8vvjdqqsqr5qtg%40group.calendar.google.com&ctz=Europe/Amsterdam">Here’s a calendar</a> for the date and time. </p> <p>Want to join? Join the UX channel on <a href="http://drupal.slack.com/">drupal.slack.com</a>. Get an <a href="http://drupalslack.herokuapp.com/">automatic invite here</a>. We’ll link a hangout from there and make sure we’re broadcasting live so at least everybody who wants can follow along and use Slack for background chat.</p> <p>See you there!</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/drupal" hreflang="en">drupalplanet</a></div> <div class="field__item"><a href="http://default/tag/d8ux" hreflang="en">d8ux</a></div> <div class="field__item"><a href="http://default/tag/process" hreflang="en">process</a></div> <div class="field__item"><a href="http://default/tag/meetings" hreflang="en">meetings</a></div> <div class="field__item"><a href="http://default/tag/collaboration" hreflang="en">collaboration</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> Mon, 30 May 2016 22:53:56 +0000 Roy 238 at http://default