Problem/Motivation

Panels is awesome. Drupal 8 will have an awesome architecture. Lets work out how to port Panels to Drupal 8.

Proposed resolution

Use roughly the same architecture as the D7 version, except (a) take advantage of the new APIs of Drupal 8 (especially the CTools stuff moved into core, like plugins, display variants, etc) and (b) spread the pieces out among more contrib modules (rather than the more "monolithic" D7 CTools/Panels). For example, we hope to share Layout plugins with Display Suite and the Context API with Rules.

Implement the low-level infrastructure for layouts in the Layout Plugin module (based on frega's layout builder module on GitHub) with the goal to move it into core in Drupal 8.1.0: #2296423: Implement layout plugin type in core

Hold weekly meetings every Tuesday at 12pm CT (UTC-0500 during daylight savings, and UCT-0600 during standard time) on IRC (irc.freenode.net) in the #drupal-scotch channel.

(Note: Eventually, we'd like to build a flexible layout builder (that creates derivative plugins for Layout Plugin) which we're told we can put into the Layout module when ready: #2317333: Roadmap / future plans for layout.module)

(Note: We have the d8panels sandbox, to allow more contributors to collaborate and iterate more quickly on the Panels port than a patch workflow would allow. However, to date, the number of contributors working on Panels has been pretty modest so we've been working primarily with patches in the issue queue.)

Roadmap

Milestone 1 (February 16th, 2016)

See the Google Doc: Panels eco-system roadmap: Milestone 1 (February 16th, 2016)

Milestone 2 (May 1st, 2016)

See the Google Doc: Panels eco-system roadmap: Milestone 2 (May 1st, 2016)

Remaining tasks

Identify a) missing pieces for core, b) steps necessary to port Panels to Drupal 8.

Issues tagged with "D8panels" will appear on our sprint board: http://contribkanban.com/#/sprint/d8panels

Core issues (that we depend on!)

Panels porting roadmap

Page Manager issues

Layout / Layout Plugin issues

CTools issues

Core issues (that would be nice, maybe for 8.1.x)

Core issues (that are related and will improve our lives)

None at the moment.

User interface changes

We'll aim for a user interface that has all the same "pieces" as D7 Panels, but not necessarily exactly the same.

API changes

Since the Drupal 8 version will adopt a D8-style architecture, the API will likely be entirely different than the D7 version. That said, a lot of pieces of CTools are now part of the D8 API, for example, plugins. So, declaring a Layout plugin for use with Panels will be done the same way you declare a Block plugin in normal D8 core.

Meeting notes

Original report by @parijke

I like to know if drupal 8 is going to be with panels and page manager. Maybe i've missed it, but I can't think of Drupal without it

Comments

rei’s picture

yes, I also like to know

DamienMcKenna’s picture

Title: Is Drupal 8 going to be supported? » Drupal 8 port of Panels
Category: Feature request » Task
Issue tags: -drupal8 +Drupal 8.x

Lets standardize the title & tag.

DamienMcKenna’s picture

Issue summary: View changes

Added the standard issue summary pieces.

dawehner’s picture

There has been some experiments on https://drupal.org/sandbox/eclipsegc/2158511

Things we certainly need which aren't in core:

  • Layouts
  • relationships
  • Take over the page rendering process aka. panels everywhere
  • Register own page callbacks aka. normal panels
  • Support of context in blocks? If this would work it might be possible to get rid of content type plugins
  • Access plugins seems to be the same as conditions?
DamienMcKenna’s picture

@dawehner: Thanks for that. We need to break this down further into:

  • Changes that could make it into 8.0.x (assuming semantic versioning) which are already in progress.
  • Changes that could make it into 8.0.x but which are not already in progress.
  • Changes that won't make it into 8.0.x. / will need to stay in contrib for 8.0.x.
fago’s picture

relationships

Not sure this is still needed, you could just add a computed field instead.

Access plugins seems to be the same as conditions?

Yeah, it should be.

Support of context in blocks? If this would work it might be possible to get rid of content type plugins

Yes, context is still an area that needs quite some work I guess. While there is some basic context system for conditions in core, it's just a thin-wrapper around typed data that adds/does nothing right now. The actual hard stuff, context mapping and configuration still needs to be written.
That's something will have to tackle for the Rules port as well (see latest 8.x plans). So far the strategies of panels/Rules to solve the same problem are quite different, thus this is probably not something that can be shared very easily. Howsoever, the plan for Rules is to develop those components in a a re-usable / generic fashion as far as it seems reasonable, such that we can re-use them for other contextual plugins (besides conditions/actions) as well - e.g. blocks/panes. So if someone is going to tackle this, please get in touch with me so we can make sure we reach some compatibility at least at the lower level (context API) and can discuss our common issues & possible solutions.

frega’s picture

In Szeged we had a impromptu-bof w/ aspilicious, schnitzel, klausi, jbeach, pixelmord, myself and quite a few others.

It wasn't a "panels-specific" discussion but covered the whole "content placement"-problem space (i.e. page_manager/panels/panels everywhere, context/ds, block-ui, layout.module etc.) .

We tried to summarize some of the discussion in a google doc here (it is world-writable): https://docs.google.com/document/d/1tBHL-nR2XgDaQVPntjFNLynyli_pPwgBIXyc...

Would love to see how we can maintain the flexibility (and differences) that different approaches have brought to the table, whilst sharing as much as possible.

Best, Fredrik

tim.plunkett’s picture

I've been experimenting with block plugins, and I came up with http://drupal.org/project/block_page

Currently, it provides a config entity type "Block Page", which can have a path and any number of "page variants".
Each page variant can have any number of blocks.

Right now the default page variant is hardcoded to provide two "regions", but that can be swapped out for a Layout-esque solution.

This covers the landing page functionality of page manager, and has room to grow.
I'm not really concerned with copying this or just reusing this for page_manager/panels, I'm not too attached to it yet.

frega’s picture

I recently returned to some stuff i started as part of #1841584: Add and configure master displays and moved it to separate repo here: https://github.com/frega/layout
The repo is very much WIP & more of a plaything in order to familiarized myself w/ D8; it focuses less on variants/page manager stuff and more on content placement (w/ some backbone stuff as groundwork for future in-place-editing etc.).
@tim.plunkett i'd definitely love to help out with/talk about block_page (or any efforts in the pm/panels d8 field) and will reach out to you on IRC.

tim.plunkett’s picture

After discussion with @EclipseGc and @merlinofchaos, block_page is gone and now we have https://drupal.org/project/page_manager

rlmumford’s picture

I've been reviewing tim.plunkett's Page Manager module this morning and it looks like a really good starting point for a panels port. I'm not sure where page_manager ends and panels begins, however it looks to me like we could take a lot of the work done in the Layout module (prior to it being removed from core) and use a combination of that and page manager to build Panels in drupal 8.

Page Manager provides an architecture for defining pages and variants, as well as passing contexts to blocks - there are even patches against core that have gone in see list. I think therefore that the content panes side of Panels/Ctools has largely been dealt with.

Areas that need work as far as I understand it:

  • Relationships - I agree with fago that we probably want to just use the Entity/Field API for this although we may need context to 'lightly' wrap around it - we don't a block that needs a node to care about how it gets that node.
  • Drag and Drop Layout UI - Extend the ex-Core layouts module to give us a drag and drop UI for placing blocks in a Panel.
  • Overriding Block Configuration - Panel specific overrides.
  • Wrap it all up in a Render handler - Page Manager's Variant handler is a good example of a class that renders a load of blocks while passing context between them. Panels probably wants to have its own thing so that it can be reused for Mini-Panels - maybe a port of the Render Pipelines system in D7. If that is generic enough then it can be used fro Panels Everywhere, Panelizer and a host of other things.

The more I look at it, the more I think we may want to use Layout 8.x-2.x-dev as a starter point. That defines layouts and a Display config entity that renders them.

RoySegall’s picture

I think the page manager of tim should be merged into panels. And we also need to handle things like views pane and ctools content type render plugin which come with required and optional context that panels is passing.

andypost’s picture

Suppose better to join forces with rules to make core conditions usable #1976758: Plugins miss metadata about configuration

I'd prefer page manager as separate module to provide sane UI to core routing
Context and Condition already tightly coupled to routing (request attributes and access checkers)

Here is a attempt to make entity displays usable for ds and panels #1875974: Abstract 'component type' specific code out of EntityDisplay
Currently entity displays are prototypes of panels displays.

For every kind of content there's core blocks that lacks proper context and conditions to be placed/rendered into layouts

tim.plunkett’s picture

I think the page manager of tim should be merged into panels.

Nope. I can elaborate after our meeting next week. They are separate for a reason.

Context and Condition already tightly coupled to routing

This is not true.

For every kind of content there's core blocks that lacks proper context

#2272801: Allow blocks to be context aware. *just* went in. Patience.

rlmumford’s picture

tim.plunkett, is this meeting with panels people an open meeting?

dsnopek’s picture

For those who couldn't make it, here are the notes from our meeting today:

https://docs.google.com/document/d/1EOqzx3ogskD1ZzOg6zyDdTLxVmGzD-QJ-8_S...

@rlmumford: Sorry, I didn't see your comment earlier! The meeting was coordinated on an "invite" basis, but I had originally (more than a week before your comment) invited everyone who commented on this issue. :-/ Anyway, I hope the notes are helpful!

dsnopek’s picture

Version: 7.x-3.x-dev » 8.x-3.x-dev
Issue summary: View changes

I've tried to fill in the issue description with the current state of this effort. Please feel free to modify it further!

dsnopek’s picture

Issue summary: View changes
rlmumford’s picture

*Removed*

dsnopek’s picture

Issue summary: View changes
dsnopek’s picture

Issue summary: View changes

Updated roadmap with some tasks.

dsnopek’s picture

Issue summary: View changes
dsnopek’s picture

Issue summary: View changes
dsnopek’s picture

Issue summary: View changes

Skipped this weeks IRC meeting due to low attendance. Copied proposed agenda for next week!

dsnopek’s picture

Issue summary: View changes
dsnopek’s picture

Issue summary: View changes
dsnopek’s picture

Issue summary: View changes
dsnopek’s picture

Added link to the issue @frega made asking about the roadmap/plans for the Layout module

dsnopek’s picture

Issue summary: View changes

Adding notes from the latest (non-)meeting.

dsnopek’s picture

Issue summary: View changes
dsnopek’s picture

Issue summary: View changes

Added the notes from today's IRC meeting.

dsnopek’s picture

Issue summary: View changes
dsnopek’s picture

Issue summary: View changes

Added some related core issues.

dsnopek’s picture

Issue summary: View changes

Blergh! HTML fix to summary.

dsnopek’s picture

Issue summary: View changes

Added notes from this weeks meeting.

dsnopek’s picture

Issue summary: View changes
dsnopek’s picture

Issue summary: View changes

Added an issue to the roadmap about implementing renderer plugins: #2340999: Implement "display renderer" plugin type (now called "display builder")

dsnopek’s picture

Issue summary: View changes

Meetings suspended for two weeks until the week of 2014-10-06 - will post an update here when meetings resume again.

dsnopek’s picture

Issue summary: View changes

Added a new issue: #2350119: Move permissions into panels.permissions.yml

And re-arranged the core issues so it's clear that we don't depend on most of them to move forward.

dsnopek’s picture

Issue summary: View changes

Weekly meetings rescheduled to every Tuesday at 12pm CDT (UTC-0500) on IRC (irc.freenode.net) in the usuall place: the #drupal-scotch channel.

dsnopek’s picture

Issue summary: View changes

Added a link to the meeting notes from today: 2014-10-07 - #drupal-scotch on irc.freenode.net

Also, update the issue summary a little to reflect that layout_plugin got promoted to a full project.

dsnopek’s picture

Issue summary: View changes

Er, switching away from sandbox link too.

dsnopek’s picture

Issue summary: View changes

Added some related core issues from today's meeting.

dsnopek’s picture

Issue summary: View changes

Added the notes for todays meeting: 2014-10-14 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from todays meeting: 2014-10-21 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from todays meeting: 2014-10-28 - #drupal-scotch on irc.freenode.net

philsward’s picture

Panels isn't exactly the place to suggest this, but I'm wondering what it would take to have say... panels, completely override the theme process of Drupal and build the template on the fly for the requesting viewport. This is more of a layout issue than a panels issue, but they kind of go together...

The thought is to have the layout system generate the output code depending on the breakpoint viewport. Whenever a change is made on the backend (admin interface), a new "template" is created and cached as a static file for that viewport. This way we can send ONLY what needs to be sent to the requesting viewport instead of vomiting a bunch of information that the device will never use. If the viewport changes, reload the page for the new viewport or use (angularjs?) to pull only the files that need changed. Most devices have a static viewport width and height. Why send all of the information designed for a desktop, if that device will never have the screensize to utilize all of that information?

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2014-11-11 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added the notes from today's meeting: 2014-11-18 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes for today's meeting: 2014-11-25 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes
dsnopek’s picture

Issue summary: View changes

Added the notes from today's meeting: 2014-12-09 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added the notes from today's meeting: 2015-01-27 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added the notes from today's meeting: 2015-02-03 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Title: Drupal 8 port of Panels » [meta] Drupal 8 port of Panels
Issue summary: View changes

Added the notes from today's meeting: 2015-02-10 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-02-17 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-02-24 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-03-03 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-03-10 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-03-17 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-03-24 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-03-31 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-04-07 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-04-14 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-04-21 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-04-28 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-05-05 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

We didn't meet last week due to DrupalCon - sorry for the retroactive notice! And today we didn't have enough attendance to hold a proper meeting. We'll be back at it next week! There was some great progress at DrupalCon that we'll talk about..

dsnopek’s picture

Issue summary: View changes

Added notes for today's meeting: 2015-05-26 - #drupal-scotch on irc.freenode.net

Also added info about our sprint board: http://contribkanban.com/#/sprint/d8panels

dsnopek’s picture

Issue summary: View changes

Added notes for today's meeting: 2015-06-02 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-06-09 - #drupal-scotch on irc.freenode.net

tim.plunkett’s picture

Category: Task » Plan

Using the new Plan category.

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-06-16 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-06-23 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added the Page Manager meta issue that came out of our meeting today: #2511554: [meta] Move some parts of Page Manager into CTools

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-06-30 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-07-07 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-07-14 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-07-21 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Today's SCOTCH meeting was canceled due to lack of attendance.

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-08-04 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added the notes from today's meeting: 2015-08-11 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Cleaned up the issue a bit and updated it for the current state of things!

dsnopek’s picture

Issue summary: View changes

Fix HTML error in issue summary.

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-08-18 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-08-25 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-09-01 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-09-08 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-09-15 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-09-29 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-10-06 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-10-13 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-10-20 - #drupal-scotch on irc.freenode.net

saltednut’s picture

Issue summary: View changes
dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-11-03 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-11-10 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-11-17 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-11-24 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-12-01 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Update time in the issue summary to be valid both during daylight savings and outside of it.

japerry’s picture

Proposing that we move to Panels 8.x-4.x once we get out of synchronization with the other suite of modules (ctools, pm, etc) in 3.x alphas.

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-12-08 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added the requirements we came up with at our "roadmap meeting" last night about the first major milestone: Panels eco-system roadmap: Milestone 1 (February 16th, 2016)

MustangGB’s picture

Have a feeling it's meant to read Feb 2016, not 2015.

dsnopek’s picture

Issue summary: View changes

Ah, sorry, you're right! Updated the milestone to be 2016. :-)

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-12-15 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-12-22 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2015-12-29 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-01-05 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-01-12 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-01-19 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-01-26 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-02-02 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-02-09 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-02-16 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-02-23 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-03-01 - #drupal-scotch on irc.freenode.net

yanniboi’s picture

Issue summary: View changes

I have added a link to our Meta issue for porting mini panels.

dsnopek’s picture

yanniboi’s picture

@dsnopek ta :)

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-03-08 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-03-08 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-03-22 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-03-29 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-04-12 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-04-19 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-04-26 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-05-03 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-05-17 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-05-24 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-06-07 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-06-14 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-06-21 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-07-12 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-07-19 - #drupal-scotch on irc.freenode.net

dsnopek’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-07-26 - #drupal-scotch on irc.freenode.net

samuel.mortenson’s picture

Issue summary: View changes

Added notes from today's meeting: 2016-08-02 - #drupal-scotch on irc.freenode.net

japerry’s picture

Issue summary: View changes
japerry’s picture

Issue summary: View changes

Added notes from the 9/13 Scotch meeting.

japerry’s picture

Issue summary: View changes

Added meeting notes.

MustangGB’s picture

Trying to track the latest progress/readiness but struggling to find any updated reports.

Did the meetings stop?

DamienMcKenna’s picture

Sorry, we have continued the weekly meetings, we just forgot to keep the meeting notes :(

Michelle’s picture

The scrollback in #layouts on Drupal Slack currently goes back to January 26th so you can catch some of what's been going on if you join and read back.

DamienMcKenna’s picture

Status: Active » Fixed

8.x-4.0 is out: https://www.drupal.org/project/panels/releases/8.x-4.0

Marking this "fixed".

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.