 Hello, is that work? Yeah. Hi. I think I will wait one more minute Just to make sure everyone's right if you're in the right room my This is planning for Drupal 8 1x and 8 2x and our future together. Hello. I'm Tim Plunkett Thank you I'm a senior engineer aquia. I'm a core developer and I maintain a bunch of stuff in core and I'm currently focused on d8 panels, which is not in core yet So my basic premise here is that core is awesome and the more stuff in core the more people will realize that triple is awesome and that you know small core and hiding everything in contrib is backwards, you know and not conducive So if you disagree with me on this Wait till the end, but I hope this entire thing is predicated on the idea that core should be bigger So to begin semver semantic versioning changes everything everything we've ever known about core and the core workflow and The way we add features and change core is completely different now in Drupal 8 we can no longer make any Backwards compatibility breaking changes. We can only add new features We can only add new features now in future versions of Drupal 8 so 8.1 point zero 8.2 point zero Until Drupal 9 happens And also now we're going to as per Jesus keynote. We're switching to a more predictable release cycle So we're just gonna release, you know 8.1 gonna pick a date and it's just gonna happen we're not gonna wait for us to rewrite everything from scratch and add 30 modules So the the biggest thing to me about the Drupal 8 cycle has been the contributors so of the top 50 contributors only 35 of them were really even barely active in during Drupal 7 and 20 of the top 50 had zero commits at all. I didn't even touch Drupal 7 and Of those top 50 contributors 45 of them are still contributing within the past week And over a five-year period, that's pretty good Those those contributors are also familiar with You know the core contributors are familiar with contrib modules Because very many of them are active contrib module maintainers Which gives them kind of insight into how things might go in the future And I hope there's a bunch of them here and you're gonna help me with this presentation My request to you is please once I mean well Drupal 8.0 point I was gonna come out and we're all gonna go on vacation Then we come back. We have to keep working. We can't just you know rest on our laurels and You know there's a lot of work left to do My plan my hope is that we collaborate we continue to collaborate in the way that we've collaborated in the core queue You know just because I maintain this one module and everyone else maintains their own modules Doesn't mean we should work in isolation. It's very important like the You know the benefits of working as a team cannot be stressed more Drees mentioned even with these the new feature branches that we're gonna have He said cross-functional teams get the best results. We've seen it in the multilingual initiative That if you have a bunch of people with different, you know approaches You can the code you're gonna create is gonna be that much better than just one person working solo I think that contrib is gonna be very important to like figure out how to use all these new APIs in conjunction with each other and You know iterate on what course done and take it to the next level and I think that it's really important for us to share code between modules So for example, the which I'll get to later layout plug-in is a module that allows You know the user to provide a layout There's really three main modules that you use and contribute to do layouts context Display suite and panels and all three of them use different code But in Drupal 8 display suite and panels use the same exact code to do their layouts So you only have to write one kind of you only have to learn one layout engine Everything uses it and then that's gonna be something we're gonna try to put in core so the more we collaborate and contribute and You know distill the best practice the more code we can put into core Which will then make writing trip modules even easier You can count on C tools. So if you've ever used C tools in any version of Drupal It's just a bunch of stuff. It doesn't really do anything by itself But you a guarantee you use the module that depends on C tools But of those 11 things that these will happen to do in Drupal 7 9 of those are in core So see tools is pretty empty as of today. I think the only two things that didn't go in were the form wizard and the like user generated Like user UI entered CSS writing directly to a file This is the only two APIs and see tools that aren't core as of today But the D8 see tools modules already starting to be things are already starting to be added to it to kind of facilitate the next thing so for example Stuff around plugins. We have the new plugin API that used to be in C tools. It's now in core But there's extra things that that we could have done in core that are being done in C tools until such a time It may or may not go in Yeah, I already mentioned this put my slides in the wrong order. So We the but the main thing in which I didn't mention is the well-scoped feature sets So if you if we're gonna be working on new features trying to add them to core It can't just be like add views module to core because there's no way that a 2.5 megabyte patch is going in at this point It's really hard for one person to kind of define a set of features And it really helps when there's a team of people that especially ones that build sites and That really helps not all core developers build sites anymore It's really useful when when there's someone who actually uses these modules on real-life production sites To tell you exactly what is really important So this is the fun part. What should we work on? That's that's what I got blank space so There's a bit Lee Triple con you are which is the Twitter handle 8 1x everyone open your laptops or phones I'll wait What the internet So if you go to that We're literally gonna spend the rest of the session actually writing this stuff up Yeah, sorry triple con you are 8 1x Now I have to figure out how you get pirate pad to there we go Features everything that we're gonna add from here between now and triple nine What do you got? Okay, so pirate pad doesn't work on iPhone. Sorry everyone So I want to excuse me The pad is full All right, we'll just yell things we could type them in and if people use your microphone well make suggestions Yes, that's what I was gonna do. Okay everyone Let's see if someone delete my no, I can't scroll there we go So I want to talk real quick while everyone's typing about layouts. So the concept of layouts Is kind of split into three different things So the actual like plumbing the API for layouts is Right now in a module called layout plug-in as I said before it's used by display suite and panels You can go download it. It is stable. It hasn't really changed even for you know API changes in core It didn't even really break it. It works. It's on production sites now and It could be very well the first feature added to 8 1 the other two parts of it are the layout UI so you know actually Seeing the layout on your admin site and being able to drag things back and forth and the final part Which I don't even know if we want has anyone ever used the panels flexible layout builder show hands Like a dozen people how many people you liked it No hands how many people looked at the code it generated and then really really hated it everyone Yeah, so I don't even know if we want to code that it could be fun could be its own module I don't think that's going into core the other thing I just put media just because I know that was one of the big you know killer features that didn't really make it into 8.0 I will leave it to the media team to kind of help define what those things are Hope to turn this into a blog post and kind of set the set the stage for what we're gonna work on So now let me look see what we got editorial workflow. So there's workbench if you're a d7 site builder and That's about it Anything else anyone used for d7 work workflow editorial workflow CPS is that SPS and CPS The new one that's Earl. Yeah, so CPS is the is pretty awesome It's very recent and it came out since I last built a website. So I can't speak to it personally I think yeah, it's like if you could thank you I think those two kind of those teams are hopefully gonna figure some stuff out I know that some of the Palantir and some people from tag one have talked about where workbench is gonna go and That's the thing. We don't need to have a d8 version of workbench. It could be called anything we want Just because you know, it was called something and we had three competing solutions in v7 doesn't mean we need to do that We can have better namespaces for our modules Let's see also got a delightful content authoring experience. What d8's not delightful enough No, okay Yeah, so there's been a lot of changes to The d8 country content authoring experience preview is actually like a real preview this time You know, it's in two columns. You have some you have a whizzy wig But there is a lot to be done. We're not quite on the same levels as WordPress or any of those other competing solutions Peter And it's fine. I'll repeat it and hopefully it'll get typed in So we need end user testing we need a Lot of it So that was one of my favorite slides from Jesus keynote was the one about how we shouldn't just do our usability testing every four years When we're done it should be built into the workflow and he didn't call out specifically when he said Cross-functional teams. I was sitting next to a UX researcher who was like jumping out of her chair with excitement Because you know, you don't need to be able to write code to contribute and if we're able to loop in people Earlier into the and build them into the flow of working on these feature sets We'll have much much better stuff and we won't have to go every three years the University of Minnesota and want to stab ourselves I Know for just for example the panel's team right now We have you know the requisite crew of back-end people But we've also been working with a UX designer and a front-end developer and like actual product owner Project manager and it's really changed the way that we work on contrib And we need to do that for all of this question. Yeah, there was law yesterday. There was a talk about Crap it was about to create read archive and purge And I think that's also something that really should be in core. Yep. Did anyone write it down? Yeah, that kind of I didn't know that before I pick pirate pad. Oh well For the people who don't know it's about when you delete content. It still remains in Drupal and you have to purge it So you can get better audit reels for applying to ESO standards for example but also to The recycle bin for example What's normal in YUMLA WordPress, but not in Drupal when you delete something. It's really gone Yeah, I agree and they look that so that was Dick Olson, right? I think give that talk and he also gives his usual talk about how deploy module is amazing That would be another I'm gonna write that one down myself. I think that Like, you know, it also deploy actually does have a good namespace I'm like whatever the thing was that was before deploy whatever Deploy would be great if we could really You know re-architect it for on modern d8 principles and and as I said included, you know Some UX testing along the way yesterday I attended a session on composer where they're trying to get those in It seems like they're trying to get too much in an 80 and maybe that's an eight one Plus I've got some in composer work that I need to integrate in with theirs that I think we can do better in any one Yeah, I Interesting you mentioned composer. It's not since it's not actual It's dev only right. It's it's to pull in and code basically it's not like a front-end, you know It's not user-facing But it is very very important But I also think that our use of composer right now everyone knows it's bad and it's wrong and it needs to be fixed I use composer for site building on yeah as it's like seven x and that stuff can can move date Could be easier and better in 8x right. Yeah, so the composer manager module tries to do some of that, but I think that We can Improve that we don't need to wait for a one. Basically. Hopefully we can fix that like during the 80, you know, we could It can be it can start tomorrow. It's not an API change to use composer and fix composer Right. Well, yeah, I Think it's categorized as a bug so it could be fixed like anytime, but yeah, it's very important Okay, so yeah, we did also autosave I think autosave is really cool. The other thing I want to put on here is the so we have Previews for nodes now as if anyone's looked at do triple it recently and hit the preview button It's pretty great, but it's hard coded for nodes I mean, there's a lot of other things we want to preview like comments and any now that you Now that writing entity types is super easy Well in theory and compared to triple seven it'd be nice to be able to you know And stop abusing content types for everything and write, you know, custom entity types But you'd want to have preview for that So so I preview all for all other things is a very important to me So we got automated testing. So we had a very late Valiant effort to put Like be hat and mink based tests into core and it like there's some of the plumbing in place But we're not there yet and that's I mean, there's so it's like, you know You're not allowed to fix any PHP bugs without test coverage It's just a rule every time you got to fix something you need a test for it If it's a if it's a visual regression no test coverage. Just commit it just hope hope for the best Hopefully, you know that enough people looked at enough different browsers and off different configurations So that is going to be huge Especially if we continue iterating on things like content editing and editorial workflow we need need need front-end testing for that and Automated performance testing I know there's work being done on that right now and that would be a killer feature every year Yes, we have a discussion today about entity stuff and You're going to do it similar as you plan the sea tools so we're going to have the entity module in group in contrip and They're going to put stuff in there and then work on getting it into core over time that will include like better you default user interfaces like revisions and possible also preview So that should be the place to work on everything related to entity awesome. That sounds great Okay, so automatic core upgrade for small sites This is an interesting one. I Know what was it? Was it word pressure? No who got recently? Yeah, and everyone just lost it when all their sites got fixed for them and then all of their code broke and So that's that's that's what I don't have personal opinions on because I think that's scary But I know a lot of people really really want it and but we need to do it, right? We're just gonna look so stupid. I mean that just happened in like the biggest most prominent CMS that everyone else knows about and They got it wrong and if we get it wrong, too, you know, it's gonna we're just gonna It's gonna be embarrassment so Peter as an employee of a hosting provider. I'm sure you think that I Worked there, too. Um Yeah, I don't I don't think I mean, honestly, it's something that maybe the hosting providers iterate on and then we figure it out It's that's like you could be the contribe of that Because running a like the automatic will fix your stuff for you as an optional control module doesn't really make sense As much, you know, you have to know if you have to know about it in advance. It's not gonna help you So More usable fields UI, so this is something I haven't been in on any of the discussions I don't even know if it was talked about this Drupal com, but there's been a lot of talk about a more generic Like data modeling UI Taking the field UI kind of to the next level and just beyond the idea of attaching fields to to entity types and and there I think that's really really interesting I know there's a lot of people in this community that can talk about content strategy and all that And I'd really love there'd be another easy way to get non coders or people who aren't doing code based work at that time to work alongside developers and improve improve Drupal Rest support and yeah, I mean it's we have better rest support than we did before but we could have better rest support In every release rest, you know and not just rest. I mean we use rest as kind of shorthand for all of that and Services and everything else and there will always be the services module But maybe the services mod parts of the services module could go into core as part of you know improving a rest API Some equivalent for features overrides. Who put that in there? Okay, so who here has built a site using features Who has enjoyed building a site using features more importantly? Who has used a distribution that used features and then had to maintain it over a long period of time So that's why I did my most recent job and features overrides Makes it less terrible. I don't really think anyone knows yet what that's going to be like with CMI There's we had you know, we haven't really gotten our feet wet with that Right. So yeah, the config module provides a UI for exporting individual single parts of configuration As well as just dumping your entire site and importing certain parts of the configuration And you can use it as developer to see what you're doing what's been changed and whatnot But there there's still no like I don't know that how distributions are going to use CMI properly because there's no way for them Once once their distribution is installed writing upgrade hooks for that saying they want to change default values It's going to be very tricky. I don't know how they're going to do that So overriding that on the fly or you know any of the different mechanisms. It's going to be very interesting Yeah, it's sorry you can use the mic There's already some much common in drush for config and there's also It's called config update module. Yes, that allows to change default config settings on the fly So that could be used as a right kind of overwrite thing Yeah, and I think we're that's going to be one of the things where we're going to end up with four solutions and Then we're going to have to try to figure out what the best one is And that's the kind of thing I mean, we don't know how long each you know the time will be between 8 1 or 8 0 and 8 1 and 8 1 and 8 2 yet Is it gonna be okay? So it's six months between each one and We don't know how many features can go into 8 1 depends on how 8 0 goes So, you know, there's going to be a lot of time to kind of get this right But the overall message I want to send to you is like let's talk to each other And we also we kind of get a fresh start all these modules have to be Ported and sure everyone's gonna do straight ports because they want the thing to work yesterday but keeping an eye towards the future and Porting while talking to what your competitor module competitors. That's air quotes for the recording You know to to to come with the best solution I mean most of the modules out there except for the ones that represent third parties that have like business interests Most of the these modules are just it's free code like no one has Like other than pride and like the time they invested in it There's not there shouldn't be that much attachment to a certain approach if if we can finally the still the best approach We should work together to do that Graph QL. Yeah, that got a huge shout out in the keynote and the Dries note And I think that is something that's very important to the future of Drupal I'm not gonna say it anybody Dries did I Don't know the best way to kind of integrate into core, but I think there's a lot of a lot of cool stuff. We can do For dear mention the any day prior improvements, which is great Permissions management and the permissions page not sad my old boss used to have a bedsheet made that was a printout Basically of the permissions checkboxes and and yeah, and Morton has a pillow of it That would make me sad. Yeah, no, I think I think I don't know how we're gonna do that But that's sure I mean it's it's one of the first pages you go to as a as a novice site builder and or you know I'm a site builder like a site maintainer. It's like oh someone wanted permission to do this thing load the page five minutes later Like what happened? So we really need to work on that. I don't know who's gonna do it In triple seven you have fast permission access who improves it a lot. Yeah, I mean there's UI based ones, too Just like the permissions filter module and stuff, but I think we need I mean, we can't break API's but we Need to think of it more than just like re-theming the permissions page although that might also wait for nine I know there's been talk of re-writing the permissions API to be hierarchical Which would be really cool But that's that can't happen anyone Another one our own permission is like Most of the D7s are like global like the parts using global function and when you work on like a big site You cannot really give site configuration permissions to everyone and you may need it for a specific content type or a specific You know like even we don't even think about those things if it's a small site. So We end up creating, you know custom modules or you know, node specific admin pages I think they have used but few other places. We don't really have an option other than adding menu alter or something Yeah, there's a lot of work to be done with that Path out on token UI in core. Yeah, I mean we have token support We could have the token UI. I mean, it's been I think it's being rewritten right now for triple A I mean, I know the module is but I think the token browser is being rethought and You know, it's it's crashed my site a bunch of times every time I try to open the token browser. It's just like there goes my Chrome page So that there's been a lot of work over the years to try to mitigate that problem I don't know what we're gonna do But we can't put it in core like it is in contrib right now path auto. Yeah I mean, honestly, it's like if they'd read had two less kids and three more of himself We'd have path auto in core Or, you know, just people to help work on it You know, everyone sticks to what they know kind of but this is kind of the dates the brave new world of awesome And anyone can kind of jump in and take ownership of something and just be the new Driving force behind a module or an effort or initiative Covert convert Convert most avenue I can be able I don't know what that means Someone explain it. Oh Sure Is it yours DJ? Yeah, that's that's mine. It's it's an idea. I think CHX started initially So, you know, currently we are creating all the config forms and saving them So it is possible if you can If you can use the config schema to generate the oh so like config inspector module But for the form half for form as well as if you can so that's one part of it So simple configurations using route or somewhere you can easily just specify the part and it just entered the config form for you It's much cooler than the D7 Admin settings form right it become and the second part is if we can if we can make Views of type config entity then we can create a views of use also content types of views So again, it's back to the place like if you have an enterprise site You don't want to display all the content types in for a for a one You know content site builder you want to provide them set up content types. They can manage So you can have a different set of pages and stuff like that. Yeah Yeah, right now in D7 you can I mean sorry in D8 You can only make views of content entities So things like nodes taxonomies and users things that are stored in sequel things that have fields Config entities which are stored in YAML sometimes cannot be displayed in views and mostly because No one is brave enough to write the back end for views It could be done and it would be awesome. I recently tried to hack together like a happy so I could make a view of blocks and it was like three days of pain and It would be really awesome if someone stepped up and worked on that I know just today someone was working on kind of the reverse Like a JSON be based storage of of all entities But yeah, you have the deep dive deep dive deep into views API is to make that happen, but it would be pretty great Snowman we pretend someone didn't put that in there default content core that almost happened Secretly it almost happened Previous next mostly worked on a default content module for D8. It's on github and it works pretty well as far as I know I think that that needs a lot of input from the community and from usability and accessibility and performance and all that stuff I think it does go along with content migration and deploying module and all that and we can look to see how Those things can work in concert. Yeah, so the tour module is kind of near and dear to my heart We added a thing using the joyride jQuery plug-in to be able to like tour around an admin UI or any UI to learn How to use it and I think we have one and it was the one that we added initially like a year or two years ago Which is how to use the views UI, which is great But we really need to to actually add those tours. I don't think that that can go into a anything really I mean, it's not a feature and That could also live in contra forever too. I mean it's it's that's the other thing though Is it since it's a tour for new people you kind of want to in Core when you install it for the first time because how are you going to know to go look for downloadable modules? Crap we talked about excellent site map question mark Question mark. I don't know. I mean it's cool. It works pretty well. I don't know how much it needs other than a straight port I don't know if it needs to be in core Beauty make the first thing anyone sees beautiful Yeah, let's do that. I know there was a lot of work done or no Well, yeah, there was a lot of work done on the installer It got better but only like incrementally better instead of being amazingly better and you still get dumped into like empty Bartik welcome to your site name We you know the landing page after you first install I'm assuming that means by the way for right after installation like the first one thing anyone sees Yeah, exactly you only have one chance as was said from the audience Yeah, I don't I think that could be very interesting and it's as also very Multidisciplinary if there's some technical changes need to be made to the installer But most of it's just a setting what what to do And that's not something we can you know one person can decide but someone needs to propose some ideas and get the ball rolling It'd be pretty cool Let's see hook up the end Hook up the end is just changed recently again Update deploy. I've never used this model, but it sounds cool So whoever put that plus one Yeah, thanks More llamas. Oh, this is just a yeah, okay Yeah, I don't know enough from Google aid, but it's redirecting core. No Maybe that's a good one for a search engine optimization. Yeah, I'm surprised people didn't put meta tag Yeah, and what they read or two more Damian McKenna's or in an apartment in a pear tree and I had another one HTML meal question mark and that's my original mail Maybe maybe not people mail still in core. I assume it Yeah it's more the expectation from the customer that a meal looks beautiful and It's a pain in the ass now to get it done, right? So we'll just put mail chimp in core, right? Yeah, that will be the best Does anyone so we've talked thanks for sharing all these ideas Does anyone have any thoughts on? Other than what what produce it about how to how to make this all happen other than just like starting coding any Thoughts there I think that so Friday is the sprints and I'm going to be personally working on Panels for D8, but I think we can pretty easily get together a bunch of people to talk about some of these I know there's gonna be people working on og and workbench and rules We didn't even mention rules because rules is already being taken care of so yeah, Jess So I'd just like to suggest that if you have a plan or a dream or a thing that you want to put in core Make an actual plan as in an issue in the Drupal core queue if it's a thing that you think should be in core there's now a Issue category called plan that got added at the last Drupal gun so make a core issue and says Media in core and say I so and so think this is a great idea and then reach out to all your other friends and enemies who Care about media and say help me plan a plan because that's the first step. Yeah, I'd there's I know there's talk About sort of a lease management and planning these feature branches It's all new to everyone and there's gonna be I guess guidelines just that are gonna Angie could confirm like how to properly Propose these sorts of things and I wish that had been finished formulating so I could have shared it with you But Angie's just gonna talk instead. I'm gonna try and talk. Yeah I mean we one of the concerns raised was like People get an idea and they go nuts and they coat it and then they've been doing that for six months before we all find out That they've been doing that and they come back and they're like I did this thing and we're like Oh, we don't want that thing actually and then they feel really bad. So yeah, I think what just said About making the plan first so there's visibility and I don't know how detailed these plans need to be I mean to me it's like You know, we just need to like a list of issues just like a normal meta issue, right? It's like a list of issues with some headings and what your idea is Get that up to RTBC and then ideally one of the product managers such as myself or trees would look that over and Validate that. Yeah, that's a great idea. You know you say I want to put path auto in core This is how I want to do it. I need these back end changes made. I need these front end changes made Here's the team that I've got available to work on this because we want cross-functional teams I think that we would totally look at that and be like go, you know if you want to replace the Toolbar with a Watch We might want to think about that a little bit more. So don't code that for nine months by yourself in a corner Exactly. Don't do that. Give us visibility early and often and that way we have the ability I don't want to really gum everything up in a whole approval process on it be super lightweight But on the other hand, I think it's good to get a check-in before you go completely nuts to make sure you're on the right track And that's basically the idea I'm also playing around with this idea and I don't know how into it boyan and you and Lewis and other people are but I Would love to run monthly product manager meetings after 8.0 where We would do things on those meetings like do a demo of stuff that just got into core or that is in progress because I Would love to get early and often feedback from users on things that we're working on so that We are not stuck every six months getting that feedback or we could get it a lot more rapidly It gets to the user testing and things like that It would be an opportunity for us to review plans that have come in and make sure that we sign off on them, you know That kind of stuff. So I don't I don't really know this hasn't been a fleshed out in any way But I think the general idea is we want to Prototype things as cheaply as possible before we get to writing actual code We want to make sure that people have thought about how they want to get things in the core kind of broken up into manageable Chunks to your point and the best way to do that is to make a plan And then we want some kind of consistency where what you're working on is also within the vision of what the Corbett committers Think is a good deal for this version of Drupal and just that everyone is sort of synced up, you know But but otherwise I think yeah, absolutely. If you've got crazy ideas, let's get a plan together and we can talk about it So thanks Angie One of the things about that people kind of get nervous about with big core is performance Are there things in Drupal 8 that helps that a performance threshold or budget? To kind of keep it fast Yes, well, so there's testing but will we as a community decide how fast like okay, so we want to add this thing Either make it faster or take something else out Yes, no, I mean that so you know individual right now individual changes are profiled when we says oh does this Regress it is it, you know a 10% gain is a 10% loss What can we what and then you have to identify what it is and get down to it like a 2% gain or 2% loss within margin of error I think automated performance testing will help with that, but also so there's brand new cash Everything in Drupal 8 The cashability stuff Wim Lears and Fabian did a talk about or Wim did a talk about it today I think so you can look up the session for that That kind of fixes all of our problems in theory, maybe we don't know yet The other thing is you know a lot of these one of that and maybe not a lot But maybe half of these are just modules just modules you turn them on you turn them off And then we have to decide whether or not to put them in the standard profile not some of them are like Changes to the way core does things Maybe in a not API breaking way or not and those kind of always on things would need to be scrutinized more No, we don't have automated performance testing core, and I think that's going to be one of like the first Things we did you know that all this testing stuff the front-end testing and the performance testing are the like number one focus Because those two things allow us to do all of these other things better And we want to do all this right. That's the whole point of this talk is let's do it right Let's not just write a bunch of crap code by ourselves and do it seven times and then have site builders You know consumers of Drupal modules have no idea what the download That's about it as far as my thoughts anyone else have any other questions or Something they want to bring up to the disagree with anything said and strong and Gower's coming No, I just wanted to point out that we are not shutting down contrib yet, so It is still possible to write some of these things in contrib So you can you can start out in contrib port modules Test them with users use them on sites get live feedback, etc. All of that stuff So you don't need to open a plan issuing core to start working on some of these things But if you went away for nine months and worked on porting some module to to aid and everything worked Then everybody liked it it may still not match the requirements that people want to see in core so it makes sense to Keep that in mind, but it's entirely possible to to keep innovating in and contrib just as much as it was before There's no requirement for it to happen in core 100% thanks. It's a very good point. Yeah, I think I'm personally just So focused on this the work we've been doing on panels It's a huge module it needs a team like one person can't do it Some of these modules are much smaller and much Or not smaller in code size, but just in scope and number of features and the functionality it provides um And so that definitely applies there, but I you know, even if You're working and only ever want it to be in contrib. I still think you should follow this the the pattern we've used in core Of of working with other people that know other things than you Especially since everyone's going to need help learning all the new Drupal 8 apis. I mean I think I Learn everything and then they add six more And then I need to ask six people to explain it to me There's a lot of work to be done there and the more people that learn it everything the better everything will be So Anyone want to have the final say? All right. Thanks everyone. I'll try to get a blog post up to summarize all of this And I'll see you in the issue queues and on the sprints on friday. So thanks a lot