Backdrop CMS Weekly meetings, 29 Sep 2016

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Backdrop Weekly 9/29

Description

Today’s development agenda: http://bit.ly/2cxcn42

A

Hello, everybody welcome to the weekly backdrop, call it sep, tember 29th 2016 really excited to have everybody here today and talk about the future backdrop.

A

Everybody here today and talk about hang.

B

A

I've got it, I've got it sorry broadcast problem.

B

A

Okay, general announcements, Kalibak Kalibak, was released final version. It has native backdrop, support we're working on getting our docker image all up to date. So that's when you use kalin box, you'll get the latest version and backdrop as well, but Calla box has always had a really excellent backdrop support. So you can install backdrop through cala box really easily it's up to date. Oh and.

C

B

C

A

We'll play 5.0 awesome, so latest version of cala box latest version of backdrop, and you can use you can actually use the docker image directly without Kelly box. But Calla box makes it's nice and easy and integrates with things like Pantheon, which is really cool. You can donate to backdrop visiting backdrop, CMS org slash, contribute and you can get an exchange of. Thank you dragon hoodie or t-shirts which there are samples of at that URL.

A

If you join the backdrop, contribute I see that we've been getting some nuclear trip authors in the past couple of weeks. You can get a free phpstorm license to use or open-source developments. If you're interested in getting a phpstorm license and you're a member of the backdrop contribute. You can email us info at backdrop, CMS org, and we will hook you up with a license updates from the project management committee.

A

We have a group of individuals that are responsible for setting the overall direction of the project and every week, if we have announcements from the pmc than we see them here and this week we actually do have an announcement which, if I give full extra intro, we have an announcement that we took a vote and it is has passed about implementing a feature freeze before before releases, which would be helpful so that we don't have the last minute.

A

Cramming like we have for every one of our six releases, but we're doing it really a pretty modest feature. Freeze we're only pushing it two weeks out 14 days before and that feature freezes literally feature freeze, it's not actually a full code. Freeze. It just means that the the wording of its I don't think we published yet. Is that right, Jen, sorry, I'm you to do the exact wording of it. We.

B

Haven't written any wording anymore official yet, but I put something somewhere. I think it was in that issue I'll go grab it yeah.

A

It's basically staying if it's a feature and if it's tagged as a feature is such an issue queue. We have to merge it before the two-week window before release and then, after once, we've entered into the feature. Freeze, all new features, any issue tag to the feature can no longer be merged, which is completely reasonable, will still be able to do things like fix, bugs change strings those sorts of things all the way right up until the release.

A

So it's a really pretty modest policy just to keep us from doing a whole lot of crazy merging the day before release.

B

So I found that I found the wording and this actually came from Wes I just modified like one sentence, but it says two weeks before release any issues tagged with feature requests in the point. Release milestone that have not been committed will be bumped to the next point, release milestone. After that point, we want to focus on the features that have been committed, get them finished, tested and fix any bugs before we release.

A

Great and we have yet published that on the website is official policy. I. Imagine we'll put this into the handbook. Probably under release cycle would make a lot of sense where we already document our regular, really schedule and the way that releases work. So that's a to-do item, because that vote was pretty much just completed.

A

So let's go into the next item on the agenda, which is infrastructure tasks. Those are things around backdrop to project that aren't necessarily the software itself, and the first item we have on here is bankruptcy. Ms, with pantheon / brush / updating with an update from.

C

Yep, so we have it: detecting pantheon is detecting a site, local drush installs, and you can definitely use josh commands through terminus. But when you like check to run update when you're doing a code, merge on pantheon dashboard doesn't seem to be picking that up so I think the next step is to ingress. He seems to be on board saying that rush is working with the Pantheon backdrop instances, but I don't think he knows specifically that checking the dashboard doesn't seem to your running, update dot PHP, for example, yeah.

B

I posted in that issue last week in like tested a whole bunch of different things with the dashboard. The clearing cache is didn't work, running, update, didn't work bunch of stuff and I asked my eyes open an issue in the like Pantheon world for the dashboard, and he said we should open an issue and then respond to him with like a ticket number or something or half the Pantheon people do it. So he knows it's not working, but we don't know why. Oh I.

C

Think I did that open the Pantheon ticket and he responded back in the backdrop issue on github and he has an example of brush commands being executed, but I don't know that he did that through the dashboard. So I on me I think to update it and say specifically through the dashboard. We don't seem to be getting responses.

C

B

My mom had a bunch of screenshots, so it should be clear. It was the dashboard that wasn't working, but that might have been a different issue too. There's like a yeah.

C

Yeah looks it looks like his response is using like a site, alias yeah. This.

B

Is working as well, which is why the dashboard is some kind of crazy magic and ah it's not.

C

Rookie so we'll just bring it specifically to his attention that the dashboard part okay sounds good.

A

Okay, excellent great. The next item on the agenda is, this is actually kind of related to the software, but creating a checklist for every release so that we make sure that all of the tasks around that release are completed and Gregory clones made a really excellent checklist as a demonstration issue. 22 26 for the 1.51 release, which is looking really good, actually I really like this idea. But the idea is that will make a checklist in the procedures repository.

A

That is basically the things that need to be done for each release, and then we make an issue, copying and pasting that checklist into the issue, queue and then check off the items to make sure that every single item gets completed, and that includes because it's actually quite a bit of things that end up happening- tagging the released updating the home page on bankruptcy, MST org release, notes, announcements newsletter for some of them updating pantheon, for example. We just talked about the docker image and oh actually sending newsletters as another item.

A

So I think this is great, because the number of things that we've got keeps increasing as we have more additional system and channels through which backdrop is distributed and making sure that every one of those tasks gets updated after every release is a great thing for us to be doing on an official basis that looks great I. Don't think, there's anything more to say about that, though other than it's in progress and second good. Well,.

B

The issue was, we need to finish that stuff, oh, not to create the list, but to actually do the things on the list. Okay,.

A

Well, that's that's a great idea, and so where it looks like I've got this down below, but it looks like we're suggesting that we won't push up to Pantheon. Tell 151 is released. Is that the plan yeah.

B

And that was just something we'd been doing historically, because if we push a first release and then everybody updates it and then we push a follow-up release like a week later, then everyone gets mounted to updated again immediately when we know we can fix those bugs I, don't know if that's a like a process, change that we should like. We should just push every release, ah but that's what we had been doing. So that's what the list says.

A

Well, it's possible once we implement feature freeze that will have more stable releases on day one, and maybe we can start pushing them out immediately, but I think for now the slow rollout is not a bad policy. People can always update their own pantheons if they wanted to immediately, but yeah I think waiting a little while is not not a bad policy. So far, okay,.

B

So, let's leave that for this one and then for 16 we can change it. If we feel like 16 is stable from then on out, we can do it the other way. What.

D

Happens if you updated yourself on pantheon, like you just update your system, but it's still connected to the upstream. What does it have? Conflicts conflicts? Let it actually, then you try to do the upstream interface I haven't.

B

Had any yet like, usually so, I've done, that a couple of times like I, have a couple of minutes: I starting 15, now and it'll. Just merge politely like you'll, still get prompted, but then I haven't had any like. Someone actually does that. Okay, yeah.

A

I think it's it's it's using get underneath the hood, but I think it also has an additional layer of logic on there. That is a little bit more aggressive and automatically resolving conflicts are.

B

Students with it yeah.

A

Okay, let's see the next item on the agenda is infrastructure tasks Jen? If you want to take it.

B

B

No, we already talked about a couple of these infrastructure, so we're on website. um So we are trying to figure out how to make these weekly meetings less repetitive and more productive for all the people who are attending.

B

So what we did is move all of the web development tests into the outreach meeting last week, and then we wanted to move the web development tests back into the weekly meeting this week, but I couldn't find them so I just dropped in the three that we're most important have to go back like two weeks and find him I jump in the three that were most important.

B

That I think we should talk about, and that is the number one thing that people ask for when we tell them about backdrop is for a list of sites that are running them or showcases about site people that are currently using it. So that's the number one priority for the website number two priority I have here it is documentation because it is so almost done and we already have this very comprehensive set of documentation for almost all backdrop- and I know Tom's working on reviewing it.

B

Doc well, mike has a plan for how to structure it. We've got like an entire team working on cleaning it up, we've got clonus in serving screenshots and it looks fantastic and I would love to just get that to a point where we can link it in the menu and I think it's almost there and then after we can get the documentation done, which I think is right around the corner. I want to focus on setting up the forum, um which is something that I know.

B

People clamoring about four years be making a place where people can ask questions. Is that backed up and talk about it that isn't necessarily github? We've got a couple of issues already going on and github that maybe shouldn't be happening in good, but that's the only place we have for it. Go and I know that I think dr. Ellman has done a ton of work on the forum module already to make it work for backdrop. He's got a pull request in the core cute just that we could get a sandbox to give it a test.

B

So if my own wants to give that a test on forum is going to be next on the list too I'm hoping that we can get it documentation out of the way here quickly.

B

So that can be our next focus, but there are a ton of other things, so we're working on a lot of blacktop CMS, don't work the website we're thinking about doing some kind of a designer fresh from the home page, since back trip has been out for two years trying to make it a little bit more um compelling at, but we need so it's got. Oh I've got a meeting with a content strategy. Marketing guy I think it's next thursday. Yes, I know.

B

You said you want you're interested in how that was going to go um I'll. Send you an invite to that and see it was supposed to be last Friday, but I had no horrible meeting that had a wonderful meeting that ran very long but yeah. So we rescheduled I'll get you on that. So you, if you can come if you want um and then hopefully we'll try and figure out like exactly how to what to do to the website, to make it um better do a better job of telling people what backrub actually is.

B

We also have some problems with module, seats and layouts to find pages, which I think are actually less of a priority. Now that we have project rouse room floor, but I would love to get image support in there somehow so far it seems some layouts to you can actually see what they're doing um and then I there's other stuff going on on back to be honest, org I, don't remember! Oh we've got github integration so that you can sign in with your github account, but I think that needs to be tested.

B

It's kind of stuck in a like. How do you test it if you're not allowed to test it for your local site um in yeah? There's other stuff I, don't remember, but I'll eventually find those two tests that they can put it back in the agenda um but yeah okay. So we move on to backdrop CMS itself.

A

Neat, do you want to take it back? Yeah, sorry, I'm meeting. So let's talk about backdrop so backdrop 1.5 k max two weeks ago, which was fantastic I. To probably our least say it that way, our most stable, minor release that we've pushed out because there hasn't been any any really serious issues with 1.5 release. However, we do have a number of items that attract 4151 and a list of really rather important bug fixes that we're prioritizing.

A

So you can check the issue. The tractor / 151 issues, just by looking at the 141 miles done and most it would something then working well. A lot of them are getting new things that we have it like a little issues of basis, CSS fate.

A

The items that are slated as important bug fixes basically those that are so important as soon as we fix any of them. We will probably make the next minor relief or the next boat fix released. We've got four of them slated here in the agenda. One of them is issue. 22 19, which is images, are not able to be inserted into custom blocks, which is really ironic, because we did a lot of work to make it so that xx and that exact thing actually works properly.

A

But what actually ended up happening here is that images are available to insert if you insert the block through the layout, you lie. But if you go over to the custom blocks, you I the ability to insert an image has been removed. So we got it half right.

A

So, basically, it's possible as long as you go through ways of adding and configuring a block, but we need to make it so that if you go through the custom box, you why you should also be able to insert an image through that interface so that one's really pretty trivial I volunteered to take on one on today, I think that'll be pretty easy to fix.

A

The next item we've got is that a home page layout is not set to drop down. This is because the we added this ability to have drop downs and we added a home page, two layouts, but we did them in such an order.

A

That's I think we added the home page personally had to drop down so later that the home page didn't get updated to include the drop down menu capability out of the box, which is really confusing, because you, you think that it would work and it does work on every page except for the home page, and so it can be really a really friction fees.

A

So the nice thing is that one's really trivial to fix. We need to change the settings on the the primary menu block in the home page layout, there's already a poor request for that, but it's been brought up that an update hook would probably be appropriate because it's really unlikely the people would have set their homepage primary menu to be a hierarchical drop or a hierarchical tree, because that's the option that makes the least sense, even though it was the only option we ever had before.

A

I want to call out just as an aside how excited I am about the drop-down menus and in particular the CSS there. The mark-up clean up around that that now that we have this drop-down style instead of the hierarchical tree style, I Urkel tree Styles. What added all of that nasty CSS that added the little arrows and the docks and the leaf and the last and all of that crap yeah. Exactly so now, when you change the style to hierarchical or top level, only the CSS no longer affects your menus.

A

So you don't as a theme, you don't need to undo all of that crap, which is just so great.

A

I'm really excited about that. All the classes are actually still there, but the CSS now targets specifically the tree structure version, so there's a specific class that is added for hierarchical tree or a top level only or dropped calm, and so you can target each one of those Styles individually, very exciting, and for 1.6 we were hoping that will expand that out to a more comprehensive ability to provide other types of menu styles. But for now these things are hard coded as those three top level drop down and hierarchical tree anyway, very exciting.

A

Anyway, we need to fix the homepage layout to use the drop-down. That's the issue, and that number is 2222.

A

Let's see another item on here, the Installer manual upload of a module zip file doesn't work, that's issued, 1920 I would say this is an important bug fix it, but it's been stuck with us for the entire 1.4 release. Ever since we added the ability, or ever since we added project browser this one's a tricky one. At least I I couldn't figure it out on my first pass. So anyone that has the the time and interest to figure out to that problem.

A

That would be really great one to dive into, because it's it's a little tricky as something to do with the fact that our module upload in the installer is in a dialogue and uploading. A file uh from within a dialogue is causing some particularly weird problem, so I'm not quite sure how to describe it, because I also hadn't been able to figure why it was happening.

A

Let's see in the last item that we have here as far as important bug fixes we'd like to make it so that the basis theme provides a full bleed hero, probably through overriding the homepage single column, template for the layouts. But it doesn't look like in the agenda here. We've just got a to do basically for the issue number. Do we have an issue for this? Yet, just as anyone to worry west's is nodding.

E

It is um 2190, is the issue number at a couple, other ones that I think are important, but they're all in the project for a basis? So quite a few of my poll requests there's one where.

E

Basically, for really boring reasons, if you override skin dot CSS, it doesn't override some of the components that were being added in template: dot, PHP the CSS being added that in template, dub PHP, so I moved everything into the info file because fixing the problem any other way would be really hairy and there's really not that much CSS that wasn't in the info file so and CSS performances is like ridiculously good, so we're not really losing out on anything and then there's an accessibility fix at some point.

E

I was smoking a lot of crack and put a px font size on the body tag and I shouldn't have so fix that and then the other one is oh.

E

No ok, the other one I just meant I mentioned backwards, so the other one is a when you override skin debt CSS some of the image links broke and that one's kind of a weird one, if you override skin that CSS, basically we're going to have to expect that someone copies the images folder from basis at least, is the starting point and they can manipulate how they want. But then the status messages come from a core folder, so that gets really hairy. Really quick, I think I had a fix. Oh yes, I did.

E

I did have a fix that I think is good enough, but I feel like maybe we could do better so that that one maybe need some of you and then I added some documentation of basis. Yeah.

A

Didn't you, you started using a github board. What are those call the project yep, but for all of those things? Maybe we could just like that here in the agenda yeah, we have yet to actually figure out how to effectively use the github projects. The integration isn't the greatest between the issue, queue and the projects, but but I think it's fine right now we're basically just kind of experimenting with how well those work and what we can use them for anybody right now that has commit access to the issues.

A

Repository can also create a project which is one of those. What if one of those boards called there was such a Kanban board yeah hmm anyone can create one of those, and if you have a good reason to do so, I would say: go for it because I think experimenting with how we can most effectively use. Github spreadability is the only way that we're going to figure out how we should actually use these in the first place.

A

B

A

B

Wants to play with those and you don't have commit access to the issue queue. Anyone who adds a comment is supposed to automatically get access, but for some reason, I think that um robot task is not actually firing. You have to create a full request in order to get commit access. So if you haven't created a pull request and you want them to access, we can just add you manually now so, if you're watching this and you want to play with it on low, stop.

A

Okay, that's it for the important bug fixes section and so now we'll talk about the release. That will be four months from now: the 1.6 release, which is scheduled to be january, fifteenth 2017 and, as noted during the announcements face. That means that we will have a feature for use on january first 2017, so we've got a number of items already slated for the 1.6 released. Some of them are items that didn't make it into 1.5, and some of them are new, the first of which is adding a reference module. Two core: that's issued 1301.

A

We did a lot of work on a reference module, or, I should say Mike did a lot of work on a reference module in the last release, but we were unable to get that integrated adequately in core in figure out what to do with our existing reference modules and an upgrade path and all of those things so uh yeah actually I have an update thing. Yeah.

D

Actually, it goes nearly as far as I want to in the last less cycle, so I'm definitely doubling down and doing it. This one, the one thing.

D

So what I'm trying to do with the module is make it so since we're can make changes to the entity system slight ones at least add additional information about all the core entities. What I want to do is be able to have the reference field be able to reference multiple different entity types in a single field.

D

So if you want to have an event or something and related to things and link both like places and people in the same field, how to be able to do that, the actual data storage- for that isn't that hard the field entering values is not that hard, but the place where I'm not sure how to handle everything is the views integration because it would mean you know, I'm joining a whole bunch of additional tables and if you were, and all of the fields attached to all of the different entity, types that that field could reference.

D

Oh I'm worried that it would be get overwhelming for the users when using vuze, so I just have need to think about that some more and actually play around with things. But if anyone has any views, integration experience I would enjoy help with it. So.

B

One thing we were talking about in the look in the last cycle was that that being able to reference different types of entities is not a deal breaker for core like if we can only reference nodes, our users separately. That's fine, because those are in the same tables and abuse integration. It's busy there if we need to add this other thing on as a control later, that's totally fine, and it's like that for for look down the road.

B

So it's a you know now that we have a little more time we can play with it a little bit, but it is not necessary for for to get that into yeah.

D

It's not necessary, but yeah I think this could be like one of the things that could distinguish. You know backdrop from you know drupal in terms of actually providing some more functionality and making more sense, but yeah. If I can't figure out the multiple entity type targets, then yeah, we should definitely just check the version where you can just heard it. One entity hyper this next release.

D

B

Okay, so I know we have we have a new plan in place for or we may soon have a new plan in place for how to work on like huge features that are going into bar and we'll talk about that a little bit more next week. um But it would be great if we could get uh I, don't know, I kind of I think we have a new renewed focus on ND references.

B

However, whatever this turns out to be in the long run, um I would love for us to be able to test our new like adding big features to core policy procedure, whatever it is, we're doing on this feature and see what I goes for 16 I know: West ran into some problems with our current process. For that trying to add basis 15 we ran in some previous issues and 14 with layouts and stuff.

B

Then, if I'm going to go in at the last minute, and so I would just say like through this cycle, everybody give us as much feedback on how this is going as possible. We want to make it so that we're um not putting too much pressure on the person that's responsible for the feature, so it's not like all West doing basis, all the time in all Mike's doing at any records like the more we can offload the work and make it easy for people to know where they can help the better.

B

um So if anyone has an idea of like maybe we can use this new project feature and github, it would be great to get feedback on like how that could be useful, um just to kind of make sure that we're using the tools that we have the best of our ability and not overloading our people in the process.

B

So keep that in mind um also, we don't so currently. The only feature we've got slated for 16 is references because it did get pumped from 15, and but there were a couple of other issues in the 15 cycle when we started talking about other solutions to the same travel and one of the things I added to the list was trying to figure out how to get some sort of a um file entity UI or a media.

B

Brow or whatever wordpress calls there upload an image dashboard thing I'm going in backdrop, because that is something that is a big issue. It's kind of a big call in terms of something to your boss, often backed up. Doesn't it's something?

B

That's really important to our kind of wordpress style users, and we don't have a clear solution for how to solve that issue in backdrop, yet um I kind of don't want to put this media type solution thing on the list for 16, because I would love to focus on and any reference first I think that coming up with some kind of smarter entity solution will also help our media problem, especially if we end up with more of a file and a bee-like solution.

B

There, too, and so I put this on the agenda a couple of weeks ago that adding a media file entity solution for one sex but I'm now feeling like. Maybe we should push that to the 17 I.

D

I definitely think that doing file entity would be yeah great. For this upcoming release, I mean mostly pieces. There are there on the back. End is basically just creating user interface that exposes the file entities to the user of them to like manage them up. So what if more document you at the same time.

B

As the entity reference thing or do you think issue? Oh it's.

D

Entirely separate they don't really they don't really touch like you know. Both of them are accessing. Basically the entity API, but the entity API is there for the most part. So it's basically just especially the filed stuff is just exposing stuff. That's already there because we already have file entities. We just don't have a user interface for managing them. Okay,.

B

Well then, maybe I'll even 16 um and we'll see how it goes. Yes,.

A

But on I was gonna say the same thing: the thing that, where it will get a little bit blurry, is whether or not we want files to be feel double, but that can be an iteration like we can add the UI for managing files, just that you can find and delete them and update them and whatever and then potentially making them yield Bowl, which is part of a file entity and Drupal 7 that that could get a little bit messy.

A

But we knew one thing at a time add the user interface for managing files feel double, possibly and then, like the in browser abilities like media module like stuff. That is almost certainly going to take a more comprehensive effort. Sup yeah that sounds.

D

Like Oh a good plan, okay,.

B

A

Jimmy continue Jenna yeah.

B

A

Okay, the last other end we've come in here is the rich text, editor meta issue, which is issue 1087 we've got.

B

A

Load of ideas to make the rich text editor experience better. We fixed a number of bugs in the 1.5 release, which was fantastic, but there's a lot of features and abilities that we can do in in the rich text editor. That would make the experience a lot better things like drag-and-drop, uploads or copy/paste uploads, and adding support for things like code tags, those sorts of things. We did really improve a number of items in the 1.5 really especially me out of box experience of the editor configuration, but but there's a lot of things.

A

We could actually do feature wise to make that British exit or a lot more powerful so that issues in meta to 1087 and there's a lot of ideas within their of things that we could potentially improve more items. Tbd I.

D

One more item that I'd like to add- and we just have a we- have a ticket number 1886, it's the one about reusing blocks of different layouts, that's actually bit something that I've been looking to like propose ideas about for a while and finally, the discussion came up, so there's sort of several different ideas of how to handle it so that when you have one layout and then you've flown it or create another layout that you and actually have the same blocks across small glass to your site.

D

So you know there was the idea of having block instances and set a main block and then copies of it or I was suggesting a region inheritance where, when you clone a when you clone a layout, all the regions start off like inheriting the the contents of the original until you override them. But anyway, people maybe should check that out. Maybe we can get something around that improvements around that into the next version. Yeah.

A

That's a great idea, actually there's a lot of fantastic ideas in that issue, ranging from something like many panels like thing or yeah, region, inheritance or block collections.

A

All kinds of credit use, because that is a big issue, and the funny thing is, is that some of those, maybe even a lot of those items, could be implemented in contribs different options to do the same problem. But some of them are definitely core like courtroom and ideas. So yeah.

D

I think I think I think part of the discussion is. Is we need to be careful about not only what we do implement as a thread, but what we don't? Just because some of the ideas could provide like a lot of extra complexity that wouldn't be good and yeah.

A

Totally, okay, yeah thanking God, um yeah I. Think that would be a great issue, I'm not sure extra. We don't even really even have an official process for deciding major critical items for minor releases. I mean, I guess we could take a you know: take a poli amongst the people presence, but yeah I think previously just kind of been. You know we're feeling strongly about this. Let's add it to the jinnah, so I guess that was that. That is the process. So there we go.

E

D

I guess he could have a PMC vote, because that sort of seems in the project management committee could do yeah, touche deposit just to give us something to do.

A

Okay, yeah, maybe actually we have an entire thread just around all of these and then work out. The overall agenda, / release.

A

Excellent well yeah. Another great issue, there's also a bunch of issues that are just tagged for the 1.6 release, features that we think would be attractive but may not be of super high importance. But if we get them done and that's fantastic, you should check out those by looking at the 1.6 milestone on github.

A

And, as always, even hit up, bankruptcy mastered, org, slash roadmap for the overall climbing strategy of backdrop for 1.6 and beyond I think, mostly, it's actually a to-be-determined for 1.7 and and thanks beyond that, but to get an over at overall idea of how far backdrop is common. When we're heading and check out that URL, let's see, that's it for backup the product, any other additions or anything, you guys want to bring up I.

B

Want to say thank you Tom for volunteering to help us with all of our documentation.

A

Ok, so the next section is community growth and normally Gregory. Does this section but I'm not sure that it's I updated it I noticed I? Wasn't he ok? Do you want you want me to give the rundown then all.

B

Right it looks like Jeff updated it too. So I was looking at and I'm like. How is this number not changed by discuz here together? Thank Jeff I'm sure. So, let's see since our last backdrop meeting we now have 315 total kinship projects for backdrop. That's too, since the last time we talked about it, we have 230 with official releases, which is plus one. Since last week um we have 369 releases on backdrop, CMS org.

B

So that's two since the last meeting and those are releases that, like our four previous projects of products that are getting updated as opposed to products that are new, we have 51 total control authors. We've got one new person since classic and that's Daryl, so welcome Daryl's backdrop. I think he poured the restful module from Drupal 7, so open a lots of that for Becca job. It.

D

B

We've still at 15, pending applications since we're problem with saying people to apply to year ago, or so, damn good back, and we have 30 organization profiles now on backdrop, CMS org, which is three since the last meeting in 370 user accounts on backdrop, CMS torque, which is a 10 since the last game, and then Jeff. Do you want to do backdrop download, since you have two number.

C

C

6624 downloads of backdrop, CMS + 145, since last meeting.

B

That's still super impressive: we had a huge boost there after we released 15 I still think people are excited about it and that's why you've got this big bump in downloads, so good job, everybody.

A

Okay, next foot, all right so upcoming events, you can check out back up CMS org, slash events for a list of things that are coming up, the first one on that list.

A

I'm sugar, many of us are excited about which is bad camp, which comes up October 20th through the 23rd at which there will be multiple backdrop, things we've got I think multiple sessions, even maybe, but we do have an all-day summits and an all-day training, so we'll have two full days of that job fun at bad camp as well as sessions during the actual camp itself. So it's going to be really exciting, Jenna of course, or local. So oh and Mike are local, so we'll all be there. Oh and Luke.

E

He was getting everybody, that's in the area, I.

D

Have to fly in this year at oh.

A

Yeah, that's right! I'm sorry, you're, not local anymore!.

D

I use it I used to be local now I have to know how to fly.

A

Well, anyway, bad camp will be great. A great event for backdrop is but there's also a lot of other items coming up, actually drupal south another advent it which there will be a mac drop project committee. Member gregory clonus will be there presenting on backdrop and then lots of things going into november and year beyond, there's also an ical feed. If you're interested you can get that from the events page on my tribe, CMS, Todd org. Oh.

D

A

D

Add the summit and stuff onto that because I just look at the dates and right now it's just as the usual usual this meeting scheduled for Thursday.

A

Yeah, it's good idea to be a little bit more comprehensive about. Oh wait, no you're saying the events aren't on the calendar at the ical feed right.

D

A

uh Jen dude I know about that yeah.

B

I can check there are two ical feeds. The meetings shouldn't be on the events. 10 I.

D

Just looking at the meat anyway, but then we're probably not having this regular meetings which might remove that from the meetings one unless we do want to have a meeting. Our of the summit Oh.

A

A good point that there may or may not be a meeting that week, I might just call in sometimes I think we've done some. Where is the things like that? We.

D

Could set up a computer at the summit tooth, but then I want to call in and look at it maybe take part remotely or something you could probably get something out right. Yeah.

A

Okay, Molly John I'll leave that to you manage the calendar.

A

Okay, that seemed to the agenda. We've got up in a Q&A session or general discussion. Anybody have anything that they would like to add a free map that we haven't mentioned so far. I'd.

C

Like to put on the table for either 1.6 or something some upcoming release, this issue I just put into the chat their number 100, which is a basically a URL list entity whether that becomes a few little blocks or something like paragraphs module. Basically, one use cases like if you want a slideshow view and you want so that's a view of entities that have like maybe a picture in some text and I read more link, but you don't necessarily want a URL to those things. I always have that use case.

C

So, thank you go up for a vote for 1.6 or 1.7 with the PM substructure you guys are proposing it. I would be for that home yeah.

A

I wanna reiterate that it doesn't need to be a priority feature for it to actually be implemented in a minor release, anything that is completed and like just desirable enough week. We can include it and anything at any time. It's just that the featured features are really just to provide a focus for it for every release. Some things like project browser, for example, wasn't you know a focused feature, but then it got in anyway because it was.

A

It was a great feature and it was ready at the time but yeah, that's not to say that that this isn't important as it noted its issue. 100 we've been talking about this. Basically, since the beginning, oh yeah I think we actually have a lot of indecision still even on the approach that we should use so yeah thinking about the you know the approach and if we can come up with a battle plan, that would be great as a first step.

A

D

The other thing we might want to do, rather than concentrating because I think a lot of the discussion is around what to call these page lists entities, maybe even just providing like an entity builder that can build any sort of entities through the user interface. So we don't actually have to name it. You could just say, create new entity type or something like that and then create like slideshow, so rather than rather than blind, kids will create bundles of a certain entity, types that were create.

D

We could just actually create allow for the creation of new entity types through the you I would that work I don't know, because, because I'm not sure if they need classes or whether we can just like you know actually in code or not, but that's just an idea. I.

C

Think I, probably my favorite approach that I've seen so far is feel double blocks. And then you know people can make new blocks and they can place them in layouts if they want to and if they want to make a block they're going to use to make views out of that's fine and we don't have to introduce new vocabulary. I mean XD is not new vocabulary, but can be confusing for people. I think.

B

A

Think it's have the word entity.

B

Anywhere in the UI but sure like what it, what is it I, don't know like there are some really crazy things. um We're gonna need to figure out a long-term like um which issue was. I was talking about with talking about like we're turning tomorrow, vegetable 60 architecture, where all of our entities just the king. No, it's no different kinds of notes, we're in like taxonomy term sort notes and like trying to simplify all of this crazy objection. We got in drupal 7, where it's like. Okay.

B

Well, maybe the note just fest settings like whether it does it have a page or just have an automatic view like a tech sonometer, and is it in a reference field like a taxonomy term like there's a whole bunch of stuff? That is really all the same, that we've separated and different for some reason, but I'm not really sure some valid reason, and so then, if it's all just going to be no, it's like. What's the difference between a block and a note?

B

Well, just as a pat, so that's just like I setting I, don't know like trying.

D

To record whether.

B

We want to make it more complicated with like build your own entity for everyone, making more less complicated, like I'm. Looking I'm like I, like it I like.

D

A lot of the stuff that triple seven did with entities and I think that it sort of was an additional level of abstraction that was needed and it makes stuff like the entity reference field and views just a lot easier to build. So I definitely wouldn't want to get rid of that. If anything, I would say, let's get rid of nodes and just call them pages and page types for a backdrop for backdrop to just because it's.

B

A page two, um it's just a pinch, Ethan reference in an entity, reference field.

D

Okay, but pages are pages and then text on me things. You also have a page I mean we might not even need to that. Like you know, we're may taxonomy pages like actually a view instead or something like that. You know, because really it is.

B

Just a taxonomy term is scalable anyway,.

D

But I mean I'm not saying that I'm not saying the other entities can't have their own page I'm. Just saying like it would be it kind of makes sense to rename nodes just pages and page types, so you can have a blog page type n day, like you know, a huge.

B

Time, yeah page 2, I think ph is too loaded to term I'm, not sure, there's a right answer to this problem. I'm just playing devil's advocate here, but I'm saying it was like. I do not want to add more complexity if we can solve the same problem by removing complexity- and I don't know how that's going to deal with the user interface. What.

D

B

D

Mean I mean either like I would say: either we should remove node and just call them pages, or we should call like all these custom entity contest, custom content, size nodes and not have a separate entity for these and isn't for these. Like knows without pages, you know it's like we should go one way or the other, but not both anyway. This is a whole discussion. I think that you should we should have the drink. We should drink, discussed one issue at bad camp that.

B

Sounds like a good idea. Maybe we should devote like an hour of the summit to like an ageless node like brainstorm. Yes, it's a great idea. I'm! Writing it down. Yeah.

D

Maybe we should actually have other people suggest. Other things to talk about. The summit. Do with people have ideas, yeah.

B

Do you have ideas, won't even have idiot I can.

E

Rant about cssa at you all! If you want that.

D

What well we might we might be, let's, let's frame it this way, we might want to actually have like a discussion at the summit about backdrop to and start thinking about where we're headed with backdrop to so, we can actually start heading that way and then think about where we're going so- and this is sort of part of that discussion- that.

E

Would be great, I have front-end ideas for backdrop to that need sanity checks from non front-end, be people that.

B

Would be great, maybe we should give up like, rather than it being in page, less known our. It should just be a backdrop to two hours or something, and we can talk about everything that anyone wants to do in the future and try and figure out what our path is. So to get there and also a time frame too. That's something we haven't started. Really thinking about is one.

B

Are we going to do a factor of two because there's so much stuff we can do 11, um but also with the whole minimal amount of change saying. Maybe we should try and do it too, with minimal change and see what that feels.

B

Like so yeah I think that's an excellent idea, and just so you know, I haven't put anything up yet is scheduled for the summit, but I have gotten a bunch of speakers, um so people who own websites to want to do a little kind of talk about what backdrop has gotten them by having it. People built websites like to developers from other development chops talk about what they like and don't like about backdrop um I'm going to get a demo from the cowl box, people I'm hoping to get a demo from the pantheon people.

B

So if anyone else wants to tribute I, don't know Mike, if you have something in particular, you wanted to talk about would be great to get you up. There, West is going to do a little talk about sub Fenian basis, and so yeah I would say anyone unless you contribute anything. We've got a bunch of people lined up with your to rearrange like the schedule to it makes sense, but yeah for sure will be great to have more people talking about more things. I think this is a fantastic idea for the afternoon to like.

B

If we can switch to a debate during the nap time, our I think we can prevent people from falling asleep. So.

D

Like that, the base yeah, backed up to in debate you and I, can get up a debate. Lots of stuff, oh yeah,.

B

Don't be great literally like.

C

B

Tap way through, though, put.

C

A put my head gotta put field, you I as a bullet point to talk about for backdrop to that's complicated and we need ideas of what users want. Yeah.

B

D

I would say, I would say, abused you I to view suck, but we could also I'm not sure that doesn't require an api change if we change the UI, so that might not need a full version released, but still something talk about yeah.

C

It's talking point.

A

Okay, well, that's where I guess we started a little late, but we're approaching on one hour mark. Let's call it for the end of the official meeting. We're going to stay on after the broadcast is ended to talk about agenda items for next week, an adjustment to our normal weekly schedule. So, if you're interested in setting the agenda for next week and how big flash that then please stay on, but otherwise thank you. Everybody for joining think you're, ready for watching and see you guys next time.