Backdrop CMS Weekly, 26 Feb 2015

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Backdrop CMS weekly meeting 2/26

Description

Weekly status meeting for Backdrop CMS

A

Are on air so today is Thursday. Februari 26th and we are here talk about the status of backdrop, CMS issues that core is working on or not backed up or above backdrop, other related stuff, we're doing and beginning of every meeting. We have a little period of time when we can make announcements from the PMC, and this week we have a very exciting announcement to make neat yeah.

B

It is, it is super exciting we added our first additional core committer to the backdrop project, so we now have an additional committer will mom shillingford or better known as doc. Wilma has joined the list of core committers, so he's taken on well, he has already been responsible for documentation. Writing up the API documentation changelog from that sort of thing, and we wanted to empower him to be able to make API changes are not sorry not engage in just documentation, changes to the core project as well.

B

So now he is joining to our list of commanders country really exciting, to expand out a little bit.

A

So we've updated on the backdrops TMS primary website. We've updated our leadership page to show the new core committer. We are still looking for more core committers, so I know they're going to help people who expressed interest in various subsystems, and we have our eyes on a few more, um but our leadership diagram shows a lot of core committer. So we're trying to find you know that now we have a proud of project out. We will try to fill up the team with people who have already shown their commitment on a really good job already.

A

It seems like a no-brainer to just say: hey you're, on the team go ahead and make changes where you feel like it's necessary. If we feel like you've got generally, um you know understanding how things work over here in backdrop land, it's kind of a promotion to just say: okay, we're, including more people, so we're super excited. We've got diploma on board. We actually sent him one email a couple of weeks ago and didn't hear back and we got really nervous and we're like wait.

A

What happened didn't get the first, you guys, so we assigned a second one. You gladly greater were like yay, so we'll work out the details, I actually getting him added to the list of people have access to commit which is good and then he'll be able to start making documentation changes, and so, if you're interested in working on documentation, you'll be submitting poor request, he will be reviewing and merging as well as Nate will be. Reviewing and merging are above fixes short term and then, of course, we will have.

A

You know right now we're still working on the One X branch, which means bug, fixes and new features, and so there's less work to do urgently, but we do still want to try and build out that team. So that's what we're kind of working on now. We've got our own a few people, so yeah team is still growing, which I think is super exciting for us um all. Right, so other exciting things. Since last week we still have a happy healthy, contributi.

A

We've got 25 um back, shopkin tip authors, I'm, not sure these numbers were updated. Since last week's meeting, there's also a ton of people with applications in the queue, so if we can get them moved through them will have people work, which is good and we've got I. Think a total of 50 or 51 can trim projects thinks that people are working on and I know, there's a bunch more coming down the pipeline as well bit too so.

A

I think we're doing a pretty good job on only being out for just over a month and having a bunch of people working with and using backup, which is great, I would love to see. um Since there are people porting module, a crazy. I would love to see the sights they're working on that require these modules.

A

So if anyone is working on sites and they get them watched, let us know we're super excited to see what those look like I just noticed, one of them on Twitter today, which is super exciting and then, of course, there's the ones that we're working on that we know about like backdrop CMS our um we good to have a list of other ones too, all right. So, let's start with talking about the things that were working on that are not backdrop.

A

The product there's been a bunch of really exciting progress on brush in the past week, uh Mike came and wanted to get it working on the latest version of cala box, and so he spent a couple of days, hacking on Josh and backdrop and totally got it working together.

A

He figured out the parts of Josh that needed to be changed and we've got some issues in the dress, cure, he's talking about things like drugs, checking for the valid Drupal version and obviously not finding that when it's back job and figured out what needs to be refactored so that drush can have an easy kind of drop-in backdrop, configuration which is fabulous and he's got a version of it working on cala boxes, kind of hacked together, and he even wrote a blog post about how we did that.

A

So, if anyone else wants to get it patched together and working, you can do that today, which is fabulous, and we also have a path forward for fixing those things that we're currently hacks. They need to be fixed in a more stable wait long term. So I think that is huge in terms of progress for backdrop and I. Think Luke give a talk on Monday at Berkeley and was talking about how we were working on it, but it didn't work it that only came together like really late Sunday night. There's.

C

A

C

Not about that.

A

But I just thought it was perfect that was like breaking news. Mike's got it working, so that was fabulous and he spent all weekend working on that and he's going to be in San. Diego I tend kept this weekend, so we'll talk to him or not. That in person get to thank him greatly for all of his work there um today, I would like to try and I know he's specifically been working on backdrop in cala box. Today, I'm going to try and duplicate his work in vamp and see if we can get that st.

A

those impacts that he did for Josh working in it in am Anthony Herman too, because he said he hadn't done any testing up other than Kalibak, so um yep backdrop should be working on catwalks, which will be great and then hopefully we can get it working on a man with the chirashi as well. So I'm super excited about all of those things, so progress on Josh. The next thing on our list here is update server. This is currently blocked by the port of backdrop. Cms to backdrop.

A

That's currently running a Drupal 7 and we're working on a new version of it. There is a new version of the site up at new backdrop, CMS org, where we have it fully ported to backdrop. We were waiting on two things before we could launch. One of them was redirect module and one of them was google analytics and I know. Last night um Nate you did a bunch of work on getting redirecting Google, Analytics, running and I. Think we are close enough.

A

um So I know we got a port of redirect last week and haven't tried it yet so sorry for the delay on that, um but we've got we've got everything going now and I think we should be ready to launch that site in a day or two. um We've got a couple of other modules like honey pot, that we need something on that form on the home page where people submit their logo, it's just to prevent us from getting a bunch of Sam right now.

A

It's currently moderated anyway, so I think we could launch the site without it it's just long term. We need something on there before the robots find us. So getting honey pot party would be good and now there's two people like you mentioned working on it. Someone else had mentioned working on it a couple of weeks ago, which is why Nate and I hadn't started courting and I suppose just check on it and see. If there's an issue in the issue queue or someone mentioned, it should be tagged with backdrop port.

A

So you can look for that um or if you don't see one go ahead and create an issue and ask because it could be that whoever is working on the port. You know didn't ask the issue ahead of time and didn't ask in the in the triple Q, but but I think there is someone working on our way. So we get to not duplicate that effort, if possible, but yeah so I think we're close enough to launch that site.

A

Any Dana will need to run the upgrade path, one more time, because I notice that we've got some documentation, changes on the life science, some new supporters- that we don't want to lose it in the process, but that should be going up in a day or two which is good um and then the update, checking which is currently blocked by that we have a plan. For that too. On the new backdrop website, Nate has been working on a module that will integrate with github I.

A

Don't think we have any particular updates on this since last week since I think it's ready, um but we just need to get that side for a trip, so we can actually use it. Do you want to give a low update on that yeah.

B

The packager is totally ready to go. I'm. Sorry, gentlemen may view the package is totally rated go. It works really well actually, but its dependence upon the the new site getting lost on back job because it's actually a module.

B

So the backdrop main site will be the responder to a web hook from github I think it will send us a ping every time a new release is made and then the packager will run adding in the backed up version information into the info files and then free zipping it back up and then pushing it up as an asset to github. The reason why the main site is going to be doing the packaging is because at the same time, it's also going to need to update or create a release.

B

Note on backdrop CMS org, so it will make backup CMS organ to kind of the canonical central repository very similar to to drupal.org. So the baxter.

C

B

It's just waiting on the site to be launched and then and then we'll start having package releases that actually have the version, information tags and cited them and then from there we'll start working on building up to the project repository. So things are coming along really nicely just one thing at a time.

A

That's great so that will be all projects that are currently in the kinship group will be able to package and put up right away. Okay. So then the only thing that would be left is, if you have a project that is not and the contribute and you want it listed on the API site. We also are sorry on the main factor of CM esta orange site.

A

We also need to open up the node creation process to authenticated users so that you can create a node and then I know we wanted to put single sign-on with github in there as well, so that you could use your github account as your backdrop account too. So maybe we should create and I'm not even sure, there's an issue for this yet, but to create that single sign-on backdrop module.

A

That would let you do that between one and the other, and then, if we had someone who wanted to start on that, um we could do that too. Yeah.

B

A

Great, so that sounds really good. um I mean if we can get the site up soon, then we can get our you know got our packaging script up, which would be responsible for creating nodes unpacked website, which means we can build a module theme layout search tool. That is not github, which is really exciting to me. So that's fabulous. um We also have kind of a long term plan to create an official github service for backdrop.

A

This would allow anyone who creates a module theme or layout on github to check a box, and that would be the equivalent of listing it as a sandbox project on CMS, org I, think that is far less urgent than getting our official projects listed on backdrop, CMS network, so it's kind of lower priority and it requires some expertise that none of us in this room necessarily have.

A

But if anyone wants to play a little bit with github, there's a really great tutorial there with good and bad examples of what services should be like, and we can get that at it at any time in the future.

A

So other things we're working on we've got our API website, I think it works fabulously right now. It's um lists all of our code, so I often use it when I'm trying to tell the differences between backdrop and drupal, you can just type in function names and if the functions of function has been removed, it'll automatically pull up the change record because it runs a search as well as just a autocomplete on function, name, Whitney, implemented and works so well and there's also, I think, almost a complete set of change records on there.

A

We've only are missing too I think there's two or maybe three that we have either noticed since backdrop. One was released or made changes since backdrop, one that need to be added. Everything else should be there. If you guys are using API setting. You notice a change record that needs an update, go ahead and create an issue against the API site and we can fix it. I haven't really been reading them over looking at them or anything. I haven't heard anything about them, so I'm assuming they're, all good, which is great.

A

But if not, we can fix that too. So, just as anyone is using, it keep an eye out for things that might need an update, and then the only thing I think is left for the API site is to get the theme from the new backdrop site potentially ported to it, and what we've obviously been waiting on getting the new batch of site done. First, we have Darius doing a design review of that.

A

I think obviously, today he's doing a training on backdrop which is exciting too, but at some point he'll do a design review of the new theme and make sure we haven't missed anything I think there's some form styles and stuff that are currently missing, but was initially get that theme done, we'll, try and drop that on API site and make sure that it works as well as the current theme, if not better, and then that should be done after that.

A

So speaking of our primary website, we've already talked a little bit about. We've got the package script going, we've got it ported to back up. We've got all of the modules, leaning almost ready, which is great.

A

um There's new features we'd like to add to obviously getting modules and themes pages up there and layouts is going to be important and then building an interface for actually searching and finding what you need is also going to be super important, so we're going to start doing a design process for that as soon as we get sign off on the current theme working the way it's supposed to, and then we'll get those modules and themes pages up, so that people can search for things that they need for backdrop on that site um and then, as soon as we get that done, we're going to move on to building a showcase.

A

So anyone hopefully we'll be wrapping up their new backdrop sites about the same time we get done with the module search wants to enter those it'll, be the same processes, creating a note for a project you log in a site. You can create a note and you can post information about the site that you built. It's going to be modeled very much off of the drupal showcase on drupal at work.

A

So same kind of thing, where people are going to want to see working examples with backdrop sites and the more we can put up there, the better, obviously the better, the better, also so make your backdrop sites make them awesome and we'll throw them up there too. Also, with link links back to your site to help you know a little SEO think you love there too, all right. So that's what we have on the table for things that are not backdrop, the product itself we're going to talk a little bit about.

A

What's left to do for backdrop in backdrop, one as well. um Obviously, as we are working on backdrop, we will discover bubs and we will fix those as needed. There are obviously a lot of bugs and backdrop just like there are a lot of bugs in Drupal today and, as we discover them and fix them will merge those into the current version. If we find one that we think is dangerous enough or a big enough improvement that we want to issue a bug-fix release will do that.

A

I, don't know that we have any right any fixes right now. I think the biggest thing is getting our themes, configuration importable so right now, if you have Tina, has configuration and you try and move your config files in none of your site will import at all, which is a pretty serious bug so soon as we get that fixed, we'll, probably want to issue a bug-fix release, so I know we have an issue.

A

I think what did you create an issue in the queue if you didn't create when I might have created one um yeah, so there's an issue in a queue for that. We just need to get a working, full request on that and then we'll probably do a bug-fix release and when that release comes out all the other one fixes that we fix along the way we'll go with it.

A

So I think that's what's next coming up for for bug, fixes and then and there's a bunch of new features working on adding as well, and those features currently include trying to get a rich text editor in core, which is not a small feat. We talked a little bit last week in detail about the actual process for getting from where we are now to getting that rich text.

A

Editor course I'm not going to go over in too much detail, but it is not involved, porting, the WYSIWYG module or the ck, my module or anything any of the solutions that we have currently in Drupal 7 to backdrop.

A

So it's going to require kind of a lot more focus and a lot more thought about the architecture of the system and needs done this once already for Drupal 8 we're going to kind of be modeling a little bit of the way that it was done and Drupal 8, uh but rather than having them, be completely separate modules for something like editor and filter.

A

We're going to merge those together because we want less swap ability in backdrop, that's more about getting a really seamless integration so doing as much as we can directly to core to get that end. I think would be the right way to go for us. So I'm not sure if there's an issue yet with all of the implementation details. But if anyone wanted to work on that, we should maybe start talking about technical implementation. Details on that too. That's our biggest thing.

A

We are likely to not get done in time for 11 dot one, um but it is also one of the most important things. Obviously, in your hundred, our hearts Nate did a bunch of work on that in interpolate in yeah with editing something everyone loves. So that's on our to-do list. Another thing that we want to do is take the token module and put that in core and we have a working token module for backdrop. This was the token module from Drupal 7 that was ported. It's got a fancy.

A

New I knew you I integrates with the dialogue system. It's going to be a huge step forward in terms of you know a whole bunch of other stuff that depends on token module, the more we can get in Corinth butter, but we need to figure out not how to take the control and just put it in court the same way it is now, but how to more tightly integrate that with core itself.

A

So, for example, all of the tokens that are provided by token module need to be distributed to their modules that they should have originally come from, and the user interface itself should probably be moved into system so, rather than having a separate module to turn on it, just becomes more of cork or just provides that that functionality, so that again, is going to require a little bit of architecting, or at least a little bit of thought, kind of on architecture and architects suppose as to where to put all of those pieces and and then similarly we're going to try input in path, auto module, which we also have a complete working port.

A

In Drupal, we took the drupal 7 version and reported that two backdrop. So we have a complete working part of that exact module in order to put that in core, it's going to be the same kind of thing where, instead of being a separate module that you turn on or off, it should integrate directly with path module and so we'll need to figure out where user interface for that should be. It should be on a settings. Tab integrated with path: where did the configurations for those go?

A

I recommend, like vertical tabs on the entity, bundle form, but there's just some kind of thought about how this stuff in path auto needs to be distributed into path. So you have two working core, so I think d architecting involved in that. So if we wanted to have someone work on either of those probably some technical, technical implementation, implementation details in the issue we have already would be a good starting point.

A

So um and those things are very likely to get completed by 11, which is May, which is now the end of February's got two months left and then getting those modules, ported and ready and working for backdrop was a great first step. Next step is smooshing them, and so, if anyone wants to work on those, those are slightly easier than trying to get that rich text editor in and then the last thing that's on my hit list for 1.1 is changing.

A

The administration look and feel for backdrops that, when you're using backed up, it doesn't feel like using Drupal 7 um and we've got a great new style guide that Darius and Ronnie and wax have all been working on, and now we have a whole bunch of other issues about how to implement the changes from the scout style guide. For backdrop, which is great um and I know on my plate, is to get the style guide module for backdrop finished it's working right now.

A

If you guys want to install it just there's a style guide for comments that is not working and I. Think everything else works. Just fine I'll try and get the comments wrapped up right now, but the style guide that we're using as our guide doesn't actually have things like comments on it anyway. So if you wanted to proceed with what everything we already have styled is ready for that you can throw it on a backdrop, site and you'll get the same style guide out and you can start styling the elements.

A

um So it should be good enough for that. We just I want to make it work the way the Drupal 7 job ID module worked, which means it will show you what comments look like and what the comment form looks like you can style those all on the same place too. um So it needs a little bit work, a little bit of work for backdrop contribu, and but it is ready for what we need to do in Port.

A

If anyone wants to start working on those issues, so I think that's a great um a great starting point. I also noticed. There's a we got a ton of really good feedback on our style guy that hasn't been addressed.

A

It has a majestic as Darius is running a training today on backdrop, so he's obviously busy and has been for the last week, um but I think that a lot of the suggestions are really good ones and what I was planning on doing today after this meeting is taking the suggestions that were made in the issue: queue especially tackle technical implementation suggestions and moving them to the issues about technical implementation, so that the issue queue for the style guide, just becomes recommendations on style changes, not technical recommendations on how do we implement our bug fixes and then that way, when Darius is done with this training is nap.

A

Oh, you can go back and look at that and say: oh yeah, we forgot to tell the quote, or we should make the black vote wide or whatever the design thinks he needs to focus on actually are, and that I think is really great. We've got some things that don't have any feedback that can implement it right away, like everybody loves the pager right. So somebody wanted to start working on those today, like pager, is ready to be styled and implemented. Backdrop and I think the the more we can get.

A

You know this one's ready versus this one is and I think we'll just kind of start, knocking about so I think there's been a whole bunch of great progress on that already and I'm super excited to see those changes moving into power um all right so that those are our major hit list items for 1.1, there's, obviously a ton of other stuff that we're working on all time. Things like developer experience are super important to us here in Bactra plant because backdrop, more than anything else, is a tool for building web sites.

A

So that means that it needs to be easy to click together and I needs to be easy to implement so developer experience. How does it feel support those modules? How does it feel to build sites with backdrop? How does it feel to write your own theme if you find things that are weird, create issues for us titanum with DX and we'll look at how to solve them and developer experience?

A

Improvements can't always be done in 12 x, because sometimes it will require an api change, but if we can introduce a wrapper function that will help with backwards compatibility or a wrapper function that will help with your module load include weird argument order. However,.

C

A

We can add those things we just can't change the way anything that's currently in there works like order of arguments or anything like that. um But having issues documented means that we can either recognize it's an issue, any fix it now or postpone it to Thaksin fix it in the future. But we do want to know what the shoes are, so we can solve them and the same thing goes for user experience.

A

Drupal has had a long history of being not the easiest tool to use and part of those just because it's super flexible and can do everything and we're not just be able to solve all those problems, the backup, because it's also really flexible and can do lots of stuff. But there are some things that we can seriously improve in the user experience area, particularly learning and round terminology, so using edit, when you mean edit and you see configure when you can configure thanks, Visser's are easy for us to clean up their novice.

A

Tat casts in terms of making the actual changes to the code. Just someone has to kind of notice that it wasn't doing it right. It correctly and pointed out, and then someone else needs to change it, and then we need to merge it in and so there's a whole bunch of issues in our queue already tagged with DX that'll help us find developer, experience, issues and new x-ray user experience, issues and I think um anyone who is looking for some low-hanging fruit / backdrop can search the queue and find the posts.

A

We did have a question why some of our issues use labels to identify things and some of our shoes use square types. So in the github q we don't have the ability to add different vocabularies. The way that you do interval where you can have something for you know, what's the status of this issue versus what type of thing is it versus? What's data, you know what um what a system is it a fact or anything like that and so in github?

A

All we have is one group of labels and we've tried to organize those labels by prefixing them with something like audience or status, or you know, pull request status, but there isn't really room in the list of labels for every tag that we're going to want to add on to an issue queue so for things that are actually tagged like thinks that anyone just wants to add on an issue.

A

We've been using square brackets, so square market, you x square bracket, DX those are tags, so they go in the issue, title in square brackets and things that are actually a status or a categorization of that issue are in the labels. So that is a little bit confusing, but that's how we have to work with the tool that we are using. So that's kind of how things work in the issue, um but yeah there's plenty of issues, easy ones, hard ones, anything anyone wants to work on all of programs and every Thursday.

A

After this meeting we usually hang out in IRC in the pound, backed up channel and try and crank through a bunch of those issues together. So neat and I'll be here today, organizing issues and working on the backdrop site, as well as the backdrop product itself, and if anyone else wants to grab something we're usually around to offer help on Thursdays as well.

A

If it's not a Thursday and you want to work on backup, we are also usually an IRC channel, though maybe not working on our selves and we're always around to answer questions so and even if Nate and I aren't there's usually other people in the eye or teaching tool. Also answer questions.

A

So if you want to jump in and ask a question: there's usually people friendly people around two to help ports and then grumpy people depending on, if it's three in the morning or not but yeah, so the backdrop community hangs out online in IRC channel found backdrop, and we also have a reddit. If you, if I RC, isn't your thing do nerdy for you and you just want to ask questions. We have a subreddit at what is it reddit.com, /, r, / backdrop or something, and that read it seems to be completely working.

A

There's a whole bunch of noise in there people or an seng question asking questions, answering questions um so uh I guess read it read, it is still fairly nerdy. We are nerdy people. We also have a Facebook group if you're not into Reddit and there's a linkedin group and there's a whole bunch of other stuff where you can find us online, but it seems to be the most most of our dirtiest. People are hanging out either and I are so you're on reddit.

A

So that's that's where, where you can find to the backdrop community um but yeah, uh we are going to be doing a in person sprint at mid camp in Chicago next month on the Sunday following the camp, which is kind of exciting. There is a Google spreadsheet where people can sign up. uh If you want to come to front on backdrop neat- and I will be there- we've got our names in there. I think Doug.

A

If you're going to do that, you can put your name that Andy I don't know if you're coming to mid camp bacon, though your name in the spreadsheet ooh we're gonna, be spending alongside the Drupal 8. Folks, so I think it'll be kind of good to have us all, be able to collaborate and talk in the same room and get along and show that we all love each other, so that'll be good and then this weekend, obviously sand camp is happening right now.

A

Darius is doing a training right now for people on the new layout system, which is super exciting and me now be doing a talk there tomorrow about backdrop, and hopefully it will be well-received, Pelosi backdrop friendly events. We also have a calendar in a Google that you can subscribe to that will list backdrop friendly drug events, and so if anyone is attending event, we don't know about. It is backdrop friendly. Let us know we'll add it to a calendar too. So that's not just for us.

A

That's for anyone who wants to go anywhere and talk about backdrop and um II bumped by your fellow nerds. We can just show that on the calendar, um so, let's see other things to talk about. There is a drupal watchdog, article coming out in May, which should coincide roughly around drupal con la that Nate and I have both written articles, for there might be some other doctor friendly articles in there, which is super exciting.

A

Today there was another um blog released about co, maintaining Drupal, 7 and backdrop modules at the same time, which I think is something it's going to be super relevant for a lot of people for a number of years to come, which is really good if anyone has anything else that they've seen on the internet that super exciting.

A

Let us know about it, we're always interested to see what other people are saying about back job, not necessarily us um in yeah I think that's all um I have for today's meeting, but we should open it up a little bit to see. If any of you have any questions or comments or things you want to talk about or think we should talk about every week, I.

C

Had one I was a I can hear myself it's a little weird, uh the ticket log for the style guide, actually implementing it. I there's not really a way to mark things that are blocked. So I was one thinking. Maybe a label that status block. Does that sound, appropriate open? Now, I can't hear anything.

B

I'm sorry I media Jen cuz. She was the UH just echo we won so I can't unmute. You, though gents oh.

A

Okay, can you hear me now yeah.

B

A

I was just saying that um maybe we should just go ahead and add that issue unless you or that tag to the take you unless you had a strong feeling against it. The label first at is blocked. I.

B

Think there is postponed I guess it's not quite the same thing.

C

Yeah I just wanted to wait easy way for people to see. Oh, the pager is good to go. There's no, there's no issues in that other. You know style guide ticket that are blocking it, so we can just go ahead and do that and I can be responsible for making sure you know when things get blocked or cleared or whatever on that does that work yeah.

B

I, wonder: do you think I guess we could market blocked I'm trying to figure out if, like we already have needs feedback, for example? And we already have postponed and I would think maybe a combination needs feedback and postponed would be kind of the equivalence of blocked on.

A

Means like we're not gonna, do this yet I mean I, guess that's kind of this in yeah.

C

And we kind of have feedback, but it's precarious.

A

C

That's why I yeah.

A

I, don't know that we want to invite more feedback on something this watch. Okay,.

B

um What do you think Jen I mean.

A

So so, what's the hesitation here is that the github UI is really horrible. When you have a lot of labels, and so.

C

A

To figure out like how to manage this creeping label problem, and so we looked at all the labels around to lower. Can we tried to remove the ones that we thought that we didn't actually need um and I actually went and removed?

A

A bunch for Nate was like I need those I use those all the time so that I had for the back so fortunate, not to add too many more I think we can use postponed as long as we knew that that's what we were using it for um cuz postponed kind of means, like oh we're not going to do this until 2x. So we're not going to do this until something else doesn't renessa mean at least the way we're using it.

A

Now we're gonna unposted as soon as this other issue is resolved, but we could use it for that. In this case, as long as we were, you know, I mean we could make that our policy of like when something's blocked market postponed and then put the you know some comment, and then it says this is block based on whatever one postponed it when it's daniel, and I think it's been as long as you. um You know as long as we're managing that, so that all these issues don't end up postponed and never unknow smoked right.

C

Yeah I'll definitely keep an eye on it. Okay,.

A

So let's try that first and see if that works um and if it does and we don't need to worry about adding a blocked tag and if it starts to become um you know, I'm clearest what's going on, we can. We can try and change it.

A

Okay, um any other questions or comments or anything. We should talk about today.

A

No, thank you all so much for joining.

B

Yeah thanks so much guys. This is quite the crowd.

A

Alright, well we're going to go ahead and jump off then, and we will move the chatter to IRC pound backdrop. If you have anything to share with back job, you can always tweet at backdrop CMS or um yeah. We have a contact form on the website. If you have any specific questions, the best thing that would be to find community on the reddit, an IRC channel or on Twitter.

A

We also using the hash tag pound backdrop: CMS do I know some people have using pound backdrop, but there's a lot of like photo Instagram stuff that uses found backdrop and so we're trying to keep it down backdrop CMS. So if you are tweeting, go ahead and add the CMS and it'll be a little less confusing for everyone. um So yeah we'll see you guys on the internet or next week same bat-channel.

B

Alright, thanks for joining everybody, bye.