Here’s the summary of our very first meeting in #hosting-community on Wednesday, January 18, 2017 at 1600 UTC (Slack archive).
Purpose
- Kicking things off by restating the purpose of the group.
- Original post on Make Hosting.
- Is the scope of what we’re looking to tackle off?
- Looks fine for now.
- Let’s just fix things as we go.
Ideas
- Hosts should band together and work through things that the core group can never do.
- Come up with solutions for things like:
- Upgrading PHP for non-managed users.
- How we can all generally make WordPress feel and work better for everyone.
- If core needs PHP module X, can we get enough of us on the same page for core to rely on that?
- Come up with solutions for things like:
- Best practices documentation (see: WordPress Hosting Handbook).
- Server setups are going to vary, but there are definitely best practices that we can document.
- Who puts default settings in
wp-config.php? - System plugins.
- Standard “default”
php.inivalues.- Hosts should offer feedback on things like upping default memory limits in core. (#29341)
- Scaling and performance optimizations.
- The REST API and plugins like WooCommerce are changing how people use WordPress.
- Who puts default settings in
- Server setups are going to vary, but there are definitely best practices that we can document.
- Promoting and encouraging WordCamp attendance.
- Hosts are uniquely positioned to promote regional WordCamps to customers.
- WordPress has great brand awareness amongst customers.
- WordCamp? Not so much.
- Knowledge sharing “in your own backyard” is a big draw for some people.
- Can leverage geographical customer data to promote upcoming local camps.
- “As a WordPress user, here’s an event near you that you might find educational and informative that you didn’t even know was a thing!”
- May require support from the #community-events team to help automate it.
- An API would make it easy to tie into.
- Hosts are uniquely positioned to promote regional WordCamps to customers.
- Making sure new features are scalable on implementations of all sizes.
- Testing things at the host level rather than just depending on the automated TravisCI tests that are currently run.
- See: @jorbin’s PUBSUBHUB unit testing idea.
Assignments
- Best Practices Documentation: @voldemortensen, @lukecavanagh, and @aaroncampbell agreed to pitch in where they can.
- Promoting WordCamps: @smaffulli will reach out to events team.
- Distributed Unit Tests: @mikeschroder is reaching out to @jorbin for next steps.
Feedback
Miss the meeting? Interested in helping on one of the initiatives above? Please feel free to drop into the comments and weigh in.
Next Meeting
Our next meeting will be in #hosting-community on Wednesday, January 25, 2017 at 1600 UTC. If that works with your schedule, we’d love it if you could attend. Hope to see more of you next week!