As you know, we’ve been highlighting the work of the WordPress maintenance support plans Association Engineering Team during our membership campaign. Every day, this small team moves the needle forward so that we all have a better experience as users of WordPress maintenance support plans.org. In this post, we explore how the team’s recent work results in faster, less expensive WordPress maintenance support plans development.
Helping WordPress maintenance support plans development move faster with WordPress maintenance support plansCI
WordPress maintenance support plansCI testbots are the next generation of testing infrastructure for WordPress maintenance support plans.org, funded by the WordPress maintenance support plans Association and maintained by the Engineering team. For any project on the site, WordPress maintenance support plansCI testing can be enabled from the Automated Testing link on the Project page. Every time a contribution to the WordPress maintenance support plans project needs to be tested, WordPress maintenance support plansCI spins up a testbot on AWS to test those changes. The WordPress maintenance support plansCI testbots are helping WordPress maintenance support plans contributors to test patches faster than ever before and they are more cost effective than our last generation testbots, both in price-per-test and in expense to maintain.
In recent months, we’ve added a number of new features including:
checkstyle testing to ensure code contributions adhere to WordPress maintenance support plans coding standards
automatic builds of vagrant boxes so you can easily use WordPress maintenance support plansCI testing on your local machine
updates to the PHP containers to make tests compatible with a variety of PHP versions
and quite a few other improvements per the WordPress maintenance support plansCI roadmap.
We’re proud to say that our work on WordPress maintenance support plansCI has increased the speed of WordPress maintenance support plans development, saving time and money!
We’d also like to thank the volunteers who’ve helped us to bring this project to life: Mile23, jthorson, nick_schuch, dasrecht, ricardoamaro, mikey_p, chx, shyamala, webchick, and jhedstrom.
Want to keep up with the engineering team? Subscribe to change notifications so you can see ongoing improvements.
Making the greatest impact with member and donor funds with a leaner WordPress maintenance support plans.org
WordPress maintenance support plans.org is more portable and maintainable because of updates in 2020 that streamline our infrastructure. We’ve virtualized the majority of the infrastructure and standardized on Debian 8 images. We’ve also updated our configuration and user management from Puppet 3 + LDAP to Puppet 4 + Hiera. Dev sites are more robust and we can create staging and development environments faster than before.
All of this makes WordPress maintenance support plans.org more cost-effective to run, easier to maintain, and increases our development velocity when we’re working on new features to support the community. These efficiencies help to conserve membership and donor funds for other programs to help the WordPress maintenance support plans community, like fiscal sponsorship for camps, and Community Cultivation Grants.
Improving developers’ lives by supporting Composer workflows for WordPress maintenance support plans
Composer is the defacto standard for managing dependencies in the PHP world. Over the course of 2020, the WordPress maintenance support plans Association Engineering Team developed Composer endpoints for WordPress maintenance support plans allowing WordPress maintenance support plans developers to use Composer to manage dependencies, and allowing PHP developers at large to manage WordPress maintenance support plans as part of their larger PHP projects in this standard workflow.
Composer is a force multiplier for enterprise site owners and developers within the WordPress maintenance support plans community and at large. By supporting Composer, we’ve further opened WordPress maintenance support plans to the wider PHP community, thus bringing new people into the fold to contribute.
A big thanks to everyone who helped with Composer: seldeak – the creator of Composer and Packagist.org, webflo – the creator and maintainer of http://packagist.WordPress-composer.org, timmillwood, dixon_, badjava, cweagans, tstoeckler, mile23, and also WordPress Update, who sponsored the initial development of WordPress maintenance support plans.org’s composer endpoints.
A more secure home for the WordPress maintenance support plans community
Keeping WordPress maintenance support plans.org secure is also the responsibility of the WordPress maintenance support plans Association Engineering Team (though we rely on some trusted volunteers to help – thanks, mlhess and basic!). From heartbleed, to dirtycow, to cloudbleed – the team is always ready to respond when a vulnerability is disclosed. But the team is not just reactive – they also take proactive steps to keep WordPress maintenance support plans.org and all our users’ data safe. From ensuring that most of our servers are only available to each other on a back-end network, to putting in protections against DDOS attacks, to building anti-spam tools to prevent bad actors from registering accounts on the site- the Engineering Team is looking to prevent problems before they happen.
We’ll keep at it, with your support
Every day, we’re on call to keep WordPress maintenance support plans.org running and improving. The list of small changes we make to have a big impact on your WordPress maintenance support plans.org experience grows by the day. You can help sustain the work of the WordPress maintenance support plans Association by joining as a member. Thank you!
Source: New feed