PHP Meeting Recap – January 22nd

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

This recap is a summary of our previous PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher meeting. It highlights the ideas and decisions which came up during that meeting, both as a means of documenting and to provide a quick overview for those who were unable to attend.

You can find this meeting’s chat log here.

Chat Summary

The #design team has acknowledged our call for design help for servehappy and added a corresponding task in their Trello board. @jaymanpandya has stepped forward and was assigned this task.
We summarized again how we’re envisioning the site:
- stand-alone design, as including it into the wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ page design would reduce the impact and hinder proper optimization;
- targeting site owners, with the option to make the content adapt to URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org parameters for more precise targeting;
- focused on easy consumption and avoiding overwhelm, with additional, more detailed content available as needed;
- hosted on wordpress.org infrastructure and showing a small mention to the wordpress.org project;
- not collecting usage data or feedback through the site, as that will likely get vetoed.
@jaymanpandya is an experienced UXUX User experience designer and will work on a first set of mockups so that we can get a feel for how this might work as a real site.

Next week’s meeting

Next meeting will take place on Monday, January 29, 2018 at 16:00 UTC in #core-php.
Agenda: Discuss UX mockups and hosting situation.
If you have suggestions about this but cannot make the meeting, please leave a comment on this post so that we can take them into account.

#core-php, #php, #servehappy, #summary

Andrew Ozz 3:22 pm on January 29, 2018
I’m probably missing something (been away for some time), but I still don’t understand what’s the purpose of a `servehappy` site.

Who is this site targeted at?
- The servehappy name suggests it’s targeted at hosting companies, although I doubt it that is the intention.
- If it is targeted at “all PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher users”, wouldn’t it be better to be hosted at php.net? It will sound/feel a lot more legitimate there.
- If it is targeted at WordPress users, does it make sense to have external site instead of utilize the current APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. and deliver the right information directly to the users? I mean, the site cannot work without additional information; we don’t want to require the users to submit that information; all needed information is already available when using the wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ API.
Looking at the analogy with browsehappy, servehappy will be nothing like it. It won’t work for “visitors” as they will have to submit additional information that they typically don’t have, like the PHP version their site is running on, if they have a site and it uses PHP. For comparison browsehappy can be used by “everybody” and everybody knows what a web browser is 🙂

This is intended to help the WordPress users in switching their site(s) to newer PHP versions. Imho concentrating on wordpress.org API driven approach is the right way to go, creating an external site that requires somewhat sensitive information in order to work is probably not.

In that terms I’d like to propose another point to the agenda for 29 January: revisit the decision of creating an external site and its overall usefulness if the users don’t submit any data.
adrianhead1 8:39 pm on January 30, 2018

I have a question. All this seems to be aimed at website owners but what about the hosting companies? Some are very slow to update to the most recent PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher version. There seems little point in recommending upgrading to the most recent PHP version available if the hosting company is not able to offer this.

Would it not be also appropriate to include hosting company notifications somewhere in this proposal?

Comments are closed.

Welcome!

Communication

Chat Summary

Next week’s meeting

Share this: