Backdrop CMS Weekly meetings, 7 Mar 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Backdrop Weekly - Mar 7

Description

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

A

All right we're on air, it is Thursday March 7th, and this is a meeting to check in on active development tasks for backdrops amis. Before we get into the core software itself, we would like to welcome KS Thomas to the community, he's created a maintainer application, stating that he's created some new modules for backdrop and wants to be able to put them into the repository. So thanks for working on backdrop modules in the last week, we had a couple of security updates for kinship projects and a new project prism, which was just released yesterday.

A

Weighted related to the website backed up CMS to org. We have updates for the magis names and layout pages and the tugboat installer that we covered in the last meeting. So we're not going to do that again, but we have a new issue here: issue number 501 to talk about our security release policy. This is something we had a pmc vote on two weeks ago and we just need to figure out how to properly document that decision somewhere on our website.

A

So we just need to figure out where to do that, and I also thought it might be nice to write a blog post about security, along with the update that we could kind of drive you people to hey, here's all of the information about security, and we could also include information about the security team, in particular how we handle security releases to can trip just so that all of this information is out there and publicly available where people can find it. Does anyone have any suggestions as to where we should put this stuff.

B

Sorry, you said as a paints on Google Talk yeah.

A

So we have a security page yeah.

A

We could update that yep.

B

C

Good I'm, sorry I think it should go. Okay,.

B

Now that you brought that up, it seems that over the past few weeks, we sort of like have an officially created a contributor team. So.

A

I noticed that you put the word, contribute the security team on the security announcement last week and I deleted it, security team, yeah.

D

A

Out, like I, think right now, there's just one team, but we should figure out if we think that should be split into two and if now is the time to do it, yeah.

B

So mainly was separations of concerns. I guess that any core issues should not go beyond beyond the team that works on them, as in the rest, should be on a need-to-know basis, and if we don't need to know or work on them, then we shouldn't.

B

So basically, the core team now is the core committers right. So Nate is it. Is it you and who else well.

A

So the way it has been going is there's people who actually see the drupal.org issues and I think right now, that's only neat and then there are people who helped get the Drupal thing ready for a backdrop, and so far we have like six or so people who help like apply the patch test. The patch J Franklin will apply it to silkscreen and we get a feedback on it that way.

A

So there is quite a large team of people who are involved in assisting with getting that core security release out that aren't necessarily core maintainer x'. Okay,.

B

Fair enough yeah, actually I, didn't have silkscreen on mine, but it makes perfect sense now that you say.

A

The contribs I think is a little different, because the core security stuff is always done before. Drupal's announcement comes out and then we co release at the same time or at least attempt to get it as close as possible, sometimes just a couple of hours difference, but we usually get out on the same day. The contribute thing rather than being proactive is reactive, as we talked about last week, where we have people who keep an eye on all the security updates that come out every week and notify people who dr.

A

up maintained, airs if their projects have updates. Now we go one step further, will actually issue a security update for those context if the maintainer is unreachable, and so that could be a completely separate group of people from who's testing the core patches, but I'm, not sure there are very many people who are different right now. Yep I.

C

Think there's a lot.

A

Of people who are involved in fixing the contribs up, who are also involved in working in the core stuff, so.

B

The main reason why we are being reactive is because they don't know beforehand what I suggested or asked is if there is any way that how is is for certain people to be accepted in the actual Drupal security team. That is tasked with reaching out to contribute a news in a way that we or.

A

The Drupal security team Nate, you would know more than this and I do do they have access to see all security issues on all projects, control objects, the.

C

I think that there are certain members of the Drupal security team that have that yeah but members, but not all members yeah. They they separate it out and then usually what happens is there's only a couple of people that have access to absolutely everything.

D

C

As issues come in, you know the people that respond to the security at drupal.org address, they file the issue, and then they individually say invite this person invite this person invite this person, and they do that manually, usually for the maintainer zuv, the controls yeah. So I.

B

Was thinking can we be? Can we suggest to them that we need either one or a couple of us included in that list so that we own our rent check if that corresponding module has been ported to backdrop.

C

B

We don't need work we've. Instead, yeah people be proactive instead of reactive. That's what I'm saying.

C

Yeah we've asked but I think we asked on Jeff's behalf actually that he wanted to get access to all of the core issues, but choral quadruped, but yeah. Well. This was just four core actually because right now they add.

D

C

Only we asked if they would also add Jeff just that there was more than one person I think the same would apply to contribute issues that you know like the the problem is: is that it's manual and I don't think that they would be very excited about adding a step to check to see if a modules poured it up to backdrop find the main great.

A

I think, but what Gregory is asking about is if we can get somebody at that, high level of like has exes all contribs, so they don't have to do the checking you.

B

Know I'll have to. We will be doing the checking so long as they tell us that there is a problem with a specific detail, torque module and then we'll be doing the check. So I know that they individually contact the maintainer of the module that has the problem. All I'm asking is, if they could just see, see a group of a couple of us with every module and then we can go and check if the module has been ported if it hasn't been ported that way, you know the message completely.

B

If it has, then we react like we try to contact the maintainer sometime, they might be able to sort it out on their end. If they don't, then we step in and fix it and ideally at the same time that seek their contributive. Read announcements come out in detail talking yeah.

C

I think I think I, don't think, there's that granularity I think that they would that whoever that would be would just need to be a full-fledged Drupal security team member to be a tab, access and all those things which I mean they're. Probably fine with I mean the more. The merrier has always been the kind of policy on security people as long as people are trusted that they want as many eyeballs as possible.

B

Yeah, so the reason why he was suggesting that it could be a couple of us is that we don't have a single point of failure. So if someone is on holidays or something it still gets picked up, uh so money has more chances and why I said one or two are not more is so that we do not risk in creator sensitive information being sort of like disclosed to more people than he has to yeah.

C

Also, the one I mean I like to show coordination with the Drupal community, but I also like to not fill up their issue key with noise. You know, like usually I, only post, one comment, maybe two into any security issue, just say: here's the corresponding backdrop release, or you know things like that, just to make it just to show that there was some visibility into that.

C

But I don't normally go into issues and you know post like backdrops iam the backdrop patches and things like that, because that's just noise that isn't relevant to ya the Drupal folks they're. Not there issue tracker at least we.

B

Wouldn't be adding noise, it's more like we would be Watchers and we will be reacting on our end like nothing that we do on our end, would would sort of like be noise and there's it'd be more like them, letting us know if there is a country release. Sorry security problem ahead of time.

C

Yeah I think I think if we can select individuals to say we would like permission for these people, then we can give that a shot and I will probably need to come from me because they're they're, the ones that they think of backdrop. As being me, as far as the security stuff is concerned, but I'm feeling what the process for that will be will be just sending an email to security at drupal.org and just saying hey: can we do this yeah yeah.

B

So if we can have one one email that they CC and then on our end, we have a few people that are being sort of like that email is being forwarded to pretty much like we do with a PMC I guess we.

A

Have a security at backdrop, email address: would that be a good one to use for that, or should we set up another one? That's yeah. They.

C

Need to be driven, auric accounts like we could get the reports as they came in potentially, but then we wouldn't have access actually see what was being done on them. Yeah, that's, alright, I think to actually have access to the security dr. pollidori issues. What.

A

If it was me Gregory and Jeff yep.

B

I was thinking about the same.

C

Yeah, that would be great.

C

Yeah and doesn't seem overwhelming yep.

B

And on like on our end, I think it surface might be the same who's, not a man. You say that, but on my end like this is what I do for my ages here. I always keep an eye on security. Things I'm I might not be fixing things, because my neighborhood knowledge is not that but I'm the one that sort of like notifies customers. We we get approvals.

B

We release the parties or, at the same time, I'll be doing the same thing for country so yeah and at the same time as I, say that I don't want to be a single point of failure. So so what would be the next step? Would be you mate, requesting access for the three of us. You said from the security team yeah.

C

Here's the here's, the process, okay, somebody also asked.

A

Us to come up with the process for how to get on the backup security team, so we should write up something similar for us as well.

A

I'm, just gonna make enough to do that.

C

I'm a high barrier here you have to have worked on at least five security issues by public security improvements, three private security issues, at least 30 issues independently in different, contributed modules or core.

C

You have to have already gone through the get acceptance process, your favorite vulnerability and why recommendations from security, existing security team members, the kind of work you're gonna, do an expectation of how much work you will how many hours per month you'll be able to contribute. Did you did you actually go through that night or.

B

A

B

A

People that they're, like we know who you are like I, think it's an issue for people who, like aren't a part of the Drupal community who don't yeah. They don't know.

C

Yeah, it actually says that the review process is you, the email is sent to the security enter valid org at least two security team members validate the application and nobody raises concerns, and then you become a provisional team member and then eventually you become a full team member and actually, in reality, I'm not a full drupal.org security team member I'm, provisional. It just so happens that they provisionally include me on every core issue: yeah.

B

If we're provisional members and the provisional members have access just visibility to the problems, then that's all we need. We don't lean, because we do not necessarily say that we will help on the digital side. Oh no.

C

I think we fall access, because provisional is only two individual issues. Still, okay,.

B

C

Well, with all of those things, we might need to do them individually, like asking for three people all at once. I don't know it.

A

Might be good before we start going through this process if we sent like a private emails like Michael, House or something and said like hey, do you think there's any chance? This will work and then, if he says yes well, then we'll open tickets for like each of the three of us and be like okay, here's what we're planning on doing or whatever, but at least that way we're not like jumping through all of these hoops ahead of time to be like for them to be like.

A

No, we don't want to add more people to the security chamber. What have you and I think.

E

A

That email me or do you want it to come from you.

C

Well, it looks like.

A

When am I draft it, and then you can send it yeah.

C

And we should ask first yeah.

A

That's what it is, that's what the email is. Oh, oh.

C

Okay, okay, you know you could probably get Michael faster in the Drupal slack channel. Okay, maybe we'll just do that. Well,.

B

There is a security town on luck right.

C

Just the normal slack channel, Drupal, okay, yeah, that's actually do a fair amount of coordination via that, just like directly over the slack channel as well. I think there is a security slack channel as well. Actually, maybe not, though I it's a mess. I think that I think there's both the IRC and the slack channel and really communications have gotten really cruddy because of the split now, because some people are in each place and and the discussion happens both places every single release. It's a big mess. Okay, there.

B

Is a there's a lot of more say.

C

Irc holdouts in the security worlds. In there there is in there mr. Turkle I think yeah.

B

I see two channels, one that is security, questions to ask questions about security and then the other one security team, public security team, Channel.

C

I've not been in the slack channel I. Just you talk to individuals.

A

What what were we talking about when we started on this about.

B

The security policy and where we should put the right there, yeah yep, okay,.

C

Very first item.

A

B

Before we move in just this, the final thing that we need to add as a task there is to update the contrib sort of like agreement, the maintainer agreement that to let them know that there is a security team and we will act on their behalf. If.

C

It's already in the country agree man how.

B

Is it okay, yeah.

C

Security team may modify and publish new releases of your module like a.

B

C

B

We're a step ahead, then: okay, okay,.

A

Okay forums, I Tim, have you noticed any improvements in spam in the last week, since we put his mint on there well.

E

I haven't noticed any spam. I mean we weren't getting any any before that, because we had or moderating right I turned.

A

E

On what's exactly yeah and I, we haven't enemies, I haven't seen any spam. I haven't checked today, but.

F

A

We should start paying for that, which means Nate I'll have to bother you for credit card details, or maybe this would be a good chance for us to get on board with Conservancy figure out how they would want to do. The like monthly yeah.

C

Wait weird: you know how that how they would prefer that to be done, that we would have a credit card for monthly expenses, and then we would ask them basically to pay the bill.

A

A separate credit card- yeah, yes, Bert. Okay, do we have one already? No, we.

C

We previously asking.

A

C

Count exactly, but essentially they now are the checking account. Okay, interesting, yeah and I actually think that they do something funny like it's not like. They wouldn't sign into any kind of online account. I think that they would, you know their preferred thing, is sending a check or any check like per request, essentially.

A

A

A

Translations I just look like Olaf's here today. I know he's been doing some work on it, though we set up a new category in the forum specifically about translation, so that people can use the forum to chat about translations.

A

He asked if we could set up subcategories for each language, um but that looks like it might be complicated, so I, don't know exactly how that's gonna happen like whether those are gonna end up being like a language feel there's something or if we're gonna actually have a forum category for each country and then within each category there would be discussions about individual topics, but that is on the work she's trying to figure out how to make people have less of a hard time communicating with each other around translations and that's it for websites Nate.

A

Do you want to check about cat about poor, update progress? Okay,.

C

Alright, so let's see one twelve four against the next bug fix release of backdrop, and we've got a number of issues that we've got highlighted here for being addressed as soon as possible. There's some more RTL issues, there's now actually a pull request on ckeditor icons. The arrangement of the toolbar for seek editor is issued. 3504, there's now a poor quest there that needs review.

C

We don't have any updates on supporting multiple equivalent security releases. 3524. Isn't that issue no updates they're a kind of regression from 111 once we had an options element in decor. If you have options element enabled prior to your upgrade, then you can get a fatal error, because the same function is defined twice that issues 3485 still needs a pull request on that issue.

C

Let's see layout clone breaks, layouts issue, 2673, there's a pull request that corrects the issue but needs tests and that same category of things that needs tests PBO exception when image is missing on disk, is issued. 3462 herp derp will created a test for that issue, but he said he can't actually reproduce the initial problem, which actually has been the case for me as well, and so we haven't.

C

We now actually have a test to include the coverage of what the problem is, but it's not failing without the tests, which would be the expected thing to happen. So so.

A

I'm, the one that reported that issue I have a site that fatals what the missing images are missing, so I will run the test and see if it passes, even though the things failing and try and figure out what what the problem actually is, there might be better or different steps to reproduce that I can throw in there yeah.

C

Yeah I kind of I've been wondering about that issue, actually because it's like that there's something different about backdrop versus Drupal with temporary files. As far as I know,.

C

What's that these.

A

Are permanent files is a database query that Thursday yeah.

C

That's what's so strange about it is that, like the management of temporary and permanent files is basically identical.

A

No nothing years temporary, though right.

C

Yeah yeah I get that okay, I guess I guess maybe files are entities, I might somehow be really I, don't know anyway, so that one at least is moving forward a little bit. Now we have a test, but we just need to make sure that's actually covering the problem that is being described.

C

Let's see and lastly, for bug fixes that are being called out. Contextual links for editing views is issue 2690, sometimes those view links or the contextual links aren't accessible like they're, hidden beyond the toolbar at the top of the page. So no updates there still needs work. I think that yeah needs work, there's kind of a proposed to thank, but we we don't think it might be the right direction.

C

Let's see, there's also a bunch of other issues, tech for 112, for you can check the one toe for milestone. Let's see, we did fix a couple of things. Let's see, we fixed a problem in link module, adding support for a PHP 7.3.

C

Compatibility thing, so that's great to get ahead of that. Thank you, Andy Broomfield, who actually is relatively you know new and contributing issues like you went through and filed a whole bunch of them recently. Thank you for making those issues and the pull requests.

C

Okay, that's all I've got for 112 for do you guys have any other bug fixes. You guys would like to call out.

B

Well, other ones, but I might need some help with what's going on with a CSS, with that entire issue for security to the the icons so I have found. So you basically my pull request currently fixes the icons themselves, but then there's some CSS issues where they're sort of like with a padding of them and I've, found the offending sort of like CSS entry, which is it's coming from seven.

B

But if we remove that, then we break the list items for the rest of the site and I couldn't override override it with CSS. That I was adding in ckeditor specifically, so I might need some help with that I'll post some more information on the ticket.

C

Eight okay, so 113 113 is the next minor release that will be coming up. May 15th 2019 with the future freeze on May 1st we've got four issues that we've got called out here to go over in agendas, telemetry, dashboard, config, translation and package. Signing of those. Let's see telemetry there aren't any substantial updates. There's some more brainstorming ideas, dashboard Jen. We want to talk about dashboard, sure.

A

I'm doing a link in the hangout chat, but it I did a lot of work on that last week on the planes it's really fun and then Gregory happened to be working. At the same time when he saw my work- and he gave me all of this detailed feedback which I think I've addressed all of it. So it's ready for more review laughing.

B

Because that's only thirty percent of what I have.

F

A

A comment that has screenshots in it, so you guys can see what it'll look like, but in seven style is there, it uses the same style, that's on the admin index page or the admin config page I've added icons, the default one is the arrow you see on the right-hand side there and then some blocks have their own specific information.

A

I also added the available updates block. So if you guys have thoughts about how that information should be formatted and definitely open to suggestions on that and I think other than that, everything is good. To go. I haven't looked at the config forums, Gregory, so I know you mentioned there. Some issues there that probably was just all ported from the other module invidious to be updated. So, for example, I think that.

B

Where we say which content types, the show stats for instead of saying, select, content types, you might say, select or no users or updates, or something like that or the other way around I gotta move it, but yeah, okay, yeah.

A

But I think on the front end: it's looking pretty good. Yes,.

B

Yes, so, as I said, it's a it looks pretty good and you can go in sort of like a Z's after we fix those minor issues here in there. It's just that there's so many the things that I've noticed that I thought, instead of just telling you pointing where, where things are wrong sort of like perhaps I'll file, a pull request against your brands, yeah I may need to review it. Yeah.

A

That's nice or if you know how you saw I, don't know how github does that, but sometimes you sound like a bunch of little paw requests on the code review them there. Those are really handy. Yeah.

B

The the problem with that is that it only allows allows a single line to be change. So if it's, if it's a multi-line change, then it's okay.

A

Okay, well, however, you want to do it. Yep.

B

C

Yeah, this looks good icons are a big improvement. Yeah.

A

C

We look like border.

A

Background changes also, don't you I, also posted some screenshots of what it would look like in Bartok in basis just so that it looks decent, but most of this style that I added to it is happening in the 7 theme, like all the icons and stuff yeah.

B

The icons are not there for the others. What one one that one! The issue that comes to mine now is that when you switch to RTL, then the icons fall back to default, arrows for all of that, so yeah, just okay, I.

G

A

On that yeah one of the things that might also happen on the admin config page I, don't know people.

B

Doesn't happen, it doesn't so I've turned myself into an RTL maniac now, so it's something I just switch the side towards the Olga because they were pretty some pretty sort of like a major.

D

B

Over sites throughout the user interface- and it's the same things happening in Drupal 7 as well so yeah.

A

That's it my empty. It's exciting. It is great.

C

Okay, cool see anybody that has additional feedback, please supposed to issue 495. They should potentially so, let's see in the world of translatable config strings, 34 55. We still have this great for requests that gets started on us, adding config strings to config files and adds the translatable strings, I think for the main site, settings like logo or slogan and site name as well as email, says: issue 34 55, there's a poor request there.

C

They could use review and package signing issue 1992, there's two different proof of concepts there that have been put together, both of which need some review and feedback, let's see also in the 113 lists. Just while we're on this topic, we didn't. We haven't called this issue out, but we did add a new feature just earlier today. That was our TBC.

C

That translation module now makes it so that, if you have, if you're using content, translation and you place an existing, the existing content block, you may now include the translated version of that contents matching the current site language. So that's handy so now you can place one block on a piece of content and, depending on the site language, it will show the corresponding translated piece of content on that in that area. So that's nice and it's all good for the 113 status.

C

Update, let's see so the next up is just do we have any other 113 items before we move on? Okay, all right now, I'll! Let you do this general discussion.

A

Sure so this is something that came up yesterday when I couldn't rib security team was working on security releases is that the project- and this happened in Drupal 2- has changed its name, so it used to be EU, cookie, compliant and at some point it became EU underscore cookie, underscore compliance and so the backdrop module maintainer taint changed the backdrops project's name to match Drupal's project name, but the way project module works is that it uses the name of that project to create a node on backdrop, CMS org and then all of the releases that are associated with the node, with the particular name are still affiliated with it.

A

So right now we're in a situation where we have one project, it has a security release that isn't marked as having a security release, because the security release is technically on a separate project node, and so there are a bunch of people who are running the insecure module and maybe have no idea. So I was wondering how we solve this problem like now that we have a secure release for this project.

A

Should we create, like another release like change the name back, create another release, change them forward and then have a really so at least the people who are running the old module know that it's insecure or do we not change the name at all and have some policy? That's like you can't change the title of your project node, but github lets you do it anyway, so we can't actually put my people doing that.

A

So just like how how do we handle this problem, where we have a security release for a kinship project and people who are running the module, don't know because the release is on a different named project than the old one.

B

A

B

If we fix the project module to always come the dust is- and this was we wouldn't have that problem in the first place. So if we enforce that all projects use underscores, that would be good. So that's step one and then the other thing is. We need to find a way to merge those two project nodes and their releases into one.

B

Which might be a tricky thing might be done, might be need to be done on like a what you call at the database level. Yeah.

A

So I was looking at that yesterday and I'm, not sure all of the places that the project name appears in the database, but it looks like so I started to do it where I was like. Oh I can just update their releases and point than that. The new version and.

D

A

Was like oh wait? No all the usage statistics is also tracked on an old name of the module and so I was like I, maybe shouldn't around the database. So.

B

So the other thing that this can work is like we, because no one has downloaded the new version with the other schools. Yet these will remove that temporarily the release in the entire project node, and then we change the existing one with a disease to others course, and then we merge the release from the other one there once it hasn't disclosed.

A

So the people who are running the version now they're running a version with dashes. So anything we do with underscores they're, not gonna, find out about so.

B

Does does the actual module folder when it's downloaded has dashes instead of yes,.

A

Oh, that's fine too had underscores. So that's why the module name was easy to change on Drupal. Certainly all the code is underscore we'll just underscore the folder and actually on Drupal. That worked. If you look in the github repository, the Drupal 8 folder has underscores the triple7. Folder has hyphens I, don't know they did that. That was a big mess, because.

G

It's the parent.

A

B

This it is a big, my cities, no.

C

We do like update module in core supports, you know, modules being considered unsupported or insecure. You know, so we could mark the node on backdrop, CMS org, the one with hyphens as being unsupported, and that would just flag it in update module. Is you know having a big warning sign saying this thing is not supported and then it links over to the issue page and then on the issue page, we could say you should delete that module and use this one.

C

Instead, you know so we can actually believe the one with hyphens kind of in place but flag it as being unsupported unfortunate.

A

I checked that, but there isn't actually an unsupported flag in backstraps version of the core project.

A

Vocabularies that were on drupal.org yeah.

C

But I think the vocabulary still doesn't do it, because our feed doesn't take into account that vocabulary. So we need to make an update to the project release module. That makes it so it pulls that flag that that status from someplace, because right now it doesn't it right now it only supports like like published and unpublished. I think sorry.

B

If we provided a sort of like an upgrade path or migration path from the old module, with a passage to the new one, and if there was again a way to to mark releases as replaced by something else, so.

G

A

Don't even upgrade paths because all of the code had underscores the problem is just that project module uses the hyphens as the project name.

A

D

A

The database on people's sites is underscores because it attracts like schema version. They.

G

Always more concerned about the configuration files.

A

Configuration as are the same so.

B

Okay, so you would pick up the configuration from them.

A

Yeah, like you, remove the old one with one name and you put in the new one with a new name and it's good to go. There's no problem. The only issues they don't know, there's a new one available, because project module isn't detecting it. Yeah a.

B

Big mess for independent of that specific use case I think that we should have it that so that either the packaging script or what the project module refuses to create create nodes when they have dashes yeah, if the refuses- or it just replaces them with underscore. So we don't have such a mess in the future.

B

What is the best place to file a ticket for that is at the project module to.

C

Actually, oh, what to implement what solution that see also thing or something else.

A

Rename rename anything that has to something that has underscores yeah.

B

Well, when, when nodes are created on Beto tog is.

C

That is it at the right place like should we oh I know what we should do so in the bankruptcy mess org.

C

Repository, so it's not it's not part of Project mantra, but bankruptcy messed org itself. It has a file that does the packaging. You know where it modifies the info file and stuff like that, and that's not a project Pancho. That's a custom module on backtalk semester, org that modifies the process before the package happens, and we already do things to like make sure that a module type is specified in the dot info and.

D

C

Like that, and if not then it it returned instead of making a package on backdrop, CMS org and making a packages package on github and making a package is required for the node to be created the first time. If, if there's a problem, then it instead of uploading a package, it uploads, this package, errorlog dot, txt file to the project and we should just add an extra validation, they're saying the project name has to include only underscores and it would refuse to make packages in the future yep.

C

And if there's no package, then there's no release on backdrop, CMS org. That would solve the problem. So we can.

A

C

Them that in the package er this.

A

Is the get LC webhook module so that sound familiar no.

C

It's the board, github module, yeah, there's a function called or the github github project validate.

C

B

So this will fix the issue for future releases. Yes,.

G

B

Future projects and then and then we didn't see what we can do with a specific module.

D

Okay, so that sound good? ah No, what do we do about it.

B

I, don't see I, don't see an easy way to automate this, maybe just post instructions on the can we mark it as supported so that people at least are notified about it. So.

A

That we don't have support yet for now, but we should anyway yeah. That would be an issue against the project module.

C

And this point I'm gonna check something over cookies as well.

C

And we do have some support in the module I'm looking through it now, apparently, if you mark no releases is supported, then it would do that, but I I'm not sure we're on backup, CMS or gif anywhere. We have the ability to mark something like a release is not supported, though.

A

C

You know how how there's like the recommended version yeah, if you uncheck all of the boxes for recommended version, then it becomes unsupported, but I, don't know where that form is on bankruptcy at start of work. If we even have one.

B

You need to go to each individual relation mark them as unsupported. Is that what you saying yeah.

C

If you mark every major version, unsupported, then the whole module is considered unsupported and then it shows that flag in the feed and.

B

It's reflected on the status based on the update status based on the size fight.

B

That might be a way to do it. I.

A

Don't think we have a form for that. Oh I.

C

Think I think we do I think that we have a problem that we don't show subtabs on tightropes name.org.

A

Don't know I see, I found it there's a releases sub tab, yeah, okay. So if I uncheck this box.

C

It then we don't have the sub cans I.

A

Have sometimes but.

C

Don't if I'm on, like note / edit yeah I, don't see any sub tabs.

D

I'm tensed this page.

C

Yeah I don't have any took eggs hmm edit tab by Anakin type / releases afterwards, I can get to this page. That's that's the page you're talking about right. If you uncheck the supported, say of what you did. It looks like yeah then now that should do the job yeah.

B

I, don't have I, don't have those maybe.

A

There's like a special permission for like releases, and if you don't have that permission, then you can't see that tab well,.

C

I can't I can access the page, though so it's not from adjusting.

A

What can I see it, and you can't see it.

C

Yeah, that's true across the board, I don't have sub-tabs anywhere um I mean there's other sub tabs as well. Aren't there.

A

We remove them from lots of places like the manage fields. Page doesn't have them anymore. Yes,.

B

Oh so, when I view the the the project page I, have you edit and outline, but if I go to slash releases I see their releases released table oh yeah, when I'm.

C

Didn't should be under /, edit / yeah, really releases yeah.

A

But that's true like on the front end I see you edit outline and on the back and I, see releases and releases table as well as project and releases.

B

So I know what I I'm responsible for that releases table and I know what it's their releases are stable. It's just of you.

A

hmm Well, I, don't know what the tab issues we'll have to figure that out later well,.

C

I think we solved at least eight that the main I mean now says that it's unsupported or it should, and then we can update the validate function to prevent packages in the future. If it, the name is right: okay,.

D

B

If I was a person that was using that module now, I will see that its unsupported I will go to the project ID, and maybe we should update the page to say that please, please replace your module with that one and point of anyone. What is yeah.

A

So it currently says: please see the new EU cookie compliance Nadja listening. This project has recently changed. Yeah.

B

But but if people delete and uninstall the current one there will those other settings correct. Yes,.

A

B

We should have a step to say that please save these settings file or whatever, or should we make it that the new one can be installed in parallel with the old one, and if it detects that it's the old one isn't is present, then it sort of like copies their settings, something.

C

There may need to be manual steps here, I think yeah.

A

C

But the right thing to do would be delete the module, delete the entry from the system table and then put the name on place.

A

Yes, that way, you lose all your settings. Yes,.

C

B

If your uninstall it and.

A

Install it or delete anything from this system table the.

C

System table only has to whether or not the modules turned on or off right.

A

But this is the schema version name, not the folder name. The upgrade path works.

C

Ok, all right! Well, I'll! Let you write howdy, we'll.

B

Figure it out, it's just needs more time, all right.

A

B

Did this coming yeah.

A

I think that was it for everything we had to talk about today. So thank you guys for helping us sort that out anything else. Anyone wants to add Justin's here Justin, we talked I'm, not sure if you're actually listening or not, but we did talk a little bit about the Leonard's in the last meeting. Oh glad you're here here um and Nate had an idea.

A

What was it long term goal? You wanted everything on its own server, but for now having just backup CMS org by itself is fine and we can put everything else on the new server was that it.

C

One the only thing I had was that using one server for everything right now, it's fine I, don't think that we should start separating them until we start having. Oh, oh.

A

Even including backed up CMS network, yes,.

C

Ok, yeah I, don't think there's any desist, I break them until we have any kind of scaling problems. But right now we haven't had any problems at all. Ok,.

A

So Justin you can set up a bigger Linode, then as a starting point, and then we can just move everything over there as needed.

H

C

Amenable ok, I have anyway, I didn't even look at this issue. I think it's worth mentioning on the phone call, so bankruptcy master, org, 4, 7 9, is where Justin has been posting comments on here.

C

Yeah, actually, do you want to run through these Justin? You last comment was just 11 hours ago. So.

H

I'll, have it up and running well, I have nginx running I, don't have PHP configured yet, but it's installed so probably do that tonight and then I migrated the files over I'll grab the databases. Next, like I, made a little to-do list there yeah.

C

Excellent yeah migrate to databases, configure PhD in genetics, Maria anniversary cash. Let's see there was something SSH keys, great Oh, sir pot. Did you get sir pot working I.

H

Installed it okay, I.

C

Know I know a lot of people have had trouble with certify, which is you know, Letson for other people. That's for, let's encrypt for basically free SSH, keys or sorry and I know. In the past, we've had some problems with it with engine X. So if, if that, if that proves to be problematic, you know we have the certs off the old site. We can just continue using them for the time being, but this is a good opportunity, because every time the certs run out we're always like.

C

Oh, we should switch to let's encrypt and then we have problems and then we're like fine, we'll just fly the new search for another two years and and then then we just gonna kick the can down the road a little further yeah.

H

Well, I know I'm the sane OS X systems, the Python version, that's provided by the package managers out-of-date sir pot, so it complains and sometimes doesn't do the auto updates.

H

C

Avoid that I think.

H

It'll render on Debian yeah.

C

I I would guess so as well. Yeah cool well! Thank you so much Justin for for putting forward so much effort on that. That's very exciting I mean our current version of PHP is 5/4, which just seems atrocious in this day and age, but unbelievably new install of Red Hat. That's still the current version like even though the latest version latest stable at Red Hat. It's still the current version, yeah.

B

A thing is one of these cases when the vendor promised that they will be back porting, the security fixes to their previous versions. So that's why so it's still, it might be not officially supported by PHP, but it's supported by Red Hat yeah.

C

Yeah I know that that's supposed to be the case, and it probably is for the most part, but still it's really frustrating that it's just so freakin ancient, yeah, yeah but I mean that's exactly why backdrop still has that ridiculous?

C

You know old version of PHP requirement, because this isn't it's not a problem just with us like for just for us there's a lot of people that are still running older versions of PHP yeah.

B

We have exceeded the time. I just want to quickly bring up another letter and just quickly get a feel for what people feel like about basis. I have suggested in the past, I'm, not sure if I have added a ticket for it, that we should ship core with at least an extra layout for context, node slash percentage so that people can, because it's easier for people to enable and play with things and configure them, rather than build them from scratch.

B

And now another use case possible use case for a layout came up with the login page, where yeah you need to follow that issue too, to have a clue but yeah in general. How do people feel about another couple of layouts being added, even disabled? If not, you know food on when I enforce them to people chipping with core. That's what I mean.

C

Anybody else want to say something: silence.

B

C

Generally in favor I think that wasn't.

B

So that machine is how do you feel about adding another couple of layouts, not layout templates but actual layouts, like the default, the front page layout that we have so and one use case for that was in the past to add something with a college content layout or something like that and have have it have the nods less percentage yeah that sounds like yeah cuz.

B

What one of the one of the problems that we have with new comers like I was given my brother, which is not a Drupal user, that to play around with it in and I said that, yes, you can add fields to as blocks layout and it took him a while to just sort of like start complaining about, but I don't see any field says looks and then I was puzzled right.

B

Not the right context, so against that it's easier for newcomers to enable a.

B

Layout that offers the the blocks out-of-the-box sort of.

C

Yeah I agree: I think it's natural that people typically will try to add a layout at like no, it's flash ten. You know because they think oh I want to add blocks, but they, like so little I, mean I. Think there's an issue for that as well like making that easier, but yeah it would be it would. We would avoid the problem in the first place. Isn't it so yeah.

B

And if it's too much like we do, we do have the option to disable play em, so they can ship disabled by default. If it's like too many blocks there, the.

C

Mandatory layout.

B

C

The only thing that makes me hesitate as I wish, there were a reason.

D

C

Like a different block that we would actually want to add to an individual node by out yeah.

B

Yeah I was actually I was actually thinking, but this might break people's sites, so it would be actually a use case to have the post spider use that layout and have the image be on the sidebar or something like that who are bio. It would make an excellent out-of-the-box use case of Harriet and use fields as blocks.

C

Or there may be something like a more blog posts view or something like that. It would go in the side yard.

D

Which I know the.

C

Out of box WordPress is its behavior is to have that funny. Archive thing in the sidebar that shows all of your posts by month and year in the sidebar yeah did that, but no similar yep.

B

Right cool I'll have a little bit more thought about. It, I'll find that issue for it. Okay, okay,.

C

Well, let's wrap it up work overtime by quite a bit and gem is handling a barking dog. So thank everybody for.

G

C

Great discussion and I'll talk to you guys later and see you on the Internet yep thanks.

G

The cat has a gone cat.

C

Goodbye for real.