On Wednesday, May 15, 2024 at 0900 UTC we had the Hosting Meeting, and this is a summary of that conversation focused on the WordPress Hosting Directory Project.
Slack conversation.
Participants: @javiercasares, @ashiquzzaman, @zunaid321, @kirasong, @Crixu, @justlevine, @markoheijnen, @ipajen.
Summary of WordPress Hosting Directory Project
The Basics
The WordPress Hosting Directory project aims to provide a comprehensive, objective, and community-driven resource for selecting WordPress hosting services. By leveraging both technical criteria and community contributions, the directory will support informed decision-making for users while fostering greater transparency and collaboration within the WordPress ecosystem. The project welcomes community involvement and feedback to ensure its success and relevance.
Overview
The WordPress Hosting Team discussed the proposal for the “WordPress Hosting Directory” project. The goal is to create a directory to help users choose hosting services based on objective criteria such as technical features, proximity, and community contributions. This directory aims to be a reliable resource for WordPress users, supporting informed decision-making for their hosting needs.
Key Discussion Points
- Project Background and Goals
- The project has evolved from previous proposals and initiatives, such as the WordPress.org Recommended Hosts Page Requirement Matrix Criteria, Project Bedrock, and Hosting Application Rubric.
- The directory will feature extensive filtering options, including hosting type (shared, VPS, cloud), WP-CLI access, and server energy types, among others, totaling over 50 variables.
- Community and Technical Contributions
- The directory will also highlight hosting providers’ contributions to the WordPress community, incorporating elements like Five for the Future (5ftF) commitments.
- An example project similar in spirit is Yoast’s WordPress Hosting overview.
- Hosting (Data) Review Team
- A new Hosting Review Team will be formed to oversee and validate the data submitted by hosting providers.
- The review process will likely involve initial private reviews to resolve sensitive issues before making data public on platforms like GitHub.
- Transparency is a key aim, but balancing it with privacy and sensitivity is essential to avoid conflicts and misinformation.
- Process and Workflow
- Initial reviews may be conducted privately to iron out issues before public disclosure.
- Discussions suggested mimicking successful practices from the Plugins Review Team and Themes Review Team as well as the vetting process currently in place for WordCamp sponsoring.
- Public transparency is preferred, but sensitive initial discussions may be necessary to maintain quality and avoid conflicts.
- Technical Implementation
- The JSON Schema for hosting providers’ data has been drafted, and a sample JSON is available for reference.
- A tool for generating JSON files is under development, inviting contributions from developers and hosting providers.
- Next Steps
- Discussions and work planned for WordCamp Europe 2024 Contributor Day.
- Refining the JSON Schema and creating the initial version of the directory plugin.
- Collecting and reviewing the first JSON submissions from hosting providers.
- Publishing the directory plugin and website.
- Expanding the review team and scaling the process globally.
Concerns and Challenges
- Public vs. Private Reviews
- Balancing public transparency with the need for private initial reviews to handle sensitive issues.
- Concerns about public conflicts and misinformation were raised, suggesting initial private handling before public release.
- Vetting and Compliance
- Ensuring hosters comply with community standards and technical requirements.
- Developing a rubric to assess community contributions and technical reliability.
- Addressing concerns about subjectivity in vetting processes, especially around values and historical brand perception.
- Technical and Community Integration
- Creating a seamless process for hosters to submit and update their data.
- Leveraging community input to refine and improve the directory over time.
Community Engagement
- Encouraging participation from developers, hosting providers, and community members.
- Inviting feedback on the JSON Schema and contributions to the plugin development.
- Emphasizing the importance of community feedback and transparency throughout the project.