Open Channels FM
Open Channels FM
Inside WordPress 6.6 with Key Updates & Community Insights
Loading
/

In this episode host Abha Thakor is joined by Mary Baum and Meher Bala, as they chat about the recently released WordPress 6.6.

They explore various aspects of the release, including the challenges and rewards of being involved in the development process. Meher, who coordinated the release, shares her experiences and insights on how contributing to WordPress, whether in familiar areas or new ones, can be fulfilling and beneficial for personal and professional growth.

The conversation also touches new features in WordPress 6.6, such as enhanced site editing, automatic plugin rollbacks, and improvements in typography and design flexibility.

Takeaways

WordPress 6.6 Features and Improvements – The episode highlights several new features in WordPress 6.6, such as enhanced site editing capabilities, automatic plugin rollbacks, negative margins, custom shadows, and improved typography tools. These features offer more design flexibility and ease of use for both developers and end-users.

Global Collaboration and Contribution – The episode emphasizes the importance of contributing to the WordPress project, regardless of where you are in the world. Contributors can get involved in various aspects of the release process, from development to documentation, testing, and more. They also highlight the benefits of working asynchronously across different time zones.

Encouragement for New Contributors – They encourage listeners to overcome any hesitations they might have about getting involved in the WordPress community. They stress that there are numerous ways to contribute, even outside one’s professional expertise, and that support is available through documentation and community channels.

Role of Release Coordinator – Meher Bala shares her experience as the release coordinator for WordPress 6.6, explaining the responsibilities of the role and the importance of thorough testing and communication to ensure a smooth release.

Community Support and Learning – The podcast underlines the value of community support in learning and contributing to WordPress. Resources like the Field Guide, developer blogs, and the Learn.WordPress.org platform are recommended for both new and experienced users to deepen their understanding and skills.

Opportunities in WordPress – With WordPress powering a significant portion of the web, the episode discusses how new releases present opportunities for developers and site owners to enhance their websites, improve security, and stay up-to-date with the latest tools and features.

Links

Download and find out more about WordPress 6.6

As Anne McCarthy was not able to join us as planned for the podcast, we are sharing her videos on 6.6.

Get involved links

Episode Transcript

Abha:
Hello and welcome to the WordPress Way. It’s Do the Woo time yet again. You’re here with Abha Thakor and we’re talking about all things WordPress as you would expect. But more importantly we’re talking about the new release 6.6 just out and we’ve got lots of things to share. But also in this episode we thought we would answer some of the questions that you’ve all been sending in about how to get involved, how to get past the worry about getting involved, and also some of the tips from people who have been engaged in the recent processes. So a little bit more different than our usual release series, but at the end of the year in November, we will be doing a reflection on all the releases of this year and a bit more technical stuff too. So make sure you join us for that. In the studio today, we’re doing some globetrotting again, we’ve got Meher Bala joining us direct from India, and we have Mary Baum joining us from the US. Hello ladies.

Mary:
Hello ladies. Hey everyone.

Abha:
So thank you both for joining. I know you probably had quite a lot of 6.6 in your heads for the last few weeks. Meher, you’ve been the release coordinator for this major release and the first time as a release coordinator, not just shadowing so much, been a very exciting time. And Mary, you’ve been leading Marcos and also being involved with some other component stuff, so it’s really great to have you both with us and we’re going to have some conversations today also about component maintenance and those who listen regularly to the show, know that we often talk about all the different ways that you can get involved with WordPress because it is our software and our project and that’s for everybody, wherever you are around the world. So we’re going to touch on those things a bit more.

Mary:
Coming off a release coordinating of six five, I cannot be more proud of Meher who did an absolutely phenomenal job with the release of 6.6, and it was not easy and my heart just sings for the great job you did and for you in general, you are a rising star.

Meher:
Thank you. Thank you for inviting me to the show. Going from Marcomms to release coordinator, it’s different but it’s new. It’s something different in a release than doing Marcomms

Abha
And I think that’s one of the things we want to get across today is that you don’t have to just get involved in a release in the areas of where you are professionally working. It can also be in another area that you want to develop and there are so many jobs in release. It doesn’t have to be just on the squad. A squad is an amazing place to be, but actually it’s a whole community that brings the release together and there are so many opportunities and Maher’s going to share some of the testing ones a bit later in this show as well. So ladies, I’m going to start with some of my favorite things from the release and as previous docs co-lead and Marcos and having been involved in various other bits of the release this time, it was really interesting to be focusing a bit more on the component side and to see some of the things that people have been talking about and wanting and we haven’t quite got there as a community to achieve in previous releases, but to be in this, one of the things we’re going to start with is the site editor experience in WordPress because it really has transformed in recent releases.


And I think that’s one of the things we want to get across today is that you don’t have to just get involved in a release in the areas of where you are professionally working. It can also be in another area that you want to develop and there are so many jobs in release. It doesn’t have to be just on the squad. A squad is an amazing place to be, but actually it’s a whole community that brings the release together and there are so many opportunities and Meher’s going to share some of the testing ones a bit later in this show as well. So ladies, I’m going to start with some of my favorite things from the release and as previous Docs Co-Lead and Marcomms and having been involved in various other bits of the release this time, it was really interesting to be focusing a bit more on the component side and to see some of the things that people have been talking about and wanting and we haven’t quite got there as a community to achieve in previous releases. One of the things we’re going to start with is the site editor experience in WordPress because it really has transformed in recent releases.

Mary:
I just redid Support Inclusion in Tech website over the weekend, mostly the typography and I’ve still got a couple of things, but I did change the theme to 2024 and we were already on 6.6. I’m using the grid layout on the homepage, extensive use of the font library from 6.5, smoothed out and refined in 6.6, and we redid the header, we redid everything and everything is so much smoother. I’ve never redone an entire design in a day.

Abha:
It is a lot slicker and a lot quicker now with the new facilities that we have quicker.

Mary:
And quicker and quicker, and things take the first time.

Abha:
Which is really important that when you get things that work when you first do it.

Mary:
Yeah, yeah. Yes. As somebody who has tried to estimate how long something’s going to take and been off by a factor of five or ten, and then having to do things over.

Abha:
Also with the layouts. Mary, you’ve been talking about negative spacing. Do you want to share a little bit about why that is useful? Because as a term people might think, well what is that?

Mary:
Well, as an example is that the way we’re doing testimonials. Winstina Hughes is the founder of Support Inclusion in Tech, which does pair up WordCamp speakers with funding to get them travel. So when you’ve been picked to speak then you can submit an application and get matched with a company who can underwrite your travel expenses on the same continent. So no flying over oceans at this moment to make the best use of the resources. But at any rate, we had testimonials on the homepage and we have the person’s name at one side and then underneath, which makes it a subhead instead of a kicker. Yes, I am a typography addict and to get the little subhead close enough to the headline that they fit together as a unit, we need to make the top margin on the subhead zero and sometimes we need to make the bottom margin on the headline negative just to get them close enough together. In other cases you might want to have two pictures overlapping. You need to have one or the other have margins that are perhaps negative one REM or negative two rems to have them open. Let’s say you want to do a Venn diagram, particularly a Venn diagram in a pattern, where you will have text inside the parts of the circle that overlap and the parts that don’t, that change. For that matter,


you might have that as a locked pattern that you then or a synced pattern that you then can override by changing that text and just have that ready to go.

Abha:
WordPress 6.6 introduces these negative margins and the custom shadows, and it really does help you make those eye popping designs and because you can add them directly in the editor for the blocks that support those margin controls, you’ve got so much more flexibility. You could do this before with the theme JSON, which allows you to create all these overlapping elements, but to be able to do it in the way we can do it now is so much quicker. As Mary has said, it just keeps getting quicker and quicker. We also have these featured image blocks so that we can use customizable block shadows and all of this just helps us to make these pages look a little bit better, but also gives a little bit more control to our end users. Speaking of end users, if you are wanting to know more about how to do something or if you want to even write documentation for end users because you love a new feature, the documentation team will absolutely welcome you to come and help.


And they’re still working on the documentation for 6.6 as they do at every release and their work is amazing and they have contributors from across the world, so do get in touch if you want to be put into contact with them and we’ll put the links in the show guide as well. I’m just going to go over to Meher. Meher, obviously in a release like this when you’re not just, you’re incorporating lots of the Gutenberg releases that have happened before and you’re hoping somethings will land, you keep testing. What is that like being release coordinator?

Meher:
Being a Release coordinator for any Word press release, it’s a little tough and exciting at the same time because you have to keep a track on what is going to land and what is not going to land due to any tech issues, which will cause a lot of sites to stop working or break. The role of the release coordinator just to check in with all the teams to make sure everything is on track. If something is getting pulled out from the release for whatever reasons, it’s informed to the world that before the release this is not going to be there. So people don’t have that expectation that they want to see this feature and the feature is not available.

Abha:
It is that moving feast, isn’t it? And it really is that live environment, which is amazing, exciting, very stressful at times I’m sure, but also being part of a bigger picture. So Meher, before you joined as release coordinator, obviously you work as a senior developer already using WordPress. Did you know what was involved in a release? Did you have a concept of how it came together, the amount of people that were involved and the amount of testing that it included?

Meher:
Right now, yes, because I have been a part of multiple releases in the past, but when I first came into the release in 5.6 in the documentation team, I was not aware of what goes into a release. I used to read occasionally the release parties but sometimes it gets too late at my end, occasionally just used to read it but not participate. But from 5.6, I became part of the squad. I got to know which teams are there, what roles individuals play, and how does the entire release take place. Becoming a release coordinator was helpful because I’ve already done a lot of releases as a Marcomms Co-Lead after 5.7. It was a new experiment.

Abha:
And I think it really does make a difference If you’ve shadowed before, I think I’ve been involved now in releases since 4.7 and every release you learn more and you learn from other people, which is one of the beauties of working and contributing to WordPress is that you have that opportunity. And the same with WooCommerce. We’ve got a fantastic community growing around us and Do The Woo and being part of that learning experience for yourself as well as others is a challenge, but it’s also very, very satisfying. So Meher, when you put together a release like the ones that you’ve been just doing recently, what’s the feeling when as a developer when you take your release hat off and you go back to look at the release. As a developer, what is the feeling that you have when you first find a new WordPress release?

Meher:
As a developer, once a release is out, for me it is like what new I can implement in my existing client site, how can I make it better or what can I propose to a new client who’s coming to me with issues from their website, how can I make things better for the end user? Be it e-commerce side, be it a block side, be it a magazine side, be it just a simple brochure side. So each new feature of any release helps me think how certain aspects can be better website and how it can help the user.

Abha:
So really it’s an opportunity. And do you think that looking at that, if you are a storefront with a website on Woo or a Cat blogger or anybody who uses WordPress, people who use it as their detailed international intranet, that releases present opportunities and maybe not for the immediate, but something that they can take up later on?

Meher:
Yes, not all the features help instantly, but there will be some features which will work as soon as the release ends and in the day-to-day life of a developer or a user or a person who’s just using WordPress to share their updates.

Abha:
Now I know Meher, you use a lot of the Gutenberg releases and some of them before they go into Core as well. What do you see as the main advantage for people now that we do get so many Gutenberg releases coming into core and being part of that major release?

Meher:
I have only a couple of sites which I use direct Gutenberg on, the others all features come when added to the WordPress core. For the sites which I’m using Gutenberg, it’s like an experiment to see what advantage will these bring when it’s added to the core.

Abha:
And I think that’s a good way of looking at it. It’s a way of helping people really understand what’s their experiment if they’d like to beforehand, but once it becomes part of core, it is much more seamless and having that is a great thing. So in 6.6 we have this automatic plugin rollbacks now and that plugin management that we have really does make it so much safer to be able to try new things, try the plugins. I’m going to go to you, Mary, because I know this is something that you’ve been really wanting to see in WordPress.

Mary:
Yeah, I’ve tested it a bit and I have some involvement and been watching the ticket. The kicker is that it is not optional if a plugin update is an automatic or otherwise, but I think mostly automatic. If something happens and you get a fatal error with an automatic plugin update, it automatically will revert to the plugin version that worked. So there’s no reason not to turn on auto updates, and that in turn makes not only your site but the entire web more secure. It just does, and I’m saying that personally because the official position is not to claim that plugin updates necessarily make sites more secure. The fact is, well particularly now when a lot of security issues are not coming from automatic are not coming from outdated plugins, they’re coming from compromised credentials. The fact is that abandoned plugins, and in this case I’m going to mean, I’m going to say abandoned by the site owner who’s not updating them. The plugins are doing a fine job of keeping everything updated. If you for whatever reason are not checking in with your site regularly and plugins, updating themes, updating core, you do become vulnerable because let’s face it, at 43% of the web we are the open web’s last great hope. We are the open web, so it’s up to us to make it as easy as possible to keep sites current and to keep security up. It’s that simple and this is a way for upgrading everything to be a no-brainer.

Abha
Thanks Mary and Mary, you’re also a component maintainer. In fact, we both have a couple of components in common too. Can we both contribute to some of those maintaining, and I was very excited to see some of the bulk edit component maintenance items in this time and to see things that we’ve been really wanting to move forward actually getting there. So Mary, could you just share why people should volunteer to help on a component?

Mary:
Again, it’s everything we can keep maintained and keep updated. We contribute to the security of the open web. Somebody once said to me, why do I volunteer my time to organizations I care about, because I am selfish and greedy, it makes me feel good.

Abha:
Also improves what we’re doing. So if you are thinking that there’s tickets that you want to see and they’re all in the same area, then have a look at what that component is. Is this something that you can help? There’s normally quite a few maintainers for each component. They all have different skills. Sometimes you’re just trying to get people to collaborate on something and help push something forward. Other times you’re looking at the code, sometimes you’re looking at patches. There is so much variety that you can get involved with, and we’ll put a link in the show notes to some of those places too and we’ll put a little bit of a guide as well about how you can get involved with that because at Do the Woo, we try to be part of that collaboration and encouragement journey as well.

Meher:
What I’m saying is, if you want to be a part of any component and you don’t know where to get started or you don’t want to ask question because you feel that it may not be the right appropriate question. But I’ll always encourage you to ask questions because all questions are great questions. There’s a lot of documentation in the handbook which helps a normal user or beginner user to get started with how to submit a patch or how to take a look at the number of components. We have because we have a lot of components which goes into the entire WordPress software. So just ask questions or just read the handbook and you get answers. Otherwise you can always put your questions on the Make WordPress Slack and someone will respond and guide you to the right documentation.

Mary:
Also, the next time you’re in the Admin, click on what’s new and you’ll see four things. You’ll see the credits, you’ll see the four freedoms, you’ll see something else, but there’s a fourth button called Get Involved was started. That was a ticket that was opened more than 10 years ago by a friend of someone who was recently Marketing team rep, and it was just committed a year ago by one of our co-maintainers. So there’s another reason to become a component maintainer, and if you click on that button there will be a bunch of concrete steps you can take.

Abha:
Absolutely. And also if you’re in the Admin , you can see on the right hand side details of meetups. Now there’s WordPress meetups all over the place and all over the world and it’s a great way to get involved and find out more. And many of the meetups at the moment are doing features on 6.6, so make sure you check those out too. We’re going to have some links in the show notes too to a wonderful video by Anne – who normally joins us for these releases and unfortunately can’t be here today and – all about negative margins grid block and custom shadows and it’s well worth a look. There’s also a lot more resources about things like 6.6. There’s the Field Guide that comes out with every single release and that links to all the different documentation about items in that release. If you’re a developer, it is the place that you need to be.


If you’re an end user, it’s a great way to learn and if you want to just start contributing to WordPress, it’s a wonderful place to actually learn how WordPress works and be part of that solution too. So for 6.6, there were 299 core track tickets and 108 of these were enhancements and feature requests. That’s quite a significant number. There were 16 tickets focused on performance, 24 on accessibility and 15 on modernizing code and applying coding standards. This is what it takes to go into a release. These tickets are from people all over the world, people who have contributed with different skill sets. We’re now looking at volunteers for 6.7. Again, we’ll put the link in the show notes if you think actually maybe I can get involved too. Like all three of the people who are on this podcast today, we’ve all shadowed, we’ve all been involved with testing and got involved in different aspects of a release. You need to only get involved in a way that has to suit you. You do not have to take on things that you’re not happy with or take up a commitment that you don’t feel that you could do at this time.

Mary:
The way I got involved was sometime in 2018 or 19, I just started keeping my desktop Slack app open and I would look at it occasionally, like just with my left eye. And gradually I started seeing something that I felt like I could comment on or ask a question about, and so I did. And look at us three, now look at us four.

Abha:
There are lots of ways as Mary said to get involved. And for anybody who’s not sure how, we do love all of your messages after shows have been out and I know people have said about what are these notifications, what are these Slack channels? We will try to continue putting those links to that, not just in the Show Notes, but also we try to contribute in other slacks in the Make WordPress community. And also if your local community is wanting to do something and you’re not sure how, get in touch and we’ll try and help. And more importantly, we want to try and boost the voices of different communities that don’t always get airtime. So if you feel that yours hasn’t and you’re doing something exciting with a release or something exciting in WooCommerce, do let me know and I can be contacted through Do The Woo, on the Make WordPress Slack, or on Twitter on NonStopNewsUK.


I’m going to jump back to 6.6 again because there are still a lot of features we want to tell you about. So I’m going to jump over to Meher. In terms of this particular release, we’ve looked at pattern management and one of the things that I thought was really good was that 6.6 makes it easier for users with classic themes now to manage the patterns on their site. I know you feel very strongly about WordPress keeping and allowing people who have older versions, to a degree, to still use it and to be able to advance and improve and update, but in a way that they feel supported. Do you think that’s how we’re going? Do you think that changes, like the ones in pattern management and classic themes, are going to help people to move over to things like the block editor?

Meher:
Yes. Having patterns support classic themes will encourage the people who are using classic themes to slowly and steadily think and migrate to full side editing, and make them a bit confident that what they do in classic editor, they will be able to do equally or more better with full side editing. So it is the hope giving to classic editor people that they will gradually with time move to full site editor.

Abha:
And I think having that pathway is actually really helpful. So if you’ve not tried Block Editor yet either in your WordPress or your WooCommerce environment, have a look at some of the update and it is, as Meher has really well explained, an easier route and will give you more confidence. The other thing that is also I know very close to Mary’s heart is this idea that you can mix and match styles now and colors and typography in WordPress 6.6. So before I just go to Mary on that, I’m going to give a shout out to the developer blog. So Justin Tadlock has done a wonderful feature on the blog which came out a few days ago, all about how to do this. It’s a great tutorial. I’ve been through it from both the editorial team but also trying it as a WordPress user and I’ve had great fun registering color variations and following Justin’s example of creating an emerald color palette. So that is the Developer Blog and it’s Developer. WordPress.org. And I’m going to just go over to Mary so she can tell you a little bit about why all these things and all these new typography and styles and colors make WordPress such a better tool to use.

Mary:
I am a certifiable typography addict from the age of 14 – which is 50 years for me – and it has never been easier to use really quality typefaces. Google fonts, yes, and there are a lot of great typefaces on Google fonts. But there are also great typefaces on Adobe type and if you have any sort of creative cloud subscription, you have everything available to you on Adobe type and that’s slightly complex. But then there’s a new Monotype subscription where for various not horribly expensive amounts of a year, you can actually download font files that you can then upload to the font folder right in the font management interface in the block editor and has almost anything you want. I mean from major foundries like Monotype and Linotype, places that have been around for a hundred years. But also current contemporary foundries like Latino type and new places like set sales studios and any little type stand you want to follow from the current serif fonts with ligatures and loopy roundy type or brutalist or whatever.


Just amazing. Those are now available in your WordPress site and you do not have the write one line of code that in queue a style, but you don’t even have to do that anymore. Furthermore, your admin clients and those people we call site builders who buy fonts, install it and buy plugins and install it, install them. Those people in the block editor now also can control the type and you can control colors and list any type you want in theme JSON. There’s a whole new world out there and frankly I should be in a 12 step program about all of it.

Abha:
It is a very exciting time in WordPress, isn’t it? And if you’ve never discovered it, this is the time to come and have a look at it and see how it can support your WooCommerce journey too. So also in this release, we have some lots of things on API. So do check out the Field Guide and the links will be in the Show Notes about that. Also, just a reminder that support for PHP 7.0 and 7.1 is dropped in WordPress 6.6. So the minimum supportive version of PHP from WordPress 6.6 is 7.2 0.24, but the recommended version of PHP for WordPress 6.6 remains at 7.4 or greater. So do check the backend of your website, see what PHP you’re running, if it’s controlled by your host, have a look if they can upgrade it for you. And it just as Mary’s talked about, it helps to make a more efficient and secure web as well. So I’m going to go back to Meher. In this release, as in all releases, we have improvements in internationalization and we also have lots of polyglots that are involved after every release. What do these volunteer translators have to do with a release?

Meher:
The volunteer translators help the release by translating the new version of WordPress into different languages because the 45%, 46% of the web which uses WordPress doesn’t always use English as a default language. There are many websites out there which uses WordPress in its own language. For example in French, in Hindi, in Spanish, in different languages. So when the release is published, the same English words have to be transmitted is multiple languages. So these translators volunteers help to translate and keep the release up to date so that when a non-English website which uses WordPress updates, it doesn’t break all of a sudden and from Spanish everything goes into English. It just makes sure that whatever language you are using WordPress in has the right language for the new version.

Abha:
Thank you Meher and a very, very big shout out to all those polyglots who have been working around the clock for many of them to translate the latest release, their work is just amazing and you can get involved with that too. See there’s so many ways you can get involved and we’ll put that in the show links. The show links are getting bigger and bigger at this rate, but that’s as we said earlier is how we like to do things at Do The Woo as we like to be part of your journey and hopefully learn alongside you but also help you navigate the learning process. Talking about learning there is Learn.WordPress.org and people who follow this show know that we love to highlight this and we’ll be doing something on this and focusing on releases in the summer as well. So do come back and see what we’re doing on that.


Just a few quick hits on the release if you haven’t caught them already. There’s a new version of React and that’s available in WordPress 6.6. So do again check out the Field Guide and because this is the place that you will get all the details that you need about it, there is lots of preparation help too for the React 19 upgrade. So if you’re a dev and you’re not quite sure this is going to involve make WordPress, core has got it covered. One of the things that we often get asked is how do you get involved with some of these things when you work or you live in different time zones. So just with the two guests that we have on today, they are in completely utterly different time zones. Meher, what time is it for you right now?

Meher:
Right now as we record this podcast, it is 1041 PM.

Abha:
Meher and Mary, what time is it for you?

Mary:
Quarter past 12pm, just after noon.

Abha:
For Bob and I on the show at the moment, it is just about quarter past six in the evening. So just this little microcosm shows you that you do not have to be in the same time zone. Some things can be harder when you’re not, but there is a proposal and it’s just been published by Joe McGill, the current core team rep about what time should the Dev Chat be for 6.7. We will put a link to that because they do want your views and also if you are not able to join anything like the developer’s chat or any of the live experiences that exist around a release, then you can contribute async and I’m going to go to Meher first. Meher, you’re often in a completely different time zone, I never can keep up with which time zone you’re actually working in the moment. But if you could share as some of your final thoughts, why is contributing async worth doing?

Meher:
The time for each release good for the Europeans as well as the Americans. It’s not really good for the Asians but for 6.7 as a lot of folks in the release are from the Asian countries. They’re trying and see if they can schedule the release parties in a better time zone for Asia. And if you can join those parties, you can come to know how the release cycle goes. If you cannot, you are always most welcome to contribute async. You can test out the release cycle and if you find some major bugs or your test website crashes or it just doesn’t load, you can always create a Trac ticket or leave it on the code channel. What exactly happened when you updated something and someone will definitely help you when it is a good time in the European American side, one of the reasons I encourage people to participate, whether async or at the given time the release is because you are helping the release be better when it is officially released. A lot of people say that there is a bug when a release happens, but if you want to help solve the bugs, come be a part the release cycle and let’s avoid that. Let’s try and see if we can avoid that as possible and make WordPress better than we did because that’s how we grow in the entire world.

Abha:
I love that answer Meher, thank you very much. I think that’s just perfect and as Meher said, it really is important. So Mary, you’ve worked in the US predominantly and worked normally in the US’s different time zones. What has it been like to actually work globally in the way that you have in core in other teams as well , and what do you think makes it special about WordPress?

Mary:
One thing, it’s really efficient. I can draft a post, like a release post or a thing about coordination or a proposal in my evening and tell people it’s there on Slack and wake up to feedback when I work on the Dev Blog. Same thing in my afternoon and evening. People are often asleep, they wake up when I’m asleep, when I wake up, things have moved forward. That’s pretty nice and I know that it’s one thing that we think of across the project is essentially it’s a way to cover questions. Certainly on the support forums, it’s a way to get questions answered from users 24 -7 because everybody has different holidays, everybody has different days of the week that they’re unavailable. I mean even the concept of a weekend is different. There are people who are definitely off on Sundays and definitely off on Saturdays and definitely off on Fridays. And that means there are also people who start their week on Sunday and people who start their week on Monday. I’m not sure of anybody who starts their week on Tuesday, well me occasionally, and people who work at country clubs in the US, but it means that there’s always something happening and things are moving forward.

Abha:
Absolutely. It’s the idea that there is constantly something that you can get involved with and moving forward. And if you’ve not had a go yet, give it a go. You can join people all over the world and you can definitely do that here with us at the WordPress way. Thank you for joining us today for this and I hope you’ve found out some more about 6.6. Hope it’s made you really want to go and try it. We’re already working on 6.7 and what we’re going to be doing for Do The Woo. So as usual, please send us your items for what you’d like to see highlighted, how you would like to get involved, that you’ll want to know more about. And the joy we’ve had at Do the Woo is putting people in touch with the various groups, the squad that they need to talk to.


And it’s been a real joy when we’ve had that, particularly from the areas where they haven’t had contributors before. So please keep doing that. We are here to support you from Do The Woo. All that remains for me, is really is to thank our two guests, Mary Baum and Meher as well. And it’s just been wonderful to be sitting here talking to you about 6.6. I want to do a shout out to everyone who helped prepare for this as well today and who sent in suggestions and information and of course to Bob who really is an energetic enthusiast for us getting those voices that we don’t always hear and for spreading that international message. So thank you for joining us. Do come and check out 6.7 when it lands later next year, get involved with the 6.7 team and we’ll have all those links on the show notes. But for now, it’s goodbye from me and I’ll let our guests say their farewells too.

Mary:
Well, thank you very much Abha and Bob and Meher, and we’ll catch you on the flip side.

Meher:
Thank you to Abha, thank you to Bob for having us. Thank you to Mary for being with me in this podcast. To all the great publishers out there, go try out 6.6, come be a partner of 6.7.

Abha:
And if you are new and have just discovered these releases, and you actually get involved from what we’ve been trying to put out there, then let us know. We always want to feature things like that and to help encourage. So catch you next time.

Share this episode
Sponsors
Open Makers (archived)