Backdrop CMS Weekly, 7 May 2015

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Backdrop CMS weekly check-in 5/7

Description

Check in on Backdrop CMS progress, in anticipation of 1.1 release NEXT WEEK!!!

A

Alright, ryanair, it is Thursday, may seven um happy night, everyone we're gonna check in really quick today on the most important items for backdrop, CMS development.

B

A

Is backed off itself, but also the infrastructure and backdrop that we also need to get set up. um For starters, we still have free phpstorm licenses for backdrop contributors. So if you want a phpstorm license- and you are backdrop, developer- send an email to info @ factor of CMS network and one of those will get mailed out to you if you're not yet a backdrop kinship developer, you're, not yet a member of the backdrop kinship group on github.

A

um If you are interested in reporting or maintaining a module or adding a theme or layout or anything to that group, we can help get you through that process as well. um Read the readme in that group and there's links to help get through that. So anyone who wants to be a backdrop kinship author gets a phpstorm license thanks to phpstorm, so that's really cool. We also have a bunch of fancy new swag for a triple con.

A

I just had the stickers, but now I've lost them, but there is a link in the agenda to our tweet, where we had a picture of the.

B

A

They came out really great. We finally got thickers, maybe a little dragon on them. So if you wants to grow the dragon and not our boring square logo will be handing those out a triple con la next week, and we also have a new run of t-shirts that also just got finished in our getting meals there as well.

A

So um officially, the best place to meet up with anyone associated with backdrop to grab a sticker or t-shirt will be at the Drupal watch job author meet-and-greet, specifically Tuesday at ten fifteen in the morning, we've got an hour blocked out there for anyone, who's interested in coming talking to us about backdrop to come meet at the day stage and at the LA Convention Center, where the Drupal con madness isn't happening and we're just going to have a suitcase of stuff will be hang handing out so we'll be able to roll around with it all day.

A

If you end up meeting up with us somewhere else, that's also fine, and if anyone in this call wants to help distribute stuff, if you guys are going to be a triple friend, we can give you like a handful of stickers and handful t-shirts and just say anyone sandy stout, then there's more likelihood people meeting up a backdrop person to try and grab swag.

A

So since we don't have a table or a booth or a official place to distribute that we're going to try and do it at the drupal watchdog meet and greet, and then if you can help us to show beauty, that would also be pretty cool. And then friday, night after drupalcon we're going to have a backdrop. 1.1 release party and we'll probably still have some stuff left by then, and if you want to meet with us at a local brewery, we're trying to get that little too and we'll have stuff there and hand up.

A

Hopefully, so that's tentatively that the plane had that stuff out and then you can always get more printed to the runner to LA. Any other hand comes up if everyone really lots of dragon stickers will get more dining stickers. So so far they look really cute all right, um so Nate I don't know if you've gotten a chance to look at these community growth numbers, but I did update the number of new projects with official releases that were on back top CMS org, and so since last week we have eight new projects, which is good.

A

That means we had eight year leases since last week we have 34 total projects, and so those are projects that will appear on the backdrop CMS to org modules page as soon as we go ahead and turn that on so that's that's coming pretty pretty soon as well. um I think the number of kinship authors is still 34. I checked that I couldn't figure out how you normally do the count for kinship projects cuz.

A

It wasn't obviously on the github group page things count there, but I think that's still pretty close, so it was last week mmhmm.

B

Yeah, there's only one one new project on github and fluffy: okay,.

A

um So I still think that's pretty good. I mean the fact that our current projects are getting updates is a good sign. The fact they're all going to end up on our primary website is also really good, and everyone is really busy right now. What's your book on coming up, so those will probably start to grow again after we get 1.1 out will be a flurry of new interest. um Okay, two other things that were working on um the backdrop update server Nate.

A

Do you want to give us something on that, since you've been doing a ton of work around it lately, yeah.

B

There's nothing new there since last week we already have everything all in place: project module and the update status.

B

Well, project module provides the connection for update status and it's still sitting there on TMS org ready to be turned on, but we haven't turned it on and yet again.

A

B

Of think that the project repository fewer and the update status will probably all come along all at the same time and probably post the 1.1 release, because we've got our hands full right now with just getting the next version out. So I would say: look for that soon after release, but up until like you know, for the next week, we've got our hands full. Getting at one point, one.

A

Great- and we also have a bunch of work going on with a dress and backdrop, I'm not sure that's got any progress since last week, but I think we're in a pretty good state with it being ready to go. We just need to build something into backdrop that will tell back job um while the josh commands.

A

Do you so that when you do like address, CCL won't try and call a triple cache, clear, functional call backdrop catch their function and I think we'll be good to go soon as we get that mapping in there and our primary website is also kind of on hold right now, just because we're so focused on back shop, the product. But next on our list is getting those modules things in layout sections built out.

A

We have designs for the search listing page and we've got, um I think, a first round of designs underway for the actual project pages themselves and that's based roughly on what we've got on triple that or that we really like and a couple of other sites that have extensions or plugins or other things that you know of the same ilk of what we're looking at, where we've stolen good ideas from them too.

A

So if we will get that wrapped up shortly after 11, is out and get people using our website to download the mod modules to the themes and layouts instead of just using github, which is really good and then as soon as we get those three modules, layouts and themes, sections down on the site, we're going to shift our focus to setting up a showcase, because we know we have all these people building backdrops. But we don't know what they are.

A

We don't have anything to point to when people go, what size running back, Jeff, it's like! Oh the API site, the backdrop cider yeah, so we'd like to have a place where we can kind of show those off. As well and for poly people doing all this hard work on their back drop sites, give them a place to kind of post the stuff they've done to, UM and we've got other plans to that are further down the road. We'll worry about those later all right, fun stuff.

A

So we're going to talk a little bit about backdrop, the product itself. We currently have a.

A

Patch release that I think is close enough. I I, don't know at this point we're so close to 1.1. If it's even worth doing the patch release, maybe this week and then do the 11 release next week, and that way it would give us a chance if there any issues with the patch released, we could fix them before 11 I have a feeling we're probably going to be doing a 1, 1 1, I'm pretty shortly after 11 anyway.

A

So I don't know need if you have any thoughts about whether we should try and push that patch release out before the 11 release or just save our effort for 11 itself.

B

Yeah I, don't know, I mean I, guess we could go ahead and make one final release of of the one point. Oh branch I think that would be fine, but yeah we're pretty much yeah I mean where we're focused on 1.1 at this point and so trying to fit in more into the one point 0 point: I guess it would be one point of point: six probably does and have a lot of value. So, let's yeah we go ahead and release one today, I mean there's no reason not to that.

B

Just has minor bug, fixes and everything that we've got so far and then 1.1 will be out next week.

A

B

A

John also pointed out that Drupal came out with 737 today, so I don't think we're gonna get those changes into our next point release, but maybe we can take a look at. Why was involved in 737 and see if we can get anything that applies in 211 I. Think that would be good. um So I'll create a metaphor that if someone hasn't already, um we can work through in the issue queue and see how far we get on that.

A

But we'll see. um Okay, so big, exciting thing is 1.1, which is coming up next week, and for that we have a couple of things that are going in. We've got a new administration theme, which is looking really good and we have a whole bunch of four requests that have been merged into a separate branch for the the new admin theme.

A

That I think we still need kind of a holistic review of how all the paid all of those changes look together, but I think we're looking much much better than we were even a week ago on that front, and then we have the built-in auto module, which may be neat I should let you take it over from here to talk about token in pasado, since there's been some big, exciting news since last week, yeah.

B

So token, uh I think even last week token module head had already been in core, which is great so token modules already all in core with the UI and the browser and everything which is fantastic and then pasado I picked up Jeff's work on pasado last weekend and started revising it and it all looks really really good pasado. The pull request that we have currently on that issue.

B

It functionally completes it, it totally works it passes all tests that were migrated from contribs was some additional ones that we added and all existing tests are all updated to work with it as well. So the pull request is pretty well done. The tester passing we really just need review on that to make sure that we didn't introduce any regressions or anything yet Jeff.

B

Thanks for volunteering to to take a look at that, yeah I think it looks great I'm going to do my own code review on it, which normally just means anoma just means things like comment, cleanup and code structuring and making sure that all the dark blocks are accurate and everything like that. But I think that's pretty much. The only remaining parts of the path- Otto pull request, so we're in really great shape, I mean tokens already in I mean it is a little bit of a cram here.

B

I mean we've got eight days before the release, but with the poor, requester pad already, and the quest for the new admin branch already merger bull, but just not totally polished, yet I think we're in great shape in both places.

B

I'd really like to see the the admin theme, branch merged pretty much immediately and then probably the path auto branch sometime over the weekend and then and then I'll, be drupal comp right and then then we'll have that little period of time to actually do a little bit of work while I know Jen and I are going to be there, but but we'll still be doing a lot of coding and everything during the day, because I don't think at least I'm not officially attending to poke on I'm, mostly just going to be crashing parties, and things like that.

B

So that's it for me.

A

And one thing we did discover to as we're looking at how pasado works, we kind of realized more and more that we need some sort of redirect solution in core, and this is something that started actually before. We started working on path auto when we started looking at clean, urls settings or like we should just have like a redirect tool in here.

A

So we can just have a check box is like redirect from monthly to clean and we're like wait a minute now that we're talking about redirects like, should we also think about that for pasado, so I think something that we should start thinking up after we finished 11 is looking at.

A

When do we want to get some kind of redirect functionality in core and it might be as soon as 12, just because of the way that, where you know when you have multiple paths for something it gets a little bit messy and since we're putting the ability to put in not only multiple paths but automatically generating multiple paths, I think the need for that didn't come up pretty quickly, and since we have a redirect and King trip for than what we want to do in core, we can look at how that works and try and see like with the path automic or adding the redirection kim trip.

A

What parts of that are essential that we should just have some check box looks like always you're directed to canonical or something like that. It's going to need some more thought, so we're not going to be able to do it by 11. Obviously, we have so many days, but I think it is the kind of thing that we're going to need are going to want to include really soon, and so, even though that's something that maybe not everybody knows that they need initially.

A

When you're building a site, it's something that a couple months later you're like oh, why do I have these two pages with duplicate content, or you know this one link means to one place and this other one links to another and how do I fix that they're supposed to be the same? um So that's just something that I think we should think about shortly after and and maybe we'll create an issue for redirecting for talk about the options in the queue so keep an eye open for that.

A

So you can weigh in on how much, how much of that you think should be included, and if we can do it really in a in a much more straightforward way, apparently aunt alania. um So that's a thought that came up from a photo.

A

So I think that super exciting we've got a whole bunch of other stuff we're working on. That's not necessarily urgent. It needs to be done by 11, which is good a lot of time left, but we're always working to improve user experience, developer experience and any bugs. Obviously, the comment that we would like to get fixed. So we have tags in the HTTP there's actual time for a bug. We've got an issue: title prefix for user experience and developer experience as you're working with my crop file issues a lot.

A

We have an issue, we can fix it. If we don't initiate, we can't so every time you run into have anything. Let us know we'll prioritize. Accordingly, you find something different, obviously going to need to get fixed sooner rather than later, um every Thursday. After this meeting we usually have a little backdrop sprint in IRC. So if you can get an hour to a week from your brass to spend some time working on backdrop, doing it on Thursdays is good. They also often spend much time before this meeting working on backdrop.

A

So if that doesn't work for you, that's fine, of course, if Thursday's aren't good any hour of any week is always appreciated, show pitch in whenever and, however, you feel you can, if you can or if not you know, just put stickers on stuff, that's totally acceptable as well.

A

We also have a reddit channel if IRC isn't your thing, a subreddit at reddit.com, /, r, / backdrop. So if you have going to ask questions in that in a way, that's a little more permanent, a little nerdy are in a different way.

A

They've read it's been super successful for us so far, so that's a good place to go and ask questions until we end up getting that, but you know our own stack exchanger, who knows what might in the future, but for now that seems to be working really well um and uh yeah we'd let these meetings every every week on Thursday.

A

So if you have, you know, wanted to get involved in to know where to start coming to the meetings might be a good place and if you just want to hear what we're working on meetings are always fun for that too. In yeah, you can find people working on back up in on twitter, using the hashtag pound backed up CMS or we have yeah I, guess that's probably the best way um asking questions can also be done through a contact form on our website.

A

We've got an article coming out in the next year poll watchdog magazine where we have a faq section where you tried to address the questions we hear most often about backed up and there's also a super big in-depth feature story on. If you were to build your next project in back job. What do you know what you need to know that is significantly different from Drupal 7, which I think will be eye.

A

Opening to a bunch of people also put some code samples which a lot of people haven't seen yet, um which I think will be any will be good in a perfect timing coming out with finale so yeah. We would love to open this meeting up to anyone who has any questions or comments right now or, if not that's fine, too, all right um but yeah. So any questions or comments come up.

A

If anyone's watching this video later contact form on our website, you can use Twitter, you can jump in the IRC channel and see if there's a new in there or you can ask on reddit and there's usually always someone around to feel the question. Even if it's not the one who can get into it, we can usually talk to each other and try and get someone around. Who knows how to answer the question. So that's good um also, it's just nice to see siling faces in here.

A

So thank you guys for joining um yeah and I.

A

Don't know I guess it looks like we have one question. um Thoughts on Drupal, 8 cm I aren't really sure how that um how to approach that question. Why mean we have cmi? They have seen a my slightly different.

A

Do you want to elaborate a little bit on that.

C

um Yeah I guess I've been having trouble answering that question. People have been kind of throwing backdrop under the bus. Oh and acting like certain things aren't even being addressed and I noticed that that was one of them. um So I guess I was wondering like down the line like next year or whenever. um If it was like something that was in the plants, I got to have some of like the similar features to I. Have um like the content, be like Sen Tian.

C

I guess like it seems like there's some really cool features, um they're doing absolute.

A

Dealers are just Apple of things. um We do already have cmi in backdrop, so that isn't something that people injured white can say they don't have. We do it differently. They use EML files, news Jason files. We store our and read them off the file shortly. They store there's the database in and cashed it, which is a little different, but we have hardly selfish that problem in fact, trap. We do also not unrelated to see am I better. There are a lot of things in Drupal 8 that have been happening that have not been happening.

A

In fact, I have just because of the scope of our project. We do have a medic um that is about all of the modules that are included in through late and an explanation of either when they're going into faction of why we're not interested including them back up or if they're already in backdrop, which I think is what something like a comparison of you know, drupal 8 modules that went in for and I think that we should continue. I mean long-term.

A

Our goals are to be feature comparable, literally and so I think we should continue to revise like we'll get that list, revise it. Any module that goes into triple a poor we should look at you know, is the functionality of this module module, something that is going to apply to our target audience. Eighty percent of our target audience, and so that that's something we're working on um Nate also thinks that maybe the sticky point around cmi is how durably handles translation.

A

Like our see my files, don't have um schema definitions that define which language they are, but we do have a plan for how to solve problem as well under cool there's, an issue in HS posted in the chat there, as well with how we think we're going to solve that problem in, in a backdrop, girls into a triple world.

A

So, even though, right now, the two projects are facing the same promoter, a light work on the same, you know, general to pre, happens and whatever problems existed in Drupal 7 we've inherited because you're going to Drupal 7, but we are kind of rethinking about the problems reach. One of those and say like is this a problem for the majority like if it is this a problem for eighty percent of websites and something like translation, though really important is not a majority problem and that's something that we need to solve.

A

Obviously, if we want people to translate their sites in in backdrop, but they have been able to do it in Drupal 7 and we can enable people to it in the same way and we can make significant improvements in that process that maybe aren't the same improvements that your plate has done, just because our priorities might be a little bit different, so reevaluating the problems trying to figure out, which ones are most important in solving the most important ones.

A

First, it's kind of a big piece of what we're doing a backdrop, which is why we started with DMI layouts and you know merging the number one control module of use in the court. Let's that's why we started there. Those are the biggest problems. We have a lot of problems, I mean that doesn't mean it's not a successful conjugations de.

B

A

Got a lot of HD: we've got a lot of ideas about how to soften. We will continue working to solve them. We just you know we didn't have for years version 2 pack job. So we added to some things without make the big enough difference are the biggest difference. First, so um yeah I mean if you find yourself in conversations where people are saying. Oh backdrop is nothing good because of X um the the biggest answer there. Is that wasn't a priority? You know we only had so much time.

A

We want to do the most important things first, but we also are incrementally making changes all right. We have new stuff going into 11 or I'll be used to flying to 12, and if that becomes a priority, we can fix it like this, isn't a Drupal 7 long-term support where it will never change. This is a new project where we can put in whatever we want whenever we want um within reason. Okay, that's what I would say sounds.

C

A

But yeah I mean especially because we're all active in Drupal community there are going to be a lot of naysayers and generally I, just say like from your heart, like top Duke. Will why you're interesting.

B

A

This project and fascinates you and not, everyone is going to get it they're going to be plenty of people who just disagree with it on principle and that's fine, you know back type, isn't for them. um So it's for us, that's fine! There's gonna be enough of us little it'll be ok, everyone can have their own.

A

All right, well, Nate, do you have anything you want to add no.

B

I, don't think so. I think you covered that pretty pretty adequately all.

A

Right well, let's go ahead and wrap this then, and I am excited to test- drive the new pad auto patch, and I also want to do a another once over on the theme stuff and see how close for to that and then I'll take a look at 737 and set up a new issue. Let's def irrelevant to backdrop.

A

So it's my plan for today, so you guys an IRC or reddit or somewhere um and then a triple prime next week, how many people just to carry it out of curiosity, how many people here are going to triple con.

A

B

It might be the only ones exit. Oh there, we go tambien.

A

B

Excellent john will see you, of course. Oh the LA local.

A

Ok, well um we'll try and save enough dragon stickers for everyone.

A

Alright have a great rest of your day, guys all.

B

Right, bye, guys see you on IRC.