Backdrop CMS Weekly meetings, 19 Feb 2015

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Backdrop weekly check-in meeting 2/19

Description

Backdrop CMS has many things that need to be done. This meeting outlines priorities, and gives a general progress update.

A

Alright, we are on air, it is Thursday. Februari 19th I'm, also supposed to ask anyone who joins the meeting to mute your selves. If you have any potentially noisy background noises or computer robot noises or anything like that, but looks like you already are so good job everyone Deb reading the agenda. We are doing a check-in meeting for vector of CMS to talk about all the stuff that we're working on. Hopefully, in order of priority at the banning of this meeting, we have a section usually reserved for updates from the project management committee.

A

We don't have any updates for you this week. It's been business as usual for the last few weeks here so we'll just carry on, and I clicked update on community growth nate. Do you want to take this over since you're responsible for our new contributors.

B

Sure so things are still kind of just rolling along lots of new controls coming in a 25 total contributed. Authors are now, in the backdrop, contribute and 50. Total projects have been ported or written for backdrop, and there are a handful more in the pipeline, such as Andy, for example, sinner hang out again, but is still uh still queued up in the review process for for getting added to the contribute.

B

If you're interested in joining the backdrop contribute you can visit it at github com, / backdrop dash, can't rib and in the readme there there's a information about how to actually I guess it's not really and the readme in the description there you can. You can get information about how to join the group. Basically, we do a really minor review, checking to make sure that you maintain history for Drupal 7, that you include a license file and that you include a readme file.

B

Basically, is all the requirements that we have and then you can get access and you can add or port or do whatever you want into the backdrop contribute.

B

Let's say we also have some peripherals around integrating with the contribute, but I'll talk about that later in the peripheral section soon.

A

So we also have a couple of updates on things that aren't backed up itself that we're working on and the first and foremost is josh. I love dress how you stretch every day for all my triple six, and I don't know that I'd be super happy with backdrop not having something like Josh and I. Did. We've got one. um We I suppose have one live site running on Pantheon right now in most of pina pantheons dashboard integration uses Josh.

A

So things like automated backups clearing, the cache is from the Pantheon dash, but all that stuff doesn't work and won't work until we get dressed support, so I open a bunch of tickets on Pantheon saying like backdrop, sites are having these problems and it's fine, like my life site, still gets you know, I can run update on PHP and I can make my own backups, but I wanted to all work like pantheon.

A

Usually works so I've been a bunch of tickets with the dashboard saying like well, you know what is the process for getting this done and they basically assign all my tickets to Matt, who was in Colombia last week for triple con Columbia, but he still wrote me back and said: hey I just got all these tickets design for you. Here's my plan for how we're going to deal with backdrop sites I'm going to set up a special um sandbox where we can run whatever version of dress really want, and anyone who sets up backdrop site.

A

We can drop in the sandbox. So as long as you can work on getting some version of rush ready, you being you know the community at large and we can put whatever you want there and make the backdrop sites work on Pantheon, which made me super happy. So then I checked in the Josh issue. Queue and Greg Anderson has been doing a bunch of work on kind of abstracting, the Drupal out of josh, and so he's got a bunch of pull request against Josh that'll make it easier to use.

A

And then we have a couple of people are also interested in making Josh work with backdrops. That can use backdrop as a test case for the new abstraction of Josh.

A

So it looks like there's been a lot of progress happening in drush, which is great and there's a lot of like support from Pantheon on how we can actually get the new version of josh working with backdrop when it's ready, so I think that all sounds super exciting and we also have like a short-term way to use a backdrop, specific version of Josh, where, if you have a version of dress that you have hacked to work with backup, you can drop it directly into your project route and rush will automatically look for that version of Josh um instead of using the one that's installed like per user on your system.

A

So I think that short term. We can do that long term, we'll just get the version of josh to recognize like an include file that will ship with backdrop that will tell it where it is. So I think we about the shop on the short term solution for using dress on your back drop sites like this month, which will be great you guys next month, then we have a longer term like the next official version of josh, maybe not josh seven, but some soon version of josh will contain factual support.

A

So I'm super excited about all the progress. That's happening there with josh and backdrop, um and then knee has been doing a bunch of work on updates and packaging. Do you want to talk a little bit about update server and um github integration and all that good stuff, yeah.

B

So this is tied into the the major site or the main site itself. Backdrop: CMS org is almost fully ported to backdrop itself, so our own site will be running our own software, which is always nice. You can see the new site at. Unfortunately, it has to be https, https colon, slash, slash new backdrop, CMS org. It basically is exactly like the old site, only it's on backdrop.

B

So the progress there is that we have some additional modules on there, that you can't really see it, but one of them is a integration with github and the very first thing that we've got going is we've made made a packager script so that, when you make a new release, in the backdrop contribute once we launch the new site will happen, is a web hook will be fired to the main site from github and then the backdrop CMS torgue website will then check out the zip file from the release. Unzip.

B

It read through all the dot info files. Add in all the version. Information like the drupal.org, packager script us and then compress it again and then upload it to the release on github, so get up we'll continue to host our packaged releases. But now what will happen is we'll check out the zip, modify it and then upload up a new one, and then that will be the copy that will start linking to from backdrop CMS org.

B

So basically we have a packager now, which is which is great, and so as soon as the new site lunches will wire that up and get the package you're running on all contribute the update status operations later so first things: first, the version information into packages and then we'll continue working on making update status. Work right after that. So that's that, oh.

B

You're, muted gen still.

A

Even Google was like you should unmute yourself if you want to talk alright guys so yeah I'm super excited about all the progress we've been making on the background primary website. I think we are probably days away from launching that we just need to get a little design review and make sure we get some spam protection on that um submit your logo form we've got on there and then I think it'll be good to go. So that's super exciting we've got a I github integration.

A

Did you want to talk at all about this service Nate, or do we want to skip that? You.

B

Mean a github service, yeah.

A

B

No there's not really any any progress on that I mean getting the backdrop. Control group set up and working with web hooks is kind of the first step and will maintain the most control over the web.

B

Hooks in that group, so I think it's a good opportunity for us to test it make sure that it's all working while we can still can't kind of change it and then then we'll work on the service after that, because the service is, is the concept that any github project anywhere like not just within the backdrop contribute can register projects on bike shop, CMS org as well, and that is in the plan, but it's less priority. Then then getting the back opportunity of group I figured out. Okay.

A

So that's lower priority mediation, move it down lower on the list, but we'll see about that next week. Okay, so other things we have going on, our API site is still ticking along. It's working really well as an API site. It added some great improvements, I think two weeks ago to the way the search works so that it'll autocomplete function, names or search content.

A

So if you type in, for example, like a functioning that you would have used in Drupal 7- and it's not in backdrop, it'll find the change record that references that functioning then it'll tell you exactly what you should change the function to which I think is super helpful. um The theme is currently running a fancied up version of Bartok we're working on a new theme. It's going to take some version of the theme, that's on our primary website that is lower priority.

A

It's working really well the way it is now so we're gonna leave it until we get off the mortgage and stuff done, like our primary website get up integration, a modules listing stuff like that all comes first but I've been super happy with all documentation. On the API site have been super happy with the way that I change notices are working I think we have like to change notices that are left to be created, all of them fig user review.

A

If anyone finds any problems with any of the documentation or anything on there, we could definitely use help. Reviewing and updating them so go ahead and create issues in the github issue, queue associated with the API site and we will take care of them if you can't find that just put them in any Q and we'll try and direct you where that should be, but yeah I think with API side is working really well um for a primary website. We have the new version that he talked about.

A

What we're working on next over there is the ability for people to post a note about a project, so a module theme or layout, and then we're going to try and give them a way to search those things, and also um you know ways you can add links to support queues, documentation and the actual source code. So we will be able to pull in anything.

A

That's part of the backdrop kinship group, but anything that is not part of the get contribute can also be added by creating a note and filling out those fields to yourself so we'll try and get that up soon too, so that people can post the code wherever they look like. um We also have um forum going in a subreddit which I must admit. I was a little skeptical at the beginning, but it is totally working everyone's hanging on the forum asking questions topic.

A

A new people are popping in I think it's going really well over there. So I've been really happy with how it goes. um The only thing I had issues with a couple waste guys I wanted to post an image and instead I had to post like a link to an image out of just clean image directly in the comment. I, don't know if there's a solution for that on reddit. If anyone has one I would love to hear about it.

A

Otherwise, I think everything over there playing swimmingly and I would love to continue using that as our forum software. So we don't have to build our own um okay, so upcoming releases for backdrop. We have a couple of bug fixes that are in. We have a couple more well handful, more bugs in the issue, queue that could use to be fixed, but I don't think we have anything that is a super urgent priority for releasing so we'll just keep cranking through a little changes like that until we have one.

A

Obviously, if a security release comes out either for Drupal or for backdrop, we will evaluate those and release as needed. Otherwise we're just going to keep looking at the bug, fixes that come up and say how important their and how soon those releases need to come out for backdrop.

A

We have a minor release coming up on May fifteenth that will be back up 1.1 and more releases after that. So for the 1.1 release, we have four things that are kind of important. Our rich text, editor, which I think is probably the most important but also the hardest to do, is something the backdrop is really lacking right. Now. The plan for putting a rich text editor into that Chef Cora's, going to look a lot like the plan that put a restriction editor into Drupal 8 corp.

A

So we're going to use ckeditor we're going to add a module that you will be able to turn on or off. That'll give you the editor, not the editor, but all of the integration instead of having a module called editor like triple eight did between the filter system, which is the filtering on the back end, and the WYSIWYG system, which is the filtering on the front end we'll all be integrated directly into filter module. So we'll have a filter, module changes and will ckeditor module. That will let you turn.

C

A

On and off, and so if we have anyone who wants to work on that, um we do have a example of how that works in Drupal 7 with the WYSIWYG ckeditor module, we're not going to be porting WYSIWYG to backdrop. Instead, all of integration is going to happen directly with filter module. So if we haven't who wants to work on rich text editor in core, the first step is not starting with WYSIWYG. The first step is kind of starting with what your boy did.

A

I, don't know how helpful it's going to be to look at their code to figure out what that was. It might be more helpful to look at like install Drupal 8 and see what it does like functionally and say. Oh, you know, the edit form is changed in this way and then make those same changes to backdrop that way, and we have some code that was written for triple seven and the WYSIWYG ckeditor module.

A

That might be a good starting point for that, um but this is the kind of change that requires some significant, like architecture, thinking it's not as simple as porting something. So it's going to require a significant amount of focus and someone who's like dedicated to cranking it out. So it's a hard thing to do in your spare time, but it is really important and we do want to get it done and if it doesn't get done by 1.1, we need to get it in by 1.2. So that's our plan for rich text editor.

A

We have other things that are going to be going into court in 1.1 like token module and path, auto module and those two things do start by pouring token and path auto to backdrop, and so we currently have a version jokin, an emergent auto that are now working and happy for backdrop CMS and they are, in the backdrop, control for positive, and so the next step towards getting those in court would be looking at the way interfaces work and deciding of those interfaces belong where they are in the control or if they should be more tightly integrated with core.

A

So, for example, haha no module should probably not be a separate module core. It should probably be part path and so trying to figure out where the settings form should live and that sort of stuff is, is the path forward for that and then figuring out how to integrate that into our existing path. Module would be how to get that in and then token we already have token support and poor. We just need to figure out where the.

A

Why is going to live like is that need to be a separate module called token you I, or can we just move all the tokens and where they go and then put token module somewhere else? So we need someone to kind of think kind of bigger picture about how these things should be integrated. Now that they're working and that's the the progress towards getting those two things apart.

A

um Another thing we want to get done for the 1.1 release is getting the administration for backdrop to feel different from the administration for trouble right now you install it. You get the 7 theme, it looks the same and feels the same in people aren't going to be able to tell the difference, am I writing a backed-up site or drupal site unless you go to the layout interface.

A

um So what we'd like to do is make it feel different. We have a great style guy that was working on that sets backdrops brand a little bit apart, and all we need to do is figure out how to implement and implement those changes. We haven't told me 15, which I think means we can get most of the way, if not all the way done in the next few months, so I think that's looking pretty good and then we'll start have a product that feels different from Drupal um there.

A

Of course, a ton of other issues in our issue, queue that are not necessarily slated for the 1.1 release as far as new features, I, don't think we're planning on adding any new features that aren't in this list. But if something gets done um early and we want to put it in I- think that's realistic, although if people are working on new features, I would love to see them work on these, because these are our priorities.

A

However, any other changes, user experience, improved improvements, developer experience improvements, um you know, tiny bug, fixes other terminology updates anything that we can get done between now and May. Fifteenth can go into that release. So if there's you know, you run into a bug and you want to fix it or you think an interface is confusing and you want to fix if there is ability to get those done to so as you're building websites with backtrack, as I'm sure you all are you're going to run into a bunch of little snags.

A

Obviously this new software, I would love to get as many of those snags moved out before 1.1 as possible. Obviously we have minimal number of people using it today, as time goes forward, we're going to get more and more people using it so trying to make that experience is positive for all of the new people in the future. I think is a good goal for us to so um issues in our q4 user. Experience are tagged with in the issue title square brackets in the letters you x developer.

A

Experience is the same as square brackets and DX the developer experience issues are a little trickier to fix because we aren't allowed to change any api's. Now that one point one is out. So if what we need to do is add a wrapper function for backwards compatibility, we can do that if we, what we need to do is change the order of arguments passed into a function.

A

We can't do that anymore, so it's good to identify issues that you feel like you're, creating a bad developer experience or could be improved, but not all of them are going to get into 1.1. Some of them might be typed as 1.2, but it's good to have them in the queue. So we know what the out what they are, and if you put in an issue that we think we can't change a 1.1 will do it.

A

If it's an issue, we can't will change the milestone, 2, 1.2, so you'll know this, isn't something we can change without an API break, and you know it could be that we tag it with 1.2 and someone makes a recommendation of how to do it without bringing you guys and we can move it back to 1.1, but it definitely let us know if you're working with backdrop and you feel like there's room for improvement, we want to know all the problems and all of the great things too, but you know to create shoots for those we usually have sprints.

A

Every Thursday is a backdrop day we meet in IRC. Our channel is found backdrop if you are an IRC, nerd and like to hang out online. We it's usually a bunch of group, a bunch of people in there, after its meaning, sometimes before as well. If you want to get someone's attention, go ahead and type their name and most people's IRC clients are configured to make a noise um ask them if their name is mentioned, sometimes I've been in there. People been like.

A

Is anyone in here we're all there we're just not necessary listening something like that? Someone's attention go ahead and mention us and that'll be guaranteed way to get someone to respond. We also have some upcoming events that are backdrop friendly in particular sand camp. The San Diego drupalcamp is going to be coming up in a week and a half here, and it is going to be, I think, thursday through saturday and on thursday we have our first backdrop, training, which is very exciting.

A

We're gonna be doing a half day. Training on basics of back job and I have actually talked to a couple. People that were like all I really wanted to come to see it cancel I could do the back jumping, but I'm not going to be able to do it and I had to sadly admit, like kind of the point of backdrop, is that you don't shouldn't really need a training.

A

Rick is supposed to be the same, but there are some significant differences, layouts and cmi among them, and so I think people who are interested might want to sit in that training. It's free! um It's it's a good kind of intro, bring you up to speed on stuff too, so I'm really excited about training and looking to hear what people think of it and then Nate and I'll also be doing a session at the camp.

A

So if you don't want to give up a half a day on Thursday, you will be at the camp like you're, about backed up we're, gonna talk, but on the weekend. um So definitely we're looking forward to being there um getting some more sunshine. It's Lenny here, not studying the rest of the world, but it'll definitely be sunny in San Diego, so it'll be a fun time and then in March we're going to mid camp in Chicago, which should be the opposite of sunny, not sure whether it's gonna be snowy or just cold.

A

But it is not going to be a beautiful San, Diego environment for sure, but it will be backed up friendly, so Nate now be there. You can come talk to us at the bar. You can talk to us at the sprint. We're trying to organize this sponsorship of this print. I think it's moving mostly a Drupal 8 sprint, but Nate now be there. So we'll be sprinting on backdrop on Sunday and so hopefully they'll decide that they want. Our money will be able to sponsor that. But we'll see we haven't heard back from them.

A

Yet on that, um and we have some calendars if you guys are interested in where we're going to be or if you are going to be attending an event and want to talk about backdrop- and you can add that to our calendar too and we have links to the google ical feeds both in our subreddit. If you want to grab them there or in the weekly meeting agenda for this meeting, so um those we've got two calendars.

A

One of them is virtual events, that are backdrop friendly, and one of them is for just these weekly meetings. So if you want to be notified of when these meetings are, we have this meeting every thursday at same time, and we have one meeting, it's a design, specific meeting that starts an hour earlier, but it's every other thursday, so you're interesting either those things that calendar is available for this. As well um all right, let's see other things.

A

That's the end of the agenda. The only thing I have on here is: there's a drupal watchdog.

A

That's going to be coming out to see I'm a triple con la that will have both an article that I've written that's kind of a very, very in-depth comparison of the differences between backdrop and triple seven, so talking mostly about cmi and layouts, and how your code should be different from one to the other, and then Nate has a kind of a more general faq on backdrop stuff like how do things work in backdrop, things we get asked a lot.

A

I think those are both going to be super helpful for people who haven't been following along with what we've been doing all the time and I'm looking forward to coming out.

A

That's all I have for today's meeting, there's a bunch of you here, so I want to see first of all, if there's anything, you guys think we could talk about every week or secondly, if there's anything you want to bring up this week that we should chat about today. I.

D

Have a question this may be somewhat up may be forward, but do we have plans for third-party libraries, yet drupal used the library's module and then some people said it's too big. It's too heavy. We should not do that um and this would be. You know both jQuery plugins PHP library code. um Anything that could romaji will might include a is there a think tank on that um we.

A

B

An issue where.

A

We have been thinking about that and there's been a lot of back and forth a name lest admit: I I come across this all the time and every time I revisit the issue I'm like Nate. What are we gonna do about libraries and he has some very strong feeling, so maybe you can update us on your thoughts on backdrops path forward of whether we should, according libraries module the backdrop and since we don't have anything for yet or whether we should be handling it differently. Yeah.

B

So so I tried to find the issue I'll post it in the chat or or in IRC after after the Hangout is done, but but we do still have an issue. That is a core issue that it's like. What should we do about? Organizing our libraries and I think the one thing that we know for sure? That's. A good idea is just organizing the misc directory into some kind of libraries directory in core. But that's really just reorganization like how we actually manage you know.

B

Multiple modules need to depend on the same library is still kind of a discussion. That's happening, yeah, thanks Jen for the link that's still happening for now, though, definitely the easiest thing to do is because we don't have any license restrictions on our code. Drupal.Org specifically said you can't bundle your libraries in your projects because well just because it's the the policy. Basically, they just didn't want external libraries in their projects, but on github we have no such restrictions and in the control group we don't even have that sort of policy.

B

So for now the easiest thing to do for certain is if your module depends on a library, especially a JavaScript library, and you are kind of like the canonical module. For that thing. Let's say you had like a flex lighter module and you wanted to bundle the flex slider library, then that would be the easiest thing to do. It's just included right in the repository so for now, probably just bundle long-term yeah. Well, we'll need to figure out what to do about libraries.

B

We may end up with some kind of port of libraries API, but I kind of, like the simplicity of not having all modules need to download another module for the time being so I don't know, I would say: let's discuss it in this uq. It's issue 159 and.

A

um There's also a user experience benefit there to where, if you are the flex, slider module, it's hard to say, ok down on this module and then go to this arbitrary length which changes every six months and download this package, and you don't know which version it is, and you don't know you know once you unpack it, you might have to rename it there's kind of like a big stumbling block there to installing third-party libraries, and if we can find a way to say you install a flex, slider library, everything you need is packed with it for the developers installing it it's a much better experience.

A

We are obviously going to run some problems for, if you install like flex, slider module one and flex later module two at the same time, and they both can contain the library you'll have a conflict, but the use case, like the valid use cases for having two separate modules that do the same thing differently is very slim and I. Don't think that you know our arm philosophy, here's you know. Eighty percent of sites aren't going to have to flex later modules.

A

So if you have one that is legitimately an add-on, it should require the parent one. If they're separate modules, you should choose one and I think that for backdrop, one that being our policy is realistic, long-term trying to figure out a better way to detect, which version of libraries already included and change them. Is you know valid? That's why libraries module exists for Drupal in part, but I, don't think it's it's super urgent! So um Nick, can you read over that issue and see if what we just said is summarized there in any way.

A

That makes any sense anyone knew who might find that issue, and then maybe we can document it somewhere and then closed the issue just so that or move it to two docks or something um just so we can figure out, make it easier for people to know what to do when they're into this problem. So we are. We do run into this all the time. Yeah.

B

A

It might be also be worth having like two issues like one is like: what are we going to do with libraries in core and the other one is how should contribute with libraries and then have them? You know reference at the top of the issue or something so that we can make it clear all right and then um Luke also had a question about um he's going to be doing a backdrop. Talk on Monday and he wanted feedback.

A

um Haven't read your comment here: yeah.

C

It's just I posted in the reddit group you're just that the my proposed agenda for my my on Monday and and basically I'm just going to install it and be like look if it's mostly like drupal 7, except for you know, here's layout manager in here cmi we're Shh I'll, demonstrate so sometime between now and then I have to learn them um now. I, that's actually thing I made I I thought.

C

I saw like a fairly recent video there that you demonstrated layout module, but when I search for I can't find it so is there did I see that or I.

A

Have an old one, but we were talking about just a day or two ago, making a new one yeah.

B

There isn't a new video on layouts as far as I know, at least I haven't done one. The only one I had was before backdrop was even released. I'd that preview yeah is it does it still work then yeah.

A

I mean it is: if watch the video you'll know what it does, but I think like just playing with it is probably enough to figure out how to do things. I mean there's some kind of concept, things that we were just talking about this yesterday.

A

People who come to layouts from Drupal have very strange ways in solving this problem, because that was the only way you could solve this problem, the Drupal, and so sometimes people's experience will thwart them in their interaction with layouts module, but this'll be like oh I know how to do that, but you don't know how to do it because you had to do it differently and cheerful, but I think people who are new, who come today also be like oh I, get it because it's simple and straightforward, but triple people have never had to solve this problem and it's little straightforward way before.

A

So it's a little tough, oh I,.

C

Mean that's why I'm hoping I sure to spark some discussion and kind of you know see what I know see what we know and see if there's like other stuff there, the people come up with, so I wanna. I want to open that wound and see what happens.

A

One thing that I would recommend for your talk, if you can, is find a way to demonstrate cmi like if you can have either two versions of a local site or a local site in a remote site and find a way to like export config from one site and import it into another one, and I think nate- and I did this at a live- a live demo in a session for the evening, I've developer, conference and I think I mean you only had one site right.

A

You just exported the code, changed something and then imported it back in so then another way to do it. Look if you can't have two sites, but using these or interface for cmi, explore and import I think it's going to blow people's minds, so that would be good a good place. To so I mean if they've seen Drupal 8 they've seen something really similar, but I think doing the same thing with backdrop would be compelling yeah.

C

I know that was that was sort of how I'm gonna create you know to local sites, and do that. You know export something, drag it in the finder from one window to another, and you know important the other one and have that show up. Yeah.

B

You know a Matt Cheney has a great demo that he does and he uses Pantheon. So he sets up. He spends a Pantheon instance and then on his localhost configures, all of the content, types and everything and then switches over to the Pantheon site and then just imports the entire config. So he sets up content types and fields and things like that on his local and then he's like.

B

Oh now, I'm going to move this to Pantheon any just like imports that config and like the entire site kind of gets replicated over without actually deploying any code which is kind of interesting haha yeah.

C

So today is there: does he have a recorded video of that or it's just he's been doing in person.

B

Where was that he does it for gerbil eight, he doesn't actually I mean his demo interpolate, but I mean you can do the same thing backdrop. So.

C

Who's, complete demo, he's probably he's probably getting it right now in columbia. Right, oh yeah,.

B

Yeah, that's where it was yeah yeah. That's it that's it, and so it will probably be on YouTube shortly. Oh.

C

I've ripped off Matt before I'll. Do it again, that's fun all right, I think I got enough each other, but I've got a I've got a posting reddit. If anybody wants to jump in- and you know make any suggestions, I would totally appreciate that. Ok.

A

Let's see I guess, that's it. Unless anyone has any other questions, um what got a good order, yeah.

E

um I just clarified in chat that the backdrop CMS sprint at mid camp is on um this brand.

A

Is on I, don't know if we're sponsoring it, though ah gotcha I wanted to give them money, but I'm not trying money. So, what's.

E

Getting an email here, if, if not moments ago, in a few moments, clarifying some of that okay.

A

um And then uh yeah, let's see other exciting things going on.

B

We need this. Everybody wish Jenna happy birthday to birthday today, hahahaha.

E

C

A question: what.

E

Can I do it South by Southwest I'll be out there with for the whole week with Matt chain? Him and I are doing that Drupal 8 presentation. What can I do to us important metric up all night? There tell.

A

People about it.

E

Can't stop me anything outside of what you expected to do already mean anything special.

A

I wish we had like that job t-shirts or something that gets on you, a box that we don't I, don't know. I, guess just tell people about it.

A

Evangelize as much as you can I mean right now, we're so new that very few people actually know about us, especially people outside the triple world, and you can talk to people or like have you heard of Drupal I crawl vaguely like the order back job, because I think that you know we're still kind of under the radar for a bunch of people and the fact that we're out means that anyone can try it. You can spin up on Pantheon. You can launch a site, there's a bunch of cool stuff.

A

Going on that people who you know maybe WordPress fans might be interested in learning about so.

E

If you want to design an order at dolla pay for printing and shipping of whatever you like, oh my.

A

Goodness any designers, alcohol, okay, we've gotta, call it Darius. Today we have to make this happen.

E

A

E

A

E

A

Be fabulous good.

A

All right: well, if there isn't anything else, then we should wrap this meeting. We will meet an IRC on town backdrop if you want to tweet at backdrop it's at factor of CMS and you can find us on the internet doctor CMS, org yeah. um We all hang out together all the time on these google hangouts every Thursday. So that's fun in yeah, we'll see you all on the Internet.

A

B

Guys, thanks for joining.

A