2024-04-10 Weekly Hosting Meeting #230
Closed
Crixu
started this conversation in
Weekly Meetings
Replies: 1 comment
-
|
5ftF:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hosting Team meeting agenda 2024-04-10
EXCERPT:
PUBLIC AGENDA URL:
⇾
PUBLIC SUMMARY URL (if needed):
⇾
Agenda
WordPress Community
Hosting Team Time
Open Floor
Meeting
/here [meeting type="hosting"] Who's here to chat about hosting?
👋 A warm welcome to all WordPress hosting enthusiasts! We're here to dive into the exciting world of WordPress hosting and development. Have questions? Looking for more information? Check out Make/Hosting for comprehensive guides and updates.
🥇 Participants in the Five for the Future program, we'd love to recognize your contributions! Please share your WordPress.org username in a thread here 👉
🤗 Newcomers, we're thrilled to have you on board! You are welcome to introduce yourself and share your experience or what you hope to contribute to WordPress. 👉
Agenda
🟢 Here is the agenda for this meeting
[...] Use the agenda above [...]
Would anyone like to add to or change any items on the agenda?
OK, let's get started with the WordPress Community news.
WordPress Community
🟢 WordPress Core news
Please note: WP 6.5.2 is the first minor release for WordPress 6.5. There was a packaging issue and 6.5.1 was never released.
🟢 WordPress Community news
Ok, let's move on to Hosting Team time.
Hosting Team Time!
🟢 WCEU Contributor Day
WordCamp Europe is only 2 months away, and we're going to have an own Hosting Table there again. Currently, we're aiming to have two table leads for two projects we can work on. The first one will be the improvements to the Hosting Tests and the second idea is around bringing Project Bedrock closer to the hosting tests. (More on that in its own section).
For the Hosting Test Runner and Reporter, our goal will be to finalize the work which was done during the CloudFest Hackathon and get it up and running on make.wordpress.org/hosting.
🟢 Project Bedrock Proposal
As already mentioned, above, we want to continue to work on Project Bedrock for an unbiased and objective view on the WordPress hosting landscape and include collected data into the Hosting Test result pages. The initial idea of Project Bedrock was to have something like a form and volunteers to moderate those entries, which can be a long-running process, especially in an ever-evolving landscape.
The new proposal is to have a JSON schema that provides all the details around the hosting companies in a standardized and normalized form to be machine-readable and reusable inside our tools.
@javiercasares started with this already and created an own repo for feedback and collaboration on the schematics itself https://github.com/javiercasares/wordpress-hosting-directory-schema/
I mention some people who have shown interest in this topic: @nullbyte, @liza Bogatyrev, @Crixu.
The main idea is to do the famous
/hosting, but not on WordPress.org but in a section of the team (something like make.wordpress.org/hosting/directory/). In the future, we'll try to move this into the /hosting. ;) For this, three parts are needed.The original idea was for hosting companies to enter the website, fill out a form, and manage everything from WordPress.org. That solution is complex due to the maintenance and the combination and complexity it involves.
The proposed solution has been to create a JSON Schema that allows that file with all the data to be hosted on the provider's sites, like hosting.example.com/wphosting.json, and for this file to comply with a Schema, which limits options and must be validated to work.
Every day this file will be read and processed. There will be an initial general review before the first approval, in which a Hosting Review team (like plugins, themes, and others) validate the information and approve it or request changes through HelpScout, so everything is reflected by email.
Subsequently, as changes are received, the process will be the same… simple changes can be approved almost without review (for example, accepting a new version of PHP at the end-beginning of the year), but if there are URL changes, or in the Terms and Conditions, changes can be requested or there may be a possibility to remove that provider from the list for not complying with the rules.
The plugin has 2 parts.
On one hand, there is the system that reads, processes, and validates the data that comes from the JSON. On the other hand, there is the front-end part that displays the listings of providers/products (this is quite explained in Project Bedrock). It is necessary to define the sorting algorithm that should prevail, for example, on the main page the companies that participate the most in the Five for The Future (not only should this be the value, but the community should have a significant weight when prioritizing).
The other part of the plugin should be the review. If I recall correctly, we currently have the possibility of having something like “future posts”. In this way, we could have the current data published, and, if something changes, create that “future post” with the new data, which must be reviewed. We can copy what is done with plugins.
Validation, messaging, contacts, and the like will be done via HelpScout email. In this way, on the website, we focus on the work of approving or rejecting, but we do not include messaging.
It will be necessary to define a list of rules for why to accept or reject data, and prepare the validation.
For my part, I am trying to finish a minimal version of the JSON Schema that complies, describes, and is basic to, just by reading the file, without reading the documentation, understand. Additionally, the idea is to create a tool that validates the URL and detects possible errors, and another that allows reading an existing file and modifying it or generating a new file through a form.
BTW: props to @luciaalcantara for helping with the JSON Schema.
🟢 More Hosting Team topics
🟩 Meeting Times
We finally found the issue with the hosting meetings not appearing on make.wordpress.org/meetings and they should show up there again.
Next meetings:
🟩 Open Floor
Ok, if nothing else, let's move on to the Open Floor. You are welcome to bring any topic up for discussion at this time.
...
Goodbye
That wraps up today's meeting. Please keep in mind, our discussions can continue in the #hosting Slack channel or on Make/Hosting anytime.
I hope you have a wonderful rest of your week! [/meeting]
Beta Was this translation helpful? Give feedback.
All reactions