Backdrop CMS Weekly meetings, 22 Feb 2018

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Backdrop Weekly Feb 22nd

Description

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

A

All right we're on air. It is Thursday, honey, 120 seconds. This meeting is a check-in on active development tests for dr. up CMS plus other related information. You don't think we met this meeting last week. There were several technical failures on the side of those who are trying to run the meetings and I think to me terrible timing, like so sorry we're meeting last week, but we have lots of exciting things to share last Tuesday dido, which is the drug.

A

Local development environment, actually have a hosted solution as well added built-in support for backdrop, and they have a blog post that went out. I think stay last weekend, noxian, which is pretty exciting, so anyone who's using d/deaf or local development can now use it pretty easily for backdrop, which is great fastly, also offered to help support backdrop in the same way that they're supporting Drupal by providing content delivery network for all of our properties, so that would be effective to Mister org, but also the forum slightly.

A

It gets like non-local i7, so we've started working with them on I, get that set up and when that's gone, we'll get some corporated blog posts out, one on our site, interesting that were sponsored by fastly and then fascinate at the women that they're sponsoring us as part of their open source initiative, which I think is really great.

A

Hopefully, those two things will also help us reach new markets, people who might not have been considering practical or there indeed abusers or best the users who know us that's an option for them, not a fool of us increase our reach.

A

So last week, Nate and I went to Florida terrific Ampligen training and Friday a session on Sunday, and one of the people from our dreaming on Friday has since ported the real name module in submitted an application into vector picture group requesting access to provide the module. So I mean that's fantastic. Something looks like I wonder if I can make this module work on my site, so another one contributed back. So thank you very much Mark for your work on real name in.

A

On our own website, spec top CMAs Network a couple of things going on. We have our homepage redesign as one last fit, which is creating the top-level page for.

A

Add-Ons modules and themes, I, guess, is snooping, sucked and then also building out the new try backdrop on page which we're with you, so those two things should be done joining in then we anticipated that any more. Oh, they also point out there couple of little bugs that the CSS on there, which I will try and clean up, is that our forum site is blend pretty well, there's been a whole bunch of people over there. Asking good questions, which is great.

A

That's I should be getting updated to the latest backup core today and after that point, all of our images and comments will start to work again so I know I've been an issue of other people, posting screenshots and having them cleaned up a garbage collection that issues been fixed in Florida being pushed to one site later today, and then people had also asked for a search box that you can find other people talking about your issues and that's also going to be deployed, but it's a little CSS love on search results page.

A

So that's what the holdup is on, that um API site is going to get a copy of the same theme. That's running I, backed I've, seen a store in the forum, not sure ETA on that, but back h, AP AP I think just deserve a little love. It's been a while since I've worked on, it's just been doing what it does, which is great, but it would be great to get updated to our brand as well.

A

So that's it from our other websites to talk about.

B

Yeah boy, since it's been two weeks and said we had a meeting, we have a lot to report on so 1.9 was Versailles. One point nine point: one was released last week, yay that was great. It introduced parody with Drupal 7 55 through 7 56. But that's not all one point. Nine point two was released this week yay.

B

So we had two releases in two weeks last week was just a standard bug fix release, but then yesterday Drupal had a security release in 7.57, and so, as always, we released a corresponding release of backdrop. That is 1.9 point 2. That includes those same four security fixes that are in 7.57, apparently 7.57. Those security releases, those security fixes exclusively.

B

So that means that we don't need a cross porting issue to port things from 7.57 into backdrop, because 7.57 is already fully cross, supported with with just those security fixes. One point: 9.2 also included a couple of small fixes that will help out Pantheon users, sometimes nginx. If that's your webserver, it might be complaining about your htaccess files, but HDX as files. Don't do anything on engine X.

B

So there's no point in having it notify you about engine or about HDX is files missing if they don't do anything a couple of other minor issues that were also addressed in there, but for the most part one point nine point: two is just the security fixes considering it only been a week since one point, nine point: one came out.

B

One point, nine point: three is the next bug fix release? There are a number of issues that have been continuously bumped from 191 to 192 193. Now, there's only a couple of these that are marked as needs review, but almost all of them have a pull request that are in needs, work, status and I'm not going to go over all of them individually, but check out the issue to have issue tracker.

B

For one point, nine point three: on github: all of those issues have had progress but need a little bit of work in order to push them forward and get them committed for the next version: okay, yeah and I. Guess specifically, this is just added into the agenda. There's 2904, which is the problem with database credentials. Previously they didn't have to be URL encoded, and now they do need to be URL encoded.

B

If you're using this short, one-line database credentials, we made a change in 1.9 that allowed you to use special characters, all special characters in your database passwords, but it advertently broke the percent symbol, so all other special characters now fine, but the percent symbol has a problem.

B

So we have an issue there to basically temporarily make make it so that the old format of passwords would work for your database credentials and we want to tell the people: that's.

B

They need to update their settings by PHP file to match the new URL encoded format. So you know. Hopefully, the number of sites that are affected by that is is small, but the longer we wait on that kind of the less relevant it becomes because as users upgrade to 1.9 they're all going to run into that problem, so sooner the better for trying to get that fixed in place to kind of transition, people to a password format, early all right, 1.10 1.10 is the next minor release of a backdrop that will be coming up.

B

May 15th 2018 and in particular this release is focusing on translation improvements to issues in particular issue, 22 or sorry. 225 is making menu items translate this one is really close. It actually had been marked our TBC functionally. It's complete. It just needs some terminology updates to get it all acceptable.

B

So that's really exciting menu items have always been an area of trouble for Drupal as far as translating coast, and this will resolve that problem and get us one step closer to being fully international I, simple out-of-the-box.

B

Config translation is issue 704 and config translation. We have a pretty solid battle plan for that is backwards compatible and doesn't actually really introduce any new I.

B

Don't know it doesn't really introduce new functionality. It introduces new API is to make it so the translation is more consistent throughout all of backdrop.

B

We have a solid plan there, but implementation is only the proof-of-concept phase, still an issue 704. This is something that we can start: implementation on and work to transition our API over the course of multiple releases, but it would really be great if the initial release had some really solid implementations that would set the standard for all of contribute to follow.

B

Let's see another topic, improvements, two modules, themes and layouts the process of downloading installing finding and enabling them. Let's see, we've got issue 1517, which would enable the capability to have multiple screenshots for project so that when you're searching for projects through backdrop, CMS org or through the project, installer that you'd be able to see multiple screenshots of a theme or some screenshot at all of a module which right now, there's no images at all. For anything other than themes.

B

Themes only have one so there's a plan to provide that functionality, but there is not yet pull request. I, don't think to make on the implementation.

B

A really old issue issued number 37 is adding the ability to have tags on modules to improve the way that the search results work when you're doing the module search or when you're, enabling a module having modules that are all the same tags show up, and there is an initial pull request that simply adds the capability to the intro files, and that is in a nice review state and, lastly, also kind of related to the previous issue, making it so that the instant filter searches at the top of the main modules page in backdrop search not just on the project name, but also on the grouping name and that is issued 2973.

B

That only states the problem at this point there's no code to back it up. Yet there are also a bucket of other issues for 1.10, including some file manager and media related issues and of gram. 72 has been working really hard on making it so that you can upload a file to the WYSIWYG editor. In the same way, you can upload an.

A

B

Just inserts a link instead, for example, there's a lot of other media related issues as well that have had really solid starts that we can push forward further in the 1.10 release.

B

That's it for the backdrop project updates section in here for backdrop for good Jeff I do have any updates this week for that project. I.

C

Saw some movement in the queue so I know Lehren, but Clarins been doing some work there. So I got a bit on my plate to go through that queue and then push it forward again.

B

Cool and then the next item on here I think, is also in the Jeff category, which is general maintenance of the backdrop docker image. Do you want to provide detail there? Yeah.

C

I don't know I, don't have good sense of how I watch that's used, but my motivation has slipped because the primary thing that I knew that it was used for was calleb oxen and we don't work on Calla box anymore. We only work on Lando and it doesn't use that docker image. So my motivation to maintain it is low, but I'm not sure how many people use it. So if anybody else knows any of those things, I was interested in maintaining it take it.

B

Yeah great, that project is managed in the backdrop ops, github group, if you're interested in maintaining interests in an email to info at backdrop, CMS Oregon will make it so you can get access to that repository on github. Is there a way to see where this image is actually being used like? Is it hosted on one of some of those websites that always dr. images? It's.

C

B

C

B

I think it says, like.

A

Too so we might be able to get someone there to mediate. Oh interesting.

B

Yeah, then, that would suddenly make it important again.

B

Okay, that's a great question. Thanks for bringing that up, Jeff I hadn't noticed that there it's been a little bit of delay on there and that we maintain so many up streams.

B

I can totally understand the need to distribute that we now have an upstream or or starting template for both Pantheon and platform SH and the docker image you know, and the original package file like there's a lot of different places that then right now we're kind of managing those things all centrally, and it would really be great if we can distribute those things and kind of a more to mean, be driven fashion and have people that.

D

B

D

B

D

A possibility it was.

E

Exactly what I wanted to say.

B

It's not a tremendous amount of effort, but I don't know if we want to fully automate it.

B

Like updating the Pantheon image is a matter of just pulling and then pushing like one get poll. One get push I think that's pretty much the same for the platform SH and the docker image and I think is actually even simpler than that. It's just pumping version numbers in the text file. So none of these things are commended.

B

Slee, difficult, I guess the docker image actually would be a lot easier to automate just because the risk is a lot lower there than it is with like the Pantheon upstream I feel like that needs to be exploited.

B

But a great question: it probably could be automated. There's.

A

Also, a library that he knows 1-click installs, that I think we got set up on a year ago, but I noticed that sometimes I mean tend to be shared hosting. There's the ability to do one click install backed up, but it's like that job look for so we should figure out how to maintain that as well as part of our very weak cycle, so I'll try and figure out what the name and we have an issue somewhere. That's like we should have backed up in one clicking.

A

So I was like about two check boxes and I. Think a lot of the reasons seem too old for that. So hopefully we don't have to maintain one, but I, don't know where it is here: I'm, maintaining so I'll try and do some research and figure out. Oh.

B

Great yeah Jeff said that that docker hub image says that it's had more than 1 million poles, which seems a little bit surprising.

A

Never doing a lot of automated testing. That's.

B

A lot of calls that's pretty impressive I.

E

Wanted to ask them if I recall correctly backdrop for wood is also used as a use case for the translation thing of the lingual correct.

E

Do we have the single sign-on thing going on for forum and other sites like that? Like would I, have admin access or do I need to create an account I'm interested in translating it and just playing around what we have some fun.

A

So we don't have single sign-on working with anything yet so, depending on which site you want it to be back to it. I don't know anything about the factor for good sites. Specifically, you probably have to talk to talk about that. If.

E

Is that did you the person to be talking to you yeah.

C

I think you got an account because you did some some Greek Greek translation or.

E

I started doing that. Yes, but it's been so long, so you.

C

Should have an account, though, but if you don't I'm the guy to talk to okay.

E

B

Okay, anything else, I think that that wraps up the agenda. The final thing was that doctor in each question- and maybe that actually is a better way of spinning it- you don't necessarily need to maintain the darker image. Nobody likes doing maintenance, but we do need somebody to automate the backdrop darker image and everybody loves automation. So it's a great possibility for someone out there that can you do a little github webhook magic could probably make that happen.

B

Okay, unless there's anything else, I think that does it for this call any last words: okay. Well, thank you, everybody once again for joining the backdrop meeting and we'll see you guys all next week.