Josepha 2:29 pm on February 27, 2020
Tags: make.wordpress.org/updates ( 10 ), p2-xpost ( 23 )

X-post: Daylight Saving Time Meeting Planning

X-comment from +make.wordpress.org/updates: Comment on Daylight Saving Time Meeting Planning

Corey McKrill 9:53 pm on February 17, 2020
Tags: ticket-scrub ( 26 ), wordcamp ( 36 )

Next WordCamp.org ticket scrub on February 20th, 2020

This ticket scrub will happen on 2020-02-20 18:00 UTC in the #meta-wordcamp channel.

The focus is on MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. tickets with the WordCamp Site & Plugins component.

Comment below if there’s a specific ticket or topic you’d like to discuss.

+make.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//community

#wordcamp #ticket-scrub

Valentin Bora 11:38 pm on February 12, 2020
Tags: meeting ( 5 ), meeting notes ( 10 ), meta ( 27 )

Meta chat summary: February 12th, 2020

Refresher: What’s MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. responsible for?

The Meta team makes 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/, provides support, and builds tools for use by all the contributor groups. If you want to help make WordPress.org better, sign up for updates from the Meta blog.

Attendance

@tellyworth, @sergey, @valentinbora, @clorith, @poena

Facilitator: @tellyworth

Note taker: @valentinbora

Actionable points

@dufresnesteven local dev setup process and identifying missing components
@tellyworth to clarify who’s to take a fresher and more complete dump of the live database (pruned and sanitized) for easier local setups
@tellyworth to reach out for advice on marketing ourselves better to new contributors
@valentinbora to march forward on tickets #5017, #5018, #5015, #5008
@clorith to further specify how to optimize the relationship with meta committers

Next meeting

Thursday, February 26, 2020, 22:00 (see all #meta meetings here)

Topic: Contributing to Meta

@valentinbora mentioned he found it very gratifying to work on Meta due to changes potentially going live faster than with CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., and wanted to find out whether new contributors could be encouraged to consider joining the effort

@sergey shared an interesting WordPress.tv talk he liked on the topic

@tellyworth went on to say that the Meta dev environment is a bit difficult to set up and would like to see the barrier for entry lowered.

@valentinbora confirmed that was the case but not as difficult as it looked at first sight. He suggested simply improving the documentation first, while working on a more fully-blown means of local setup

@poena mentioned they had a theme triage earlier and the attendees didn’t know what the meta environment was or what the Meta team was responsible with

@valentinbora stressed out the goals to be lowering the barrier to entry and increasing motivation for new contributors to join

Topic: Tickets requiring attention

@tellyworth mentioned a decrease in the overall number of Meta tickets, which is commendable

@valentinbora raised awareness to #5017, #5018 and #5015 while emphasizing the last two to cause some friction in the migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. process. See more details about it by checking the Summary for Docs Team Meeting: February 10, 2020

@valentinbora also mentioned #5008 and #5013 to be awaiting feedback from Design

@tellyworth emphasized the Support Forums as being the component with most open tickets and @valentinbora praised @clorith for the helpful Bug Scrub held recently

@clorith stressed the importance of defining a focus area ahead of time for a good scrub in order to avoid getting lost in details and opinions across some of the lengthier tickets

@clorith and @tellyworth agreed that an approach where we’d ask a committer to quickly review and close a well-defined set of tickets would make a lot of sense to improve delivery

Transcript

https://wordpress.slack.com/archives/C02QB8GMM/p1581544979268900

#meeting, #meeting-notes

Corey McKrill 10:31 pm on February 10, 2020
Tags: wordcamp ( 36 )

Ending support for the standalone version of CampTix

CampTix is the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party used on WordCamp.org sites to sell tickets to WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. events and manage attendee data. Since 2012, when it was first built, it has also been distributed as a standalone plugin in 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/ plugin directory.

WordCamp.org has always run the same CampTix code as that found in the plugin directory. A few months ago, however, it was necessary to add some functionality from other parts of the WordCamp codebase into CampTix. Copying that functionality into the standalone plugin would have created confusing duplication on WordCamp sites, and added a lot of complexity to the update. Instead, CampTix was integrated into the WordCamp.org codebase itself, which essentially created a fork. Since then, the WordCamp version of CampTix has changed in ways that have not been ported back to the standalone version.

As of now, the standalone version of CampTix will no longer be distributed via the plugin directory, and its original GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ repo has been switched to “archive” mode.

Continue reading →

#wordcamp

Kelly Dwan 11:50 pm on February 7, 2020

WordCamp.org session timestamp changes

On WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. sites, the session times have been saved as a unix timestamp in UTC, regardless of the site’s timezone. We’ll be fixing this across all WordCamp sites, but this requires changing the session time for all sessions on all sites to include the timezone offset. This should not affect organizers or attendees, but anyone using the timestamp directly from the 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. will see a change.

You can see how we’re fixing this on GitHub, and if you have any input, please leave a reply. There was also some discussion on slack.

What’s the problem?

We were saving timestamps as if they were in UTC, regardless of the site’s timezone, which lead to technically-incorrect timestamps.

For example, if you have a site in EST, and you save a session for March 1st at 4pm, it will actually save it as “March 1st 2020 16:00 UTC”, which is not actually when that talk is. In most places this has been fine, because php’s date also assumed UTC, but as of WordPress 5.3, we have timezone-aware date functions. Additionally, these timestamps are causing headaches for using these values outside of PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php., like in JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. (for gutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/) or 3rd parties developing apps.

Do I need to do anything?

If you’re an organizer, attendee, or someone else who just uses the WordCamp sites, no 👍🏻

If you have an app that uses the WordCamp REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. to get session info (including the time), you might need to update your code.

For apps using the the v1 endpoint still, ex wp-json/posts/?type=wcb_session, the legacy timestamp will still be returned (but please update to v2 😉).

For the current endpoints (ex wp-json/wp/v2/sessions), the meta._wcpt_session_time value will now be the correct timestamp. If you’re manually calculating a timezone offset to display the “right” time, you can remove that code. If you can’t change right away, add ?wc_session_utc=true to your requests, and it will return the legacy timestamp.

I want to run the script to convert these times ~~next week (Feb 12th),~~ Feb 18th and these values will change immediately. You can add the legacy query to your request now, and it will not do anything until the change is made.