It came up multiple times at recent events that it would be very helpful for people significantly working on Drupal 8 critical issues to get together more often to talk about the issues and unblock each other on things where discussion is needed. While these do not by any means replace the issue queue discussions (much like in-person meetings at events are not), they do help to unblock things much more quickly. We also don't believe that the number of or the concrete people working on critical issues should be limited, so we did not want to keep the discussions closed. After our first meeting last week, here is the recording of the second meeting from today in the hope that it helps more than just those who were on the meeting:

Unfortunately not all people invited made it this time. If you also have significant time to work on critical issues in Drupal 8 and we did not include you, let me know as soon as possible.

The issues mentioned were as follows:

Alex Pott
Performance issue: https://www.drupal.org/node/2470679
Entity title: https://www.drupal.org/node/2498849
Render cache for views: https://www.drupal.org/node/2381277

daniel wehner, Gábor Hojtsy
Make Views bulk operations entity translation aware: https://www.drupal.org/node/2484037

Lee Rowlands
Ensure #markup is XSS escaped in Renderer::doRender(): https://www.drupal.org/node/2273925
Create a php script that can dump a database for testing update hooks: https://www.drupal.org/node/2497323
Views::getApplicableViews() initializes displays during route rebuilding etc.: https://www.drupal.org/node/2497017

Jibran Ijaz
FieldItemInterface methods are only invoked for SQL storage and are inconsistent with hooks: https://www.drupal.org/node/2478459#comment-9983133

Alex Pott
FieldItemInterface: https://www.drupal.org/node/2478459
Ajax form patch: https://www.drupal.org/node/2263569

daniel wehner
HTML IDs: https://www.drupal.org/node/1305882

Jibran Ijaz
PHP Script for dumping the database: https://www.drupal.org/node/2497323