Tide Chat Agenda: May 1st

This is the agenda for the weekly Tide meeting on May 1, 2018 at 21:00 UTC / May 1, 2018 at 21:00 UTC:

GCP migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies.
Roadmap wishlist
General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#agenda, #tide-chat

Ulrich 9:28 pm on May 1, 2018

As I offered to lead the Tide team at WCEU contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. Milana messages me the following request.

We want to publish detailed article for each team and we think that it would be extremely helpful to include specific goals each team has for this particular Contributor Day. This doesn’t have to be long or even publish-ready (we’ll take care of it). Just a few items on the current most urgent todo list.

Could we discuss this?
- Jeffrey Paul 3:33 am on May 2, 2018
  
  @ulrich for now, the best course for contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. may be getting people familiar with WPCS and PHPCompatibility. Potentially getting folks setup to run their own code through WPCSWPCS The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the WordPress Coding Standards.
  May also be an acronym referring to the Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook. and PHPCompat to see where they can improve things. If they’re more evolved than that, potentially having folks look at contributing to WPCS issues or PHPCompat issues.
  
  Are there other areas from your vantage point that may be worthwhile as well?
  - jrf 8:41 am on May 2, 2018
    
    FYI: there will also be a WPCSWPCS The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the WordPress Coding Standards.
    May also be an acronym referring to the Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook. table at WCEU. It might be advantageous to see if these tables can be at least in the same room (if there are several rooms) and if it’s all one big room: see if the tables can be physically close together.
    For the “setting up to run phpcsPHP Code Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS./wpcs etc locally” part I expect a large overlap, so it’d be helpful if we can divide and conquer there and not spend to many resources on getting people set up with no resources left to actually do some work.
    The WPCS table has already given their goals etc (see the #code-coding-standards slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel a week or two back).
    - Milana Cap 6:40 pm on May 7, 2018
      
      There will be no rooms. All teams will be in one big room and we’ll make sure to have Tide and WPCSWPCS The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the WordPress Coding Standards.
      May also be an acronym referring to the Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook. next to each other.

Weekly Chats

Share this: