Backdrop CMS Weekly, 4 Apr 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Backdrop Weekly - April 4th

Description

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

A

Right we're on air, it is Thursday April 4th, and this is a meeting to check in on active development tests for backdrop CMS starting at the top of our agenda. We are working on updating, vector up CMS or we want to put some information about rupal seven upgrades onto the homepage. We also had some jibbing kids in the outreach meeting about writing a blog post about upgrade versus migrate and linking that and also updating our documentation on upgrading.

A

We also know we're making some changes to the module simpson layout pages. That's issue number 442, no movement on that lately whole each demo. Button last week we mentioned that we thought a new version of PHP might solve our problems, but it did not. So we need to figure out what the underlying issue is and in particular it seems like it worked before, and then it stopped working and I don't know if that was something that changed on tugboats and there's an intuition aren't, which I should try and figure out what that was.

A

That might be something we can talk about. Next, we get Drupal funding. If you know anyone the tugboat team, is there yeah.

B

It broke at a very specific point when I regenerated, the authorization token and the authorization token works from the command line, and everything like that, so I'm a little bit befuddled, but now that I've seen that it fails well, I, don't know it's even more weird that it works for me on my local copy of doctype CMS doesn't work so does that work from the command line on the new server yeah I works from the command line in the old server.

B

So yeah I know it's so strange so, but it definitely was related to that because it stops working right at that time.

A

Do you think there's something to change on tugboats end between when we generated the first key and when we generated the second key it might process, and it.

B

Was definitely when I regenerated the key like in a matter of minutes, it stops no.

A

No I know, but it had been a long time since generally, the first key right. Yes thank.

B

A

There's something that happened on there and we're there like just accept all the old keys, but new keys do something new too and then that's making it fail for some reason.

B

Maybe maybe I don't know well anyway. I think it wants a little bit more research and our ends before we before we have to live too much because I'm I'm pretty sure it's something that we did. Okay,.

A

All right, we also mentioned in our outreach meeting that I have an event on April, 20th and Gregory has an event on April 22nd, where we would like to ease these sandboxes it'd be possible to get that resolved in the next week and I. That would be amazing.

A

Okay, moving on or I'm say it looks like we have a note here that maybe this will be the next site to move to the new server I. Think that sounds good yeah like it's not here, to object, Justin's here, so the forum site is a good one, because it's not super important, it's not as important as our API site, but it's the one that has the most authenticated traffic.

A

It's also would be a good chest of a new server under slightly higher load before we move the main site, so I think it's a good one. We can also look the localization site properly at any time. Yeah.

B

C

Something belong is that, with the move to the new servers, we upgraded bid, speak you just said, but nginx was downgraded to one but 210 from 1.14, something.

C

Yeah, just to mention that you might need to update that, but I don't know what we need most in features of performance along the way that this is like four versions back, then it goes back to 2016.

B

It's an interesting question: I wouldn't have guessed that that would happen so.

C

Yeah, because they BN sort of like, has a very for I, guess, process of accepting new packages and just getting a buildup.

A

I, don't see that is the problem. I mean I, don't know very much about different versions of nginx, so I feel like. If there was a problem we probably would have known about it. No um I had another thought. What was it lasted? Oh, we should add emoji support. Oh yeah,.

B

A

Sequel version was too old yeah. We should definitely do that.

B

A

B

The second site people are gonna use.

A

B

That's a great idea: okay! Well, let's, let's try to get the forum site moved over as soon as possible. We did last week's migration on Thursday, like you know, later later this evening, I'm I'm, like super, stressed out with things, though so I, don't think I'd like to do that before DrupalCon anymore.

A

Can I do your job yeah.

B

Which it wasn't very much oh.

A

I, don't have DNS access, yeah.

B

I, can we could get you that access time, that's that's actually I mean I can be Pat Larry, that's really easy. It's validating and making sure things are working and that sort of thing so do.

A

That part yeah.

B

And so you can do all of it just by pointing your etc' host file at the new domain name and then and then checking all of it. Okay,.

C

So last time we love you David ckeditor, and this is related. There were two features, but now it's sick, to my mind like which one it was support for at like mentions and or emojis or both something like a hugging that allows that in ckeditor anyway, it's worth exploring. But but that's that's available. I, don't know what we have to do with the integration make it possible, but yeah.

B

There's already a plugin for that you're just saying it would be nice if we did have a plug-in for that.

A

Here is module for that and I think it has a backed up version already. All dimensions, I think we're. Basically you at mentioned someone in a comment in Italy email, a notification unless they're.

C

Not sure yeah, also, if you put it on comment, then it's um like- creates a link to that user's profile or something like that yeah. It wasn't impression that when I was being the the upgrade for city editor, I went through the list of changes and I saw either that or emojis being added yeah I.

C

Remember now, I'll have to deftly. Do it again? The way excused minor versions are together by the way, the only things that things was landed azharuddin than just small small things, but we might be to do that.

B

And Sikandar being able to actually type of real emojis. That would be really cool, my god.

A

There's an emoji keyboard with like a button and like pops open a thing, and you can like.

B

Yeah that like, if you use the colon key, you know how you can call in and the type smiley you know it's like your kid or github yeah. That would be. That would be useful, I'm sure that exists. Yep yeah, it's probably a matter of time before I have become too operating system-level stuff, though yeah it's.

C

The only people emojis like mombi, jewel ones, yeah.

B

Yeah MacBook Pros aside, like I'm sure that we're going operating system opening.

B

Maybe that'd be really annoying if emoji started popping up like everywhere. It's like in your.

A

Right Anna, :, yeah.

B

And your text editor is like, maybe that letting.

A

Php can't process lame-o cheat.

C

C

Nathan she loves me, she loves it. I.

B

It's actually been tested and proven that you can have a module whose name is an emoji so and and hooks and everything work in PHP. So you can have like hook, poop and hook oak smiley and hook like it's. It's so ridiculous. I can't believe it actually works.

B

Module invoke all poop Charlie works.

B

Okay, sorry, it's fairly not what we need to mention on the weekly meeting, so okay anyway, let's also mention the API site which the API site did get cut over I. Don't think we said that quite yet, but there hasn't been any problems that I've seen. Does anybody else have any issues with the API so you've.

A

Been using it and I forgot, but it was on the new server and then when I saw that in the thing today, I'm like oh, that's great, because I didn't even notice, though it's like perfect that it's yep, you know I'm noticeably different. That's great SuperDuper.

B

A

Faster but I wasn't paying attention so yeah.

B

Okay, so should I start going over the it shoes for 112? Ok, all right, so we usually go over to 112 or the current minor versions. Bug fixes that we're currently prioritizing and we found a bunch of them that need some progress. This past week the TK editor and I'm getting a little like go meet you guys, okay, so in 112 6, the CK editor icons have been broken in the RTL right to left language languages for quite a while and 3504.

B

The margin issue that we've been experiencing has been fixed. Finally, and it looks like we're now ready for a review. Thank you. You know both Jen and Gregory, for for knocking about, went back and forth. This get that one fixed supporting multiple equivalent security releases issue. 35 24, there's still no code to back this one up. Yet there was a question in the issue about where the code should live.

B

Yes, it should be in project module, so that probably means we'll need to update project module which is lips and contribute project nonchalant to backdrops ENS org.

B

There's been a fatal error if you have options, element installed in backdrop, 111 and then upgrade to 112, because options element was merged into core the same function. Names are present in both options: module and in options, element module and it causes. You know. Same function is already declared error which the Crushers everything we found out in that issue. Thanks to some experimentation, that's using the backdrop, merged modules function that that will circumvent the problem of loading options, element module after it's been merged into core, which is awesome.

B

So that issue has been marked our TBC nice clean solution there and I'm glad to see that coming together, layout clone breaks of both layouts issue. 2673. This issue is a big problem and there's a pull request that fixes it, but we need tests to confirm that the problem is solved and we want and kind of regressions in the future. There's already it like a lot of layout tests. I don't think this is actually a very difficult one to test for there's no JavaScript involved or anything like that.

B

It's just doing the same thing as you would do in the UI and making sure that the layout still function, but that one's been held up on tests for quite a while. Unfortunately, I did get to add our new tag for needs. Tests to that issue, though, which made me happy.

B

Missing, contextual links for views issue 2690 if you've got a page based a view that defines a page call back the contextual link for editing that view gets stuck underneath the administration toolbar, there's four requests for fixing that it currently needs review. It just changes where the contextual link shows up so that it's a location that doesn't get covered up by the admin bar.

B

It's a good fix, I think that if we get some additional eyeballs on that confirming that it doesn't cause any regressions, then that can be moved in and, lastly, core updates occasionally can fail due to a missing type property in that info files of profiles. That's issue 3553, and that one is currently our TBC and it just goes through an adze type to all of the profiles that are in core. So those are the issues that we've got for 112 six, that are prioritized all of them.

B

I've been saying some progress, which is great and yeah once once we have this together, Gregory I know you've you've last mentioned like after we get those done. We should we should make a release because yep this.

C

There's another notable mention they get the most filed by the passes any Zilla, three, six, four nine. He was trying to port navbar I think to the backdrop and then I think that we are calling admin bass suppress function within so we haven't accounted the fact that that we openly bar model can be disabled. So yeah there's a very simple solution to that: I just call a wrap the function and around the audio exists, but we need to call that from system or something or comment. I have added some comments there about possible solutions.

C

I would like some direction of where this function should be padded.

B

B

I'm just saying yeah, I I, don't know I think maybe just what you have already might just be sufficient, where we just check if the module exists. First before we call that function, yeah.

C

But I think that we started like solve that issue one, but it is that way or specific things like or the module, whereas other country broadcaster modules might want to suppress the new member. So we shouldn't be calling the admin bar suppress in faction collected. Maybe you should have something like a back table. I've been buying, suppress, which is called from distant module, which ensures that the consistent module is always enabled yeah.

B

No yeah I see what you're saying but I think that checking of the module instances are kind of de facto solution for modules that are optional, like we do this kind of thing like if module exists, comment like if comment module exists like all over node module and if module exists.

B

Let's see, what's another good example, we do if module exists, translation very frequently to see like if translation is available. If module looks this locale, so I think the business are just our standard approach. If you need to call a function, that's with them an optional module. You should call it module exists. First, okay,.

C

I'll follow up fully first sort of thing, because it's a very simple, straightforward solution: yeah.

B

Yeah, so that's a failure on our side and if contributed to the same pit and that's that's a problem that they should use the same like you should do that before calling any of any optional modules functions.

B

Okay, let's see next up is issues for 113 113 will be coming out. May 15th, which is coming up really soon. May first is going to be our feature freeze as always, so some of these are probably at risk. We'll go through them. Add back field for matters issue 1376 currently needs testing and code review needs testing. It might actually need new tests itself.

B

Oh no herp dual has thrown on some tests, but I, don't think that he's pushed the tests to the poll requests yet so there are tests available that we could potentially swipe from the compute module, but I don't think that they actually include the tests themselves. Quite yet, let me see what does nice okay great so that one's in in really good place? Then it actually has tests. It probably literally just needs manual testing, plus code review issue 1376 at backfield for matters issue 495. The dashboard currently is in similar place needs testing.

B

Slash needs tests, gender. Is there anything you'd like to say about the dashboard Montrell.

A

No I'm gonna look at um Gregory's changes later today. Okay,.

B

Let's see adding translatable strings to chord, config files issued 3455 says here in the agenda no PR yet, but there is a PR for for this yeah. Actually, her bill posted this right after it, you said, there's no por request. He says, there's one so sorry this this issue of adding translatable strings to config files is something that we can iterate on progressively throughout releases. So any any start that we have to start adding these translatable strings to config files. We should just start adding them as we get them complete.

B

So if this issue has been hung up, it needs her people her quite some time. Her bill filed it a couple of months ago. Actually, so this is pending some eyeballs to look at it, give it the thumbs up and then once that's done, like there's lots of other core modules that all need to have their config files updated to list their translatable strings as well. So the first for request is just the initial one that does it or a few of the basic ones in system module.

B

Let's see package signing issue, 1992 I've been taking a look at this recently, but I think this isn't one is likely yeah likely not not going to be going anywhere very soon. There's a lot to review there it and it is only a nice to have it- increases the security of packages as they're downloaded from github make sure that they have been packaged by backdrop CMS org, so we still have some more work to do there.

B

Let's see telemetry issue 285. This is been one that we pulled up as kind of like. Yes, we definitely should do that this release and then we're all I guess we should do it again and then I.

A

Just added a comment: thank you. There I think, even though there's nothing yeah like we I, don't think we should add any of the new functionality like new reporting between now and the next. Surely so, what we can do is pull out the current reporting and put it to its own module. So if we want him to be progress on it, I think we could still take the first step. This is another thing you can go in like baby steps, or it's like personally want to make a module in a second.

A

We want to add a bunch of stuff to it. um So I don't know if you think all that stuff has to get done at once, or if you think it would be okay to like do the cleanup stuff first and then the new stuff later interesting.

B

I think it depends on how we want to handle when we add additional information that we're collecting, because when we asked the person for permission the site owner for permission, saying do you want to send additional information to backdrop, CMS org?

B

If we tell them what that list is or let them see what that list is we probably shouldn't blindly just be adding more stuff later, without telling them again that we're now collecting more information than we were previously and.

C

There's no problem adding there's no problem in that meaningful message, especially if you have the dashboard. It could be a notification thing in any store and saying this is what can you please please review what has changed and we accept Realty. No doubt yeah.

B

Interesting, we need some kind of my name. The dashboard doesn't have any kind of like notification system, so.

B

C

Idea was that the test book could be for news updates and stuff like that.

A

C

See how we talked about cutting out a release candidate or just so that we can give people more so like a pencil to test what's coming up so this the best word thing could have been a great opportunity to sort of like communicate.

B

Yeah, okay, okay, maybe maybe I'm thinking about a problem that might not be too big of a deal so anyway, Jen it's not a bad yeah. If we can get to that point of like just creating the telemetry module and moving update module stuff into telemetry yeah, that would be great and still will require. You know the API part of.

B

um Maybe it would record the API part of the receiving end on back from CMS org I'm, not quite sure.

C

So if we don't touch that, what was the plan, what was it a foot there then just move functions that have to do with so that that means renaming the function. So we would have to put dropper functions in place so that maybe.

A

I'm not sure what all is in there now, but I was gonna. Take a look at it and see: okay,.

C

Oh, it's interesting, I am for the idea of this. The babies. That's the way yeah.

B

You know something that has been challenging me with this telemetry initiative. Is that separating out project usage from project module? Could you know be challenging and not not really provided so much benefit? You know like project module already is collecting its own usage statistics and then it's integrated directly into project control on backdrop, CMS org via the you know, the usage charts, and so that functionality is still useful and- and it literally is on a per project basis, rather than a like.

B

If a module includes like four sub modules- yeah, you don't know which of those four sub much was this turned on, but from the project module standpoint its you, don't I mean you just care about the overall usage of the base module usually like to see how many times your module has been installed. The entire project has been installed and further granularity than that sure that can be prior to limit your module, but actually tracking.

B

The usage potentially should remain in project module, so maybe maybe as far as project module like suppressing the ability to be tracked but maintain the ability, the update. We should leave that entire API alone and by it's up and and just keep it working as it is, but add a query string option just to suppress the tracking so rather than moving any of the API is around project control. Just leave it all there, but have the ability to disable the tracking yeah.

A

Just a new module that tracks stuff that doesn't go into the project database yeah.

B

Exactly something completely separate so that we don't end up with the project module like project modules, already a huge hassle for us every time we need to make any changes. Yeah. Okay, though good.

A

B

And telemetry, because telemetry we're talking about is this being like backdrop, CMS specific, like the receiving end of that API probably doesn't need to live in contribs. You know it could just be part of back to up CMS org and that would streamline our development processes whenever we need to collect additional information. Okay,.

C

We've got some spin of doing the minimal thing because, because now we will be giving people the option to sort of like disable any statistics that they provide to us, and this is useful to us and I understand how this can be a problem. Instead of have a everything or nothing, we could have a very minimal thing. The thing that we're doing now as in yeah. This is the type of information that we would really like, one which would be all.

C

But if you're too, like cautious about what this means and there, at the very least is send this information. So yeah have people say very minimal, send very minimal information or help us out gather it more than, but this be, as I said, iterative like let's build the basic thing now, so that is that mean it's have a basis, and then we can improve well.

A

I think there might be a way that we can set the current stuff that we're sending to be like anonymous by default and always send and then, as soon as they enable the query string that made that anonymous and then we give them an option right. So that's what you want to send us more information and if they want to be public- and you know he might.

C

Be a my idea: was there didn't my deal with, everything would be anonymous. Anyways yeah.

A

B

A

B

Yeah I mean the IP addresses are only kept for the purposes of making sure that it's the same site and they're discarded after two weeks, so I mean you're right that it's a fully anonymous, but we can't make it fully anonymous and have it actually be accurate tracking, like we have to keep track that that stuff.

C

A

B

Milestone some of them field for matters that or some translatable strings, are in good places. Telemetry package signing not so good, so I think we'll probably end up seeing some of these things on the chop block here in the next couple of weeks.

B

But chopping block just for the next release.

C

With the Drupal compound sorry coming up, it might be sort of like too ambitious to go in for a bad picture, at least, but do you think after that, yeah.

B

Yeah I've got a got a lot of head space and DrupalCon is Lola BOTS, sending everybody in the company there and there's a number of events that are happening.

B

But after let's see what would that be after April 12th, that's only eight, but you know two and a half week window, but then backdrop will be my focus or there's a couple of weeks so that we can. We can make a bug-fix release at that time. Yeah.

C

We can iron out all the issues that are sort of like almost there by then yep.

B

Assuming that there hasn't been another security release between now and then I.

C

Noticed that in the previous secret release, we snack some black pieces as well in there. Well, as my impression was, that security releases are solely so like episode, security release alone, but yeah yeah.

B

They're, not the security releases include everything that we've been, including in a bug-fix branch up until at that point, like yeah, that hasn't been that, but that's the way we've always proceeded, but sometimes it just happens that nothing has changed between the last releases and the security least but Freight for the most parts. Yeah. Anything that's in the bug fix branch goes out at the same time as the security release, yep.

B

Okay, anything else you guys would like to mention or talk about.

C

One thing that we mentioned during the previous meeting deserves to be discussed here. That one is, we have now jump, oh, that is been working. You have a use case which is having a contribute that has its own repository, because they want to maintain separate branches for d7d age and backed up versions, but because that repo is not part of macro contribs and that module the respective backup version of the module cannot show up in the project value.

C

So Jen mentioned that there might be some feature in github that allows you to clone everything and then keep it in sync yeah. We need. If that doesn't work, we need to figure out a way to allow contributors to keep their own repo, but at the same time, have the respective version of backdrop module three more layers be shown in project browser.

B

Sorry I missed him. Why? Why do they need their own copy that separate from the backtrack controller, so.

C

In this specific this specific example it's the is a repo of the European Commission and that they're managing the Atomium thing and they would like I just have more people than just a single maintainer. Looking after I guess the thing that repo, the decent version is actively maintained, the d8 is being worked on and the back to version has just been ported. So I guess that the European Commission would like to do thing.

C

Ownership of that people.

B

Well, how are you sorry don't they need to do the same thing for to be listed on drupal.org? They have to push in to Drupal's git repository right.

C

I'm not sure it's time, yeah.

B

I think that's actually kind of fine. If they want to manage to issue queue separately, they could possibly do that. You know maintain a mirror basically, but when it comes to actually cutting a release and pushing it up to backups, you messed up, I think they do need to have. That being the backdrop can't rib repository because it because if we need to like like per policy, we do if we need to do as security really. So we need to have the ability to modify the code that is delivered through backdrop to to our users.

B

So they kind of have to have it in that group, but but you're right that they could use some kind of mirroring functionality, but they could hook that up on their side that when you push to their mirror, they could have a hook set up. A web hook set up to just push it to the copy. That's on the backdrop construe as well, but I think they can do that without any intervention on our our part. So.

C

In this these days, though, we need to document, because so far we have been documenting how to mean still repository impact for country. We don't have any instructions for people to create a clone of the repo, retain the original one and create a cloning back tripping trip. So you know.

B

Yeah yeah I mean we don't have any in search of it, because it's kind of you know I'm, not even sure you really want to encourage that, but it would be possible.

C

So we will treat it sort of like Bert case, like even even in these situations. If Paul comes to us and says okay I want to do that. How do I do it? Do we do we treat it like that? Let people just ask the question and then we don't have to do it, then, even if so, if I was to help them out, I would still like pointing to instructions.

B

Yeah I mean I, think insertions are fine, but I think I'm, saying that I'm not sure that it should be official. You know so so it's really strange, but it's like well. If you want to make instructions, then put them someplace else.

B

C

Thing with the saying yeah you.

B

C

B

Probably even could find existing instructions like how to mirror or something on github. You know they're, probably already instructions for an academy or something you can give up and get out of mere sum between two github repositories: I'm sure that there's already a tutorial out there that's been written that covers the Sears case, I.

C

Tried to do some research, but I couldn't find anything automated everything was mentioned, but yeah when you're developing your local just goes to both remotes, which is yeah yeah.

C

If it's a one munch, oh yeah, it would work, but that's still it's the in the case of the specific people that is uh people from the European Commission managing it I guess, there's more more than one person anyways, we'll figure it out.

B

C

A

Sorry, can you cut out Oh.

B

What is it that you wanted add me, yeah did I saw you unmute earlier, so I thought that maybe you wanted to say something. Oh and.

A

I thought I thought I was gonna, say goodbye.

B

And everybody up there watching. So, thanks for all the work, that's gonna make you and I'll see you guys. I'm, like okay,.

C