For a while, I’ve tried to come up with newsletter styles / grouped news posts. The problem is that it never felt quite right to issue one without waiting for another’s piece of news, and then another, etc.
So scratch that. I’m back to posting tidbits of news whenever they come up.
And here you have it: b2evo 6.10.1 (stable) has been released. Release notes here. You can download it or auto-upgrade it. We are using it on this site and a handful of others. It’s proven stable already.
The reason we released 6.10.x and not 7.0.x is the infamous GDPR. (Do you enjoy all the GDPR related emails you get these days?)
b2evo 6.10.1 goes a long way toward GDPR compliance. I’m not saying 100% here because this regulation is very deep and we won’t know for a while if we finally hit the bottom or not. One thing for sure, the FUD around it is even worse as with the previous cookie regulations. Anyways, if you find something that’s “not GDPR enough” in your opinion, please let us know and we’ll address it.
Ironically, the other big thing in 6.10 is mailing lists & automations. It’s loaded with super powerful features but we haven’t quite finished the doc yet. So I’ll get back to you on that later. For now, let’s just say it plays super nice with user preferences and easy unsubscribe and it is GDPR compatible ;) … but more on this later…
Last week, I shared my State of Drupal presentation at Drupalcon Nashville. In addition to sharing my slides, I wanted to provide more information on how you can participate in the various initiatives presented in my keynote, such as growing Drupal adoption or evolving our community values and principles.
Drupal 8 update
During the first portion of my presentation, I provided an overview of Drupal 8 updates. Last month, the Drupal community celebrated an important milestone with the successful release of Drupal 8.5, which ships with improved features for content creators, site builders, and developers.
Drupal 8 continues to gain momentum, as the number of Drupal 8 sites has grown 51 percent year-over-year:
This graph depicts the number of Drupal 8 sites built since April 2015. Last year there were 159,000 sites and this year there are 241,000 sites, representing a 51% increase year-over-year.
Drupal 8's module ecosystem is also maturing quickly, as 81 percent more Drupal 8 modules have become stable in the past year:
This graph depicts the number of modules now stable since January 2016. This time last year there were 1,028 stable projects and this year there are 1,860 stable projects, representing an 81% increase year-over-year.
As you can see from the Drupal 8 roadmap, improving the ease of use for content creators remains our top priority:
This roadmap depicts Drupal 8.5, 8.6, and 8.7+, along with a column for "wishlist" items that are not yet formally slotted. The contents of this roadmap can be found at https://www.drupal.org/core/roadmap.
Four ways to grow Drupal adoption
Drupal 8 was released at the end of 2015, which means our community has had over two years of real-world experience with Drupal 8. It was time to take a step back and assess additional growth initiatives based on what we have learned so far.
In an effort to better understand the biggest hurdles facing Drupal adoption, we interviewed over 150 individuals around the world that hold different roles within the community. We talked to Drupal front-end and back-end developers, contributors, trainers, agency owners, vendors that sell Drupal to customers, end users, and more. Based on their feedback, we established four goals to help accelerate Drupal adoption.
To become involved with one of these initiatives, click on its "Issue link" in the table above. This will take you to Drupal.org, where you can contribute by sharing your ideas or lending your expertise to move an initiative forward.
Goal 2: Improve the content creator experience
Throughout the interview process, it became clear that ease of use is a feature now expected of all technology. For Drupal, this means improving the content creator experience through a modern administration user interface, drag-and-drop media management and page building, and improved site preview functionality.
Most of these initiative teams meet weekly on Drupal Slack (see the meetings calendar), which gives community members an opportunity to meet team members, receive information on current goals and priorities, and volunteer to contribute code, testing, design, communications, and more.
Goal 3: Improve the site builder experience
Our research also showed that to improve the site builder experience, we should focus on improving the three following areas:
The configuration management capabilities in core need to support more common use cases out-of-the-box.
Composer and Drupal core should be better integrated to empower site builders to manage dependencies and keep Drupal sites up-to-date.
We should provide a longer grace period between required core updates so development teams have more time to prepare, test, and upgrade their Drupal sites after each new minor Drupal release.
We plan to make all of these aspects easier for site builders through the following initiatives:
Core committers + Drupal Security Team + Drupal Association
Core committers and Security team
Proposed, under discussion
Goal 4: Promote Drupal to non-technical decision makers
The fourth initiative is unique as it will help our community to better communicate the value of Drupal to the non-technical decision makers. Today, marketing executives and content creators often influence the decision behind what CMS an organization will use. However, many of these individuals are not familiar with Drupal or are discouraged by the misconception that Drupal is primarily for developers.
With these challenges in mind, the Drupal Association has launched the Promote Drupal Initiative. This initiative will include building stronger marketing and branding, demos, events, and public relations resources that digital agencies and local associations can use to promote Drupal. The Drupal Association has set a goal of fundraising $100,000 to support this initiative, including the hiring of a marketing coordinator.
Megan Sanicki and her team have already raised $54,000 from over 30 agencies and 5 individual sponsors in only 4 days. Clearly this initiative resonates with Drupal agencies. Please consider how you or your organization can contribute.
Fostering community with values and principles
This year at DrupalCon Nashville, over 3,000 people traveled to the Music City to collaborate, learn, and connect with one another. It's at events like DrupalCon where the impact of our community becomes tangible for many. It also serves as an important reminder that while Drupal has grown a great deal since the early days, the work needed to scale our community is never done.
An overview of Drupal's values with supporting principles.
I believe that taking time to highlight community members that exemplify each principle can make the proposed framework more accessible. That is why it was very meaningful for me to spotlight three Drupal community members that demonstrate these principles.
Principle 1: Optimize for Impact - Rebecca Pilcher
Rebecca shares a remarkable story about Drupal's impact on her Type 1 diabetes diagnosis:
Principle 5: Everyone has something to contribute - Mike Lamb
Mike explains why Pfizer contributes millions to Drupal:
Principle 6: Choose to Lead - Mark Conroy
Mark tells the story of his own Drupal journey, and how his experience inspired him to help other community members:
These updated plugins also contain new features and bug fixes as well. Please visit the download page of the specific plugin to find out more information. The plugins above can also be found on Github in our Geeklog Plugins Repository.
Note: Older 3rd party Geeklog plugins may not support Geeklog v2.2.0 because they use out dated functions to create a web page. The functions COM_siteHeader and COM_siteFooter have been depreciated and now developers are required to use the function COM_createHTMLDocument to create a web page.
Developers if you have a plugin which supports Geeklog v2.2.0 which has not been included in the list above please comment on this article to give us more information, and we will add it in. Remember you can also submit an article (and upload the file) about your plugin and after review (and editing if required) we will post it on Geeklog.net.
Despite project close announcement one and a half years ago, some enthusiastic Japanese developers and users have been maintaining Nucleus CMS core. And today, we are pleased to announce Nucleus CMS 3.70. This is a direct descent of the original Nucleus CMS, supports the same multiple languages. Major fixes and improvements in this release are including (but not limited to) the following:
Enforced password security using phpass library instead of md5 hash
Default character code set is now utf-8, not iso8859-1
Added new event PreLoadMainLibs
Upcoming version 3.71 is pre-released in Japanese as well. New features in 3.71 are:
You are always welcome to post suggestions and questions for Nucleus CMS in the same old English support forum. Also, all the core and major plugins are now maintained on GitHub. Please feel free to submit issues and of course pull requests.
The student application deadline is coming up fast, but you still have two more days to submit or finalize a proposal! We're actively standing by to assist anyone having trouble, so please reach out to our team. The best way to do that is via IRC.
Five Nights at Freddy's 4 Full Version - Feel the fear one last time
Five Nights at Freddy's 4 is the fourth, and last (supposedly) release in the Five Nights at Freddy's saga. Developed and published by Scott Cawthon, this horror game has delighted all the fans of horror games, and has also raised the criticism from those that say that there are too many FNaF games. This time, you are not a security guard fighting for your life against creepy animatronics. Instead, you are a defenseless kid who struggles every night because of his terrifying nightmares (nightmares about creepy animatronics, of course).
Now, animatronics don't kill you, because they are just nightmares, but they can scare you as they have done since forever. Freddy, Bonnie, Chica, and Foxy have come back, and they have brought new nightmare friends with them. Also, the location is not an office anymore. It takes place in your own room, a room with a bed, two doors, and a dark closet. Each part of the room is dangerous since they are places where the animatronics can hide.
Moreover, the mechanics of the game have significantly changed compared to the previous tree installments in the saga. Now, you do not depend on your vision, or the cameras, because in this release, you don't have them. Now, you have to hear; you have to pay attention to every sound, breath, and laugh, because sound indicates where enemies will come from. It's recommended to play with earphones or with a very high volume. You are free to play with a regular sound volume, but you will not be able to hear your enemies.
Are you ready to say goodbye to your beloved animatronics?
As mentioned, the mechanics have changed. Now, you have nothing more than your senses and a flashlight to defend yourself. You have to control both doors, the closet, and the bed behind you. Animatronics can appear in any of the four places. What you have to do is walk bravely to the doors and the closet, listen carefully and if you hear something, close the door as fast as you can and hold it shut until the sound disappears. In case you don't hear anything, use the flashlight to prevent enemies from coming. The bed at your back has a little Freddy fluffy toy, but sometimes dreadful miniature Freddy's appear, followed by Nightmare Freddy himself. You have to shoo them with the flashlight unless you want Freddy to appear. It can seem easy, but the slightest mistake (using the flashlight when you hear a breath, or not closing the doors in time), will bring an end to the game.
Freddy, Bonnie, Chica, and Foxy have come back, and they have brought new nightmare friends with them
Talking about your friends the animatronics, when you download FNaF4, you will have to face six of them, eight if you take into account the "nonofficial" ones. You already know Freddy, Bonnie, Chica, and Foxy (nightmare version) but let me introduce you to Nightmare FredBear and Nightmare (plainly). All the animatronics in nightmare version are decrepit, broken, and especially scary. They have very long sharp teeth and glowing eyes, but Nightmare FredBear and Nightmare have even longer teeth, and they are very dangerous because they are unpredictable. This is especially true of Nightmare, since he is black and semi-transparent. They start appearing on nights 5 and 7, respectively.
In this version, you can check out the main features of Five Nights at Freddy's 4:
A new story that reveals what happened in the Bite of the 87
A gloomy mini-game that allows you to skip the first two hours of the nights (if you are successful)
Nightmare version of the old and well-known animatronics (Bonnie, Freddy, Chica and Foxy)
4 new animatronics: Nightmare, Nightmare FredBear, Plushtrap and Nightmare Cupcake (Chica's cupcake can attack you know)
This month saw two significant milestones in the WordPress community — the 15th anniversary of the project, and GDPR-related privacy tools coming to WordPress Core. Read on to find out more about this and everything else that happened in the WordPress community in May. Local Communities Celebrate the 15th Anniversary of WordPress Last Sunday, May […]