Backdrop CMS Weekly, 6 Jul 2017

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Backdrop Weekly, July 6th

Description

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

A

All right we're on air happy, Thursday, July 6th everybody new month, since we last met very exciting um going through our oh. This is a backdrop weekly meeting, usually development, related tasks. um First item on the agenda updates from the PMC PMC is currently working with the software freedom Conservancy about getting fiscal and lead a legal sponsorship from them. um They've created an issue in our github issue queue. It's issue, number 27 53, where they're asking the larger community for feedback about starting the legal agreement to make sure that there are no serious objections.

A

So if anyone wants to read up on what that looks, like there's a great post there with a link to a PDF that contains a sample copy of the agreement, if you want to see all those details and currently they've stated that if they don't receive any objections by Friday, the 14th of July they'll execute the agreement on that date. I think there are objections. We also have the opportunity to work through what those are with them and we can adapt that contract slightly if needed. So it's not.

A

This is not kind of a one-shot deal.

A

We have the opportunity to get exactly what we want out of it, so to encourage anyone who's curious about what that relationship looks like to read that over in and we can work out what is best for the whole backdrop, community um other things that are going on we have over the last week we've got some existing Drupal module, maintainer z-- that have come to back up and found that their modules have already been ported, and so we're currently working on adapting our maintainer agreements to account for people who are criteria like applying to join the contribute, specifically to Co, maintain projects with existing backup maintainer.

A

We don't have that use case outlined in our current agreement. We want to make sure that it works or them as well. So it looks like we're that currently stands is right. Now we have a section for people who are submitting applications, lip code and a section for people we deem non coders, and my current recommendation was to take the non code or section and just rework it, so that it's people who are applying without code and that way it can be for coders who are applying without code and the same process would apply.

A

So they need to have an application, a statement of why they want to apply and then to people who are already contributing vouch for that. So well, Yoriko be like. Yes, I really not just.

A

We know we don't just have one person getting all their friends involved are, however, dollars. So um that's what I currently stance? We just have to rework our agreement so that it's a little more inclusive for everyone and welcome in particular to Alma, dough or Muhammadu, who is interested in Co, maintaining SMS framework with Doc, Belmont and I brought that issue to our attention. uh All right. Jeff. Do you want to talk about just on to backdrop, CMS org, the website Justin doing some work on that over the last week.

A

You want to let us in on issue 243.

B

Yeah yeah it's working pretty well, but when it goes out and fetches the comments from github its incrementing by 27 I, don't start some kind of a date stamp issue. So I think what I really need is more developer eyes to take a look at that PR and see if they can spot something Simon struggling with it for a few days and not been able to see any reason why that would happen other than perhaps the timestamp, maybe a difference between the timestamp.

B

It gets from the server compared to what get help is time, stamping things up. What I haven't been able to prove that either but I'd love to get that in so I could want to working on other things. Okay,.

A

I mean the poor request is: can you just link that from the issue yeah.

B

A

Be great possible to find for what's on github.

A

Okay- and that was specifically to get better usage statistics onto backdrop, see mr. Berg from github yeah.

B

Let's get in the commits in comments: okay,.

A

B

A weekly basis, the issue is to get the users to buy. Think for now we should hard-code the users until I can figure out some reasonable way to get that so I think we should just make a human guess at that, and you know and put an initial seed there and.

A

This is for back job core or for all kinship projects. This.

B

Is for a backdrop CMS that Horton? Oh, where.

A

B

Counts the commits from backdrop core and it counts the comments from backdrop core and our backdrop, slash backdrop issues and from all the contributes that are sub under backdrop: contribs, okay, great.

A

um All right, yeah I, think that's reasonable. We also like I'm, not sure yeah. We can figure out where to get that user account from later, but we should have like if it is kind of a guest number and we are going to launch the redesign with that number. We should make sure to update it regularly, so we just create a task like every Thursday, so make sure we're not missing something you know doesn't go on for forever without getting up dude.

B

Yeah fair enough.

A

Okay, that's great thanks for working on that. No.

B

A

Nate, do you want to talk about a backdrop, stand with itself.

C

Yeah, okay, so we're in the world of developments. Things are rolling long. The last version of backdrop that came out backed up 1.7.1 came out a couple weeks ago. No so we're working on 1.7.2 as the next bug with Figgis release. There are a number of issues that are tagged as kind of being well they're tagged as being 1.7.2 issues, meaning they're, either easier or slightly more important, or just something that we should get done in the near future, and you can find those under the Abhishek tracker tagging 1.7.2 in that list.

C

Right now, there's a couple of our TBC issues, which is great to see and sort of need review, so I will probably get in a couple of those items right away. As for the release date, a 1.7.2 no super high priority items, so I'll just continue rolling along until we need to make a release before the next point fixes so 1.8 1.8 is our next minor release and the release date of 1.8 will be September. 15Th 2017.

A

C

We've got a number of items that we have called out as being higher priority that were attempting to make some headway on that includes layout relationships which is issued 2134.

C

There hasn't been any notable progress on this since last week, so I won't recap. It's unnecessarily still needs work, so the media, library, media library, we're hoping to add a lot more file, handling and image handling capabilities in factor of 1.8 and the main meta issue that is 1448. Al Burroughs, akov and dagger. Heart have kind of been tag teaming those issues back and forth, though, that we haven't seen any activity and a couple of weeks there, but there's a lot of work to be done.

C

It's been split up quite nicely so that those things can be done in parallel, plus. The definition of what we're attempting to do is also laid out really well, thanks to those guys for making those issues and kind of spelling out the battle-plan really pretty.

C

Clearly there I know they've also done some work, although I don't think I've seen poor requests and all of those individual issues as of yet okay and lastly, and the large feature categories, config, translation issues, 704, we laid out kind of a basic premise of how we can tackle config translation in a backwards compatible manner.

C

Generally, it looks like you know: we've had a little bit of feedback on there generally people if at least not raised any red flags about its.

C

You know, they're, not saying that that there's any problem with it so I think as far as the the basic idea, like we're kind of ready to put some code behind it, so we'll probably I'm hoping I'll be able to tackle some of that work and so probably, hopefully see some code to back up that battle plan in the near future.

C

Anything else anything else from you guys that you'd like to call out in the 1.8.

C

Let's see, there's also the github issue tracker for 1.8 milestone, which I haven't taken a look at recently.

C

I, don't think it looks like I. Don't think that there's any items in here that really need to be called out. Most of these are some items under the issues that we've already heard.

C

Yeah, that's it so backdrop, two decks.

A

C

Much for it maybe not much for them in the future, but we have that in the agenda here as as being item, and we talk about this regularly. We saw him quite decide to what to dot. X is going to look like there's some suggestions. We could potentially add functionality like automatic updates. As an item fits is of interests and we mentioned it last week. That's there's been some excellent work in a project called curator.

C

The link to which is in the agenda and curator would make it so that we could do automatic core updates, which could be kind of cool or other functionality like import/export functionality from other systems, including WordPress or, potentially you know. Maybe it's not about features at all, that we're only like remotely deprecated functionality and to dot X is really basically the same as the you know, 1.8 or 1.9.

C

Whatever the previous version is so there's some things, some decisions that we need to make around how we're going to deal with one with two decks, and even the timeline is a little ambiguous. Like you know it, it would be January 15th if 1.9 rolls over into 2.0, but there's nothing preventing us from making 1.10 or something like that. So we have some discussions to have around what our feature looks like post facto up 1.9.

C

That's it that's it for the status update on back to software.

C

Do you guys have any questions any discussion? Anything you guys would like to talk about during this meeting.

C

Negative, okay, Jevon anything else, yep, okay! Well, that's it then. Thank you, everybody for joining. Thank you guys for watching and we'll see you in the issue, queue and catch you next week.