— Kyle Chayka
from The New Yorker
writes about the unusual popularity
. Chayka says Tumblr's "status as a relic of the Internet has attracted prodigal users as well as new ones." The article is behind a paywall of sorts but readable if you create an account.
Chayka covers the early days of Tumblr
and the controversies that have followed it before Automattic
acquired the platform in 2019.
POST STATUS ANALYSIS
WordPress users probably haven’t given much thought to Tumblr and Matt Mullenweg’s plans for it. (The back end likely involves WordPress while “the front-end user experience… will evolve on its own…”) But Tumblr and its user community is a social network of sorts. I don’t think we look at Automattic as owning a social network. Especially one that acts (or doesn’t act) the way others do. As Kyle notes, “There aren’t influencers on Tumblr the way there are on Instagram and TikTok, and the experience for all users might be more pleasant as a result.”
— Robert Jacobi explains
how recent discussions
in Post Status Slack
have involved some faulty comparisons between WordPress
When the idea of a WordPress app store was put forward (not for the first time) as a means of support for open source contributors
, Matt Mullenweg
said he is "haunted by what happened to the Joomla
community when they created an official marketplace, seemed like the beginning of the end for them." Robert later responded on his site:
"Joomla has never had an app marketplace, it has had and continues to have an Extensions Directory (same as the WordPress Plugin Directory)."
Robert also believes an open-sourced WordPress.org-sponsored app store isn't the answer to supporting open source contributors, but a solid answer is sorely needed:
"We need to directly support good projects and developers by contributing directly to their livelihoods."
POST STATUS ANALYSIS
Looking at other open-source projects for lessons to learn from and apply to WordPress is a good idea Lesley Sim and others have proposed in this ongoing dialogue. Like Robert Jacobi, a fair number of people working in the WordPress space have been (or still are) involved with Joomla, Drupal, and other projects. Their experiences and observations are worth listening to, and I hope there will be more opportunities for that kind of reflection in the near future.
The Wikipedia history of Joomla is currently written as a story of decline that squares with my memories as a freelancer using Joomla heavily (and then less and less) from 2005-12. While there was never a single “Benevolent Dictator for Life” leading the Joomla project — there were over two dozen co-founders! — there was a small core group and one co-founder in particular who stood out as first among equals. They were the closest Joomla came to having a BDFL. These individuals led Joomla in its early, very successful years. They exited the project as they came into conflict with Open Source Matters, the foundation providing legal, organizational, and financial governance for the project.
The name “Joomla” is derived from a Swahili word, “jumla,” whose meaning was thematic for the Joomla community: “all together as a whole.” But that is precisely where the project seemed to founder. Organizational rather than technical failures seem to be regarded more commonly now as having had a great deal to do with Joomla’s rapid decline.
— Dan Knauss
— There are more details
coming out after the White House meeting on open source security concerns triggered by the recent log4j
asked for "a list of critical open source projects," which has already begun to be assembled using a "criticality score
" under the auspices of the OpenSSF
, which is a past recipient of $100 Million in donations from Google.
, president of global affairs at Google and Alphabet
also proposed creating an organization
to serve as a marketplace for open source maintenance with the following rationale:
"Open source software is a connective tissue for much of the online world — it deserves the same focus and funding we give to our roads and bridges."
POST STATUS ANALYSIS
In attendance at the White House Open Source Cybersecurity meeting: Apache, Google, Apple, Amazon, IBM, Microsoft, Meta, Linux, and Oracle.
Not invited: WordPress, powering 40% of the top million websites, including whitehouse.gov.
WordPress and many plugins in the WordPress ecosystem have been ranked in the top 200 most critical PHP projects, however.
Currently, WooCommerce ranks 13th out of 200 projects in criticality with a score of 0.8. Jetpack follows at 17th (0.78). Yoast SEO is #27 (0.75), WordPress is #42 (0.726), and the Google AMP plugin for WordPress is #44 (0.721).
It’s unclear if these scores and rankings are based solely on GitHub data, but in the case of WordPress, this seems to be the case — data from Trac is excluded from the calculated score.
The criticality score runs from 0 to 1 “and is derived from various project usage metrics in a fully automated way.” (The algorithm is explained in the OSSF score repo.) Those metrics include:
“a project’s age, number of individual contributors and organizations involved, user involvement (in terms of new issue requests and updates), and a rough estimate of its dependencies using commit mentions.”
It is also possible for open source projects to add their own internal metrics “to re-adjust a project’s criticality score for individualized prioritization needs.”
Currently, WordPress and other open-source projects, many of which belong to the WordPress ecosystem, do not have a seat at the table with the big tech companies that are determining the course of industry “self-regulation.” Clearly, that needs to change.
— Dan Knauss
— Fences can protect or inhibit care of a commons. "Do not remove a fence until you know why it was put up in the first place," is a classic piece of wisdom. What are the questions we need to ask about our fences and WordPress as a commons?
— How can WordPress attract and retain more contributors? How can we assess and improve contributors, leaders, governance, transparency, discourse, and diversity in this dynamic community? Jordi Cabot proposes making research into these areas as a part of WordPress.org's Five for the Future program.
— This week the WordPress.com
team announced early access to Full Site Editing
(Beta) for all new sites created by "existing English-speaking users."
developer Brent Roose
explains how he deals with dependencies
that won't support the latest PHP version you're upgrading to. Start testing early, submit a pull request if you can fix the issue in PHP yourself, and reach out to the maintainers. Sometimes you need to start looking for alternatives or fork the library in question.
— Iain Poulson
has an extensive guide for installing WordPress in a subdirectory
. Iain goes beyond installing and managing subdirectory installs to moving an existing site out of or into a subdirectory.
— Sometimes we forget some of the more creative real-world scenarios that WordPress and WooCommerce
can help with. Rodolfo Melogli
shares how Woo can help restaurants sell to customers online
. With a few plugins, they can "offer a comfortable and fast order and checkout process for customers and eliminate the need to pay a major chunk of their hard-earned money to third-party services."
— Big news on the WooCommerce front! For devs worldwide, there was this huge sigh of relief as Woo announced they are starting to work on an implementation of custom tables for orders
. How huge is this? Huge, huge! It has been in the minds and on the radar of devs for some time. Many are applauding the efforts on Twitter and anticipating this large improvement.
It's a complex update, so WooCommerce
will be wanting feedback. In the meantime, Zach Stepek
, Carl Alexander
, and Till Krüss
will be taking a deep dive into the topic
on the Do the Woo
podcast on February 1st.
In other news, WooCommerce 6.2.0 Beta 1 was released
with the final release date coming up on February 8.
— Brad Williams
and Lisa Sabin-Wilson outline goals and resolutions
in 2022. They say it's critical to keep up with industry trends, so they will be keeping an eye on "Web3," headless, and experimenting with new marketing channels like Twitter Spaces
— If you love fun CSS
certainly fits that definition. It allows you to apply "inflated fluffy 3D claymorphism styles" to elements.
— Courtney Robertson
shares the WordPress Training Team's 2022 goals
— the team "will empower users to achieve their goals with WordPress through actionable and practical learning experiences."
The milestone section mentions a "discovery phase for official WordPress.org certification" near the end of 2022.
— Ari Stathopoulos
confirms that WordPress 5.9
will be enhancing the block editor to allow multiple stylesheets to be registered
for each block. Blocks will also be able to load styles from other blocks when needed.
— Kate Kalcevich
says there are three ways to increase your digital accessibility capacity:
The best option is probably the second one:
Decentralizing accessibility throughout the team is one of the most sustainable and impactful ways to increase accessibility in your digital products.