Preparing for Contributor Day at WCUS 2023

WordCamp US 2023 will be holding a 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/. on August 24, 2023 at the Gaylord National Resort & Convention Center in National Harbor, Maryland, USA. This is a perfect opportunity to attend Contributor Day on August 24, 2023 and join the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. table in person or online on 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/..

🕰️ New contributor orientation will begin at 8:30 AM at 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. US. Returning contributors are invited to join at 9:30 AM.

If you are wanting to join in remotely and work on tickets, WordCamp US is welcoming remote contributors from 10:00 AM. Information on Contributor Day can be found on the Make WordPress Slack channel:

How to prepare to be productive at Contributor Day

In advance of the Contributor Day, it is recommended that contributors:

  • Create WordPress account and join the Make WordPress Slack – some help information is available on Learn.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/
  • Prepare the local environment
  • And don’t be afraid that someone will take your ticketticket Created for both bug reports and feature development on the bug tracker. and solve it first, there are more than 8,000 tickets. There are plenty of choices for everyone, and opportunities to collaborate with others. For example, open your new WordPress 6.3 and find the Get Involved tab of the About page. The number of people who worked on this one is around 50.

For more information, see the previous and more detailed post on this topic prepared by Abha Thakor, Jonathan Desrosiers and other contributors to the Core Team.

💡 If you have wished to contribute to WordPress Core, but were not sure how to begin and were telling yourself: “Oh, well, possibly next time”, then this could be your time to get involved. Join the core tables in person or remotely, and seasoned contributors will help you start enjoying working with the code. It is poetry!

Beyond the code there are many different ways to contribute. Follow the links below for the Core-Test team and the Core-Performance team, which will be at WordCamp US Contributor Day. Details of other Core teams at WCUS are being finalized and will be linked from this post.

Thank you to @oglekler, @webcommsat, @marybaum, @desrosj, and all that contributed content and resources linked from this post.

#contributor-day, #wordcamp-us

WP Feature Notifications at WordCamp Europe Contributor Day

The WP Feature Notifications project will be at 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. Europe 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/., led by @sephsekla. We are a small, focused team, and always on the lookout for new contributors, so we would encourage anyone to get involved!

WP Feature Notifications is a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins., with a proposal to modernise the way in which WordPress handles emails, adminadmin (and super admin) notices and user notifications. We are working towards the MVPMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia version of a new, centralised system, with both PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher and REST-based APIs.

Contributing

The project has something for everyone, and all new contributors are very welcome!

For developers and other more technical contributors, we have several areas to focus on:

  • In-progress PHP work for the MVP
  • 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/. improvements to make better use of WordPress components
  • A provisional TypeScript rewrite of the JavaScript UIUI User interface

We also have a number of areas to cover which are less technically focused:

  • Testing and feedback on our current proof of concept (version 0.2.0)
  • Feedback and pain points on the current WordPress notices and emails
  • Discussion and ideas for future requirements

No setup ahead of the event or prior knowledge is needed to get involved, but for more technical work we would recommend bringing a laptop with Docker, npm and Composer installed.

Find out more

We look forward to seeing you at the event!

If you’re interested in the project, you can also join the #feature-notifications channel in the Making WordPress Slack or find out more about the project at  https://github.com/WordPress/wp-feature-notifications.

#contributor-day, #feature-notifications

Dev Chat Summary, May 31, 2023

(Update June 6, 2023 – posts on 6.4 and 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/ added to section at the end of this post.)

Notes from the weekly WordPress developers chat which took place in the core channel of Make WordPress Slack. All are welcome.

To read the meeting on 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/. itself, it starts at this link.

1.Welcome and housekeeping

Dev Chat agenda – thanks to @webcommsat for preparing.

Note: The agenda includes information links for releases and some related content to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., especially this and next week to help new contributors to core going 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. Europe. To allow time for more discussions on tickets, all the links may not always be highlighted during the actual dev chat, and attendees are encouraged to check the full link list in the agenda itself.

Thanks to @ironprogrammer for facilitating the meeting.

2. WordPress Announcements 

Details on the latest Gutenberg 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 release: What’s new in Gutenberg 15.9? (31 May).

3. Highlighted posts

6.2 server performance analysis summary from the Core-Performance team.

Celebrating 20 years of WordPress – post by Josepha on May 27, 2023.

Analysis of the results of the individual learner survey from Learn.WordPress.org – posted by @webcommsat. This shares findings of the survey, and presents opportunities for cross-collaboration with Core and other Make teams.

Contributor Mentorship Programme – post by @harishanker. Share your feedback to help shape mentorship in our community, and even volunteer as a mentor!

The next phase of initiatives to promote and increase sustainability in the WordPress community and wider is the Proposal: establishment of a formal WordPress Sustainability Team. The sustainability initiative meets weekly on Fridays in the #sustainability channel on the Make WordPress Slack. All welcome to attend or view the discussions asynchronously.

4. Updates on releases

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.

WordPress 6.3 will be the next major release.

Roadmap to 6.3 

WordPress 6.3 Planning Roundup

6.3 Bug Scrub schedule

#6-3-release-leads channel on Slack is a good way to keep up with what is happening with the release.

Last minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. for reference

6.2.2 Security release – this came out on May 20, 2023. It addresses 1 bug and 1 security issuesecurity issue A security issue is a type of bug that can affect the security of WordPress installations. Specifically, it is a report of a bug that you have found in the WordPress core code, and that you have determined can be used to gain some level of access to a site running WordPress that you should not have.. As it is a security release, it is recommended that sites are updated immediately if you have not done so already.

Last Gutenberg release: 15.9 available to download.


4. Help requests relating to tickets or from Component Maintainers

If you have any tickets you would like to raise, you can share them in comments too. If you can not attend live, you can still add a ticketticket Created for both bug reports and feature development on the bug tracker. and your query in the comments, and the facilitator will be able to share it in the meeting.

Volunteers are also needed to help run 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. scrubs.

@oglekler requested feedback on ticket #58354 in the Help/About component.

@kebbett requested review and test the PR for ticket #57893. This ticket is in the 6.3 milestone.

@petitphp requested a second opinion on ticket #58312.

@mrinal highlighted ticket #58416.

5. Open floor

Update on core tables at WordCamp Europe – if you have an update to share, you can also add it to the comments on the agenda.
Preparing for WordCamp Europe 2023 Contributor Day.

@webcommsat shared the link to a draft post to be shared with WCEU team once published.

Post dev chat posts

Preparing to join the WordCamp Europe 2023 core tables at 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/.? Information to help you get started and set up a local environment in advance.

WordPress 6.4 Development Cycle – published June 5, 2023.

Gutenberg 15.9.1 available.

Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the #core Slack channel.

Props to @marybaum for review.

#6-3-2, #6-4-2, #contributor-day, #dev-chat, #summary, #wceu

Contribute to Core at WordCamp Europe Contributor Day 2023

What does the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team do?

Core is made up of contributors from many different areas and teams across 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/. Because Core is made up of many different components and parts, there is a ton of overlap with the other Make teams (polyglots, themes, plugins, 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., etc.). It is an exciting and dynamic place to observe or contribute.

The team holds a weekly developer chat in the Make WordPress #core channel on 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/. every Wednesday at 20:00 UTC.

New Contributor Meetings are held in the same channel on the 2nd and 4th Wednesdays just prior to the weekly developer chat at 19:00 UTC.

What areas of Core will I be able to work on at 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. Europe 2023?

The Core team and the Core WordPress software is segmented in a number of ways. While there will be some community leaders present representing some specific parts of the Core team, you can contribute to any of these segments at 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/. and there will likely be several contributors experienced in these areas. These are the most common ways that you’ll see Core divided.

Components

Currently, there are 62 components and sub-components within Core. These represent overarching categories of functionality within the code base. Some examples of these are Database, External Libraries, TaxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies., Feeds, etc. A handful of components also have sub-components. For example, Embeds, Gallery, and Upload are sub-components of the Media component.

Focuses

In TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., there are also several focuses. Focuses are disciplines or concepts that span many components, or even the entire Core code base. Some examples of these are accessibility, coding-standards, rest-api. Contributors that specialize in these focuses often work with many different component maintainers.

Sub Teams

There are also a few contributor groups that are still technically under Core, but operate as their own team. Some examples of this are Editor, Performance, AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility). These sub teams will each be represented by table leads at contributor day.

Preparing for Contributor Day before leaving home

Register for a WordPress.org profile and the WordPress.org Slack instance

The large majority of the communication around contributing to the WordPress open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. projects happens on WordPress.org or in the WordPress Slack instance. Your first step should be to register for both in that order.

There are 5-minutes videos to help you get started with the tools of communications. The Marketing Team with other contributors has been making different versions on this in a number of languages.
Set up a WordPress.org and Slack account for the Make WordPress Channel.

A majority of the Core components and sub teams also have their own channels within the WordPress Slack instance.

Install required software to contribute to the code

For those who would like to contribute by way of writing or checking code, the most popular method is by having a local development environment installed on your system.

Installing local environments are likely to be easier and quicker before you arrive at the conference venue. Conference WiFi can often be unreliable or be over-burdened. Getting set up before the event can help reduce the time you will spend installing and setting up the software on the day. You can then get onto more interesting things when you are at the conference!

In order to contribute to Core from a development perspective, you will need the following software installed on your machine:

  • GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. https://git-scm.com/. or SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. (whichever you prefer)
  • NodeJS (WordPress currently requires NodeJS 14.x)
  • npm (comes bundled with NodeJS)
  • Composer (optional, but highly recommended)

Additionally, you will need to choose one of the following:

Note: There are other tools that can be used to set up a local development environment (such as Local), but the two above are the ones maintained and have official support.

Decide how you’re going to work with the codebase

There’s a few options for you to work with the wordpress-develop codebase.

Note: if you chose the Vagrant/Virtualbox/VVV option above, the default is the third option below, but you can change that later.

Forking WordPress/wordpress-develop on GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/

This option will allow you to submit and work within a pull request on GitHub. When using this option, all of the configured automated testing will run on your code to help verify your change. You can read more about this option in the Core Handbook.

Using WordPress/wordpress-develop directly

With this option, you’ll clone the wordpress-develop repository locally and use that as your codebase. You won’t be able to push any changes or submit pull requests, but you will be able to create patches with your changes to submit on Trac.

Using SVN to check out WordPress

With this option, you’ll checkout the `trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.` branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". of the develop.svn.wordpress.org repository to use as your local WordPress site. Any changes you make need to be submitted as patches.

Docker Option

Below are the basic steps to get started with the local Docker environment:

  1. Clone your repository of choice from the previous section. If you’re using a fork that you created, the command will look like this: git clone git@github.com:{your GitHub username}/wordpress-develop
  2. Run cd wordpress-develop to move into the directory created by the git clone.
  3. Run npm install to install dependencies
  4. Run npm run env:start to start the development environment
  5. Run npm run env:install to set up clean installation with the user adminadmin (and super admin) and the password password
  6. Run npm run build:dev to run a build.

You can now load WordPress:

Frontend: http://localhost:8889

Backend: http://localhost:8889/wp-admin/

  • Username: admin
  • Password: password

You will find these steps and more details in the project’s README.md file.

Varying Vagrant Vagrants option

You will find detailed instructions for how to get started on the project’s website.

Other tips

  • Running npm installvagrant up, or npm run env:start can be networknetwork (versus site, blog) intensive. Run these at home before you leave for the event and confirm everything’s working as expected. Depending on what you work on during Contributor Day, you may need to run these commands again. But having dependencies, virtual boxes, and containers cached locally will greatly decrease the time they take to run at the event.
  • Try creating patches or a PR ahead of time. If you’re able to start working on a ticketticket Created for both bug reports and feature development on the bug tracker. before the event, contributors at the event can give you feedback on your work so far.
  • Read about finding bugs to fix and identify any you are interested in prior to heading to the event.
  • The ‘good first bugs‘ report in Trac is a great place to find easier tickets to get your feet wet. There’s also a similar list of “good first issues” for Gutenberg.
  • There is also now support for GitHub Codespaces to contributor to Core.

Helpful links

Below are a handful of other helpful links that will help you be better prepared for Contributor Day.


Many thanks to all the contributors who helped with materials for this post – as ever with WordPress, it is a real team effort! Special thanks to @desrosj who collected much of the preparation information, to @wpscholar for sharing his more detailed document from a previous WordCamp, and to @webcommsat who pulled together the material from different editions. Thanks also to @sergeybiryukov, @jeffpaul and @webcommsat for review and contributions, and to @audrasjb, @paulbearne, @mark99, @vimes1984, @meher, @oglekler for contributions and review for material used from previous editions of this post. Thanks to @davidbaumwald, @joemcgill for review of the checklist.

After WordCamp Europe, a version of this post will be added to the Core Team Handbook.

#contributor-day

Preparing for WordCamp Asia Contributor Day 2023

Checklist for those attending in-person

If you’re planning on attending 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/. for #WCAsia, CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. and long time Core Contributor Jonathan Desrosiers (@desrosj) has created a wonderful checklist and list of things to expect.

View the post on his personal site: Preparing for a WordCamp Contributor Day.

Some other useful links

FAQs for new contributors to core

Finding bugs to fix

List of ‘good first bugs‘ to get started in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and a similar list of “good first issues” for Gutenberg.

If you’re on Twitter, you can follow https://twitter.com/GoodFirstBugs.

There is now support for GitHub Codespaces to help new contributors to core.

Thanks to @davidbaumwald and @webcommsat for working on this post.

#contributor-day

Privacy Office Hours Minutes 14 May 2020 Plans for WCEU Contributor Day

Mission for 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/.:

Make Privacy Actionable.

Working groups:

There will be two working groups:
– Coding working group (coordinated by @garrett-eclipse);
– Non-coding working group (coordinated by @carike).

Pre-event office hours:

– 3 June 2020 at 10:00 UTC;
– 3 June 2020 at 19:00 UTC.

Pre-event office hours are to help onboard new contributors.
This primarily involves making sure that they have access to the tools necessary for the day.

Tools:

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/.:
Privacy Policy: region-specific at https://slack.com/intl/en-us/privacy-policy
Terms of Service: region-specific at https://slack.com/intl/en-us/terms-of-service/user

StreamYard:
Privacy Policy: https://streamyard.com/resources/docs/privacy/
Terms of Service: https://streamyard.com/resources/docs/tos/
We will be using StreamYard, as a number of experienced contributors in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-privacy have expressed an unwillingness to use Zoom due to privacy considerations.

YouTube:
Privacy Policy: https://policies.google.com/privacy
Terms of Service: https://www.youtube.com/t/terms

Core TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. (coding working group):
Privacy Policy: https://wordpress.org/about/privacy/

GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/ (coding working group):
Privacy Policy: https://help.github.com/en/github/site-policy/github-privacy-statement
Terms of Service: https://help.github.com/en/github/site-policy/github-terms-of-service

How to participate:

As a host:
If you are interested in hosting one or more topics, please comment below.
You can contact @carike on Slack if you would like more information.

As a guest via StreamYard:
You DO NOT need to register a StreamYard account in order to enter the stream as a guest.
You DO NOT need to download any program in order to use StreamYard. It is an in-browser solution.
You DO NOT need to appear on-screen if that is not something you are comfortable with. An audio-only option is available. We’re going to be using a very practical approach, so I’m going to be screen-sharing most of the time anyway.
We will provide new contributors with instructions on joining StreamYard as a guest via e-mail.
Instructions can also be found here: Guest Instructions: https://streamyard.com/resources/docs/guest-instructions/
We will provide new contributors with a link to join the stream via Direct Message (DM) on Slack, as there can only be six contributors “onscreen” (or via audio) at any one time (i.e. two hosts and four new contributors), with up to four additional new contributors in the “waiting room”.

As a guest via YouTube:
You DO NOT need to register an account with YouTube in order to watch the stream.
You DO need to register an account and be logged in to YouTube in order to participate in the live chat.
StreamYard supports integrating live chat messages from YouTube.
This will allow for more real-time input and also allow participation among those who do not want to use audio, or appear onscreen.
We are trying to recruit experienced contributors to help moderate the YouTube live chat to ensure compliance with the WCEU Code of Conduct, as well as to highlight any questions, comments and suggestions to the hosts.
Please comment below if you are able to help with YouTube live chat moderation.
You can find a copy of the 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. Europe Online 2020 here: https://2020.europe.wordcamp.org/code-of-conduct/

Via Trac (coding working group):
You DO need to register an account with 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/ in order to comment on Trac tickets.

Via GitHub (coding working group):
You DO need to register an account with GitHub in order to create / comment on issues or to create / comment on Pull Requests (PRs).

On the day:

Coding working group:

13:00 – 16:00 UTC (coding working group)
Garrett will be available on Slack during this time.

The coding working group will participate via Slack, Core Trac and GitHub.
@garrett-eclipse is going through the list of privacy-related tickets to mark them with the “good first 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.tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) where applicable.
For the more adventurous, there is the option to contribute to “help wanted” tickets for the next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. (WordPress 5.5.).
An overview of current privacy tickets can be found here:
https://make.wordpress.org/core/components/privacy/

Non-coding working group:

The non-coding working group will have two two-hour sessions.

13:30 – 15:00 UTC
How to market without destroying user privacy (working title only).
Hosts: @carike and @jonoaldersonwp
During this session, we hope to identify online marketing best-practices that can be implemented even when users have opted-out (or not opted-in, depending on the jurisdiction) to being tracked with the view of creating actionable Trac tickets and / or to provide a resource for content marketing.
Topics will include:
– What is informed consent in a marketing context?
– Which digital marketing strategies were employed pre-the-ability-to-track-across-platforms and how may we able to adapt these?
– Which data points may still remain available for analytics if a user opts out of / does not opt in to the collection of their PPI.
Jono is “special ops” at Yoast SEO and we are very excited to have him participate.

16:00 – 18:00 UTC
A case study in the application of the Privacy Workflow Document and the Disclosures and Permissions (DPT) tabs.
Hosts: @carike and @pepe
In this session, we will be attempting to harmonize the Privacy Workflow Document and the Disclosures and Permissions (DPT) tabs and apply them practically to the WP Job Manager 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.
The desired outcome for this session is an action plan for an education drive among plugin and theme authors regarding the proposed disclosures.json file.
Pepe has previously presented at WordCamp, is very involved with the #core-privacy team and was helped to create the draft Privacy Workflow Document. His insight will be invaluable to this session.

License:

We will be using the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license for the non-coding work group:
https://creativecommons.org/licenses/by-sa/4.0/legalcode

Contributions to the WordPress.org code are licensed in terms of the General Public License (GPLGPL GNU General Public License. Also see copyright license.) version 2 or later:
https://www.gnu.org/licenses/old-licenses/gpl-2.0.html

Slack logs:

You can view the Slack logs here:
https://wordpress.slack.com/archives/C9695RJBW/p1589396619341400
In order to view the logs, you will first need a WordPress.org account: https://login.wordpress.org/register
You will then need to register a Slack account: https://make.wordpress.org/chat/

Change log:
14 May 2020 at 14:15 UTC – @carike added GitHub information.
14 May 2020 at 17:45 UTC – @carike updated formatting in the Slack links.
16 May 2020 at 11:35 UTC – @carike switched out the non-coding session starting at 16:00 UTC, as Pepe has agreed to co-host.
18 May 2020 at 18:05 UTC – @carike added the times Garrett will be available on Contributor Day.
1 June 2020 at 13:55 UTC – @carike changed the start time for the first non-coding session in order to accommodate the WCEU introductions.
3 June 2020 at 19:40 UTC – @carike added details for the workgroup sessions and removed the third session.

#contributor-day, #privacy, #wceu-2020, #wordcamp-europe-online-2020

Help needed —> Core team and WCEU Contributor Day

You may have seen update posts on WCEU’s plans on how to create an online 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/. this year (see posts from April 15th and April 24th). You may have also caught a reference to this in this past week’s devchat (see related summary post).

As part of the coming online/virtual WCEU, we’ve been asked to plan for how CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. will handle an online Contributor Day.  The specific items we’ve been asked to consider:

  • Ensure our Getting Started at a Contributor Day handbook page has been updated as necessary
  • Ensure new contributor meeting happens between 25 May and 3 June, alerting the WCEU Contributor Day team via comment
  • Record a video intro about the Core team, similar to the live intros usually given in-person
  • Confirming list of good-first-issues and experience-issues for Contributor Day
  • Identifying 2+ experienced contributors to help facilities during Contributor Day
  • Plan for a live intro session at the beginning of Contributor Day

So I’m looking to you all to help here: who can help cover any of these tasks and help during the actual WCEU Contributor Day event? Please comment on this post noting which of the bulleted needs above are items you can assist with, thanks!

#contributor-day, #wceu

Dev Chat Summary: October 30th 2019

This post summarizes the weekly dev chat meeting from October 30th 2019 (agenda / Slack Archive).

Announcements

WordPress version 5.3 Release Candidate 3 was released on Tuesday. Everyone please help by testing out the RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta)..

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor team released Gutenberg version 6.8.

Dev chat meeting time

Like every year, with end of DST (daylight saving time), the meeting time should be moved from 20:00 UTC to 21:00 UTC.

Two options are proposed:

  • Moving on Wednesday November 13th (the day after WP 5.3 is going to be released)
  • Moving on Wednesday November 20th (one week later)

Please share your thoughts in this post’s comments.

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. US 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/.

WordCamp US’s contributor day is planned for Sunday 3rd November.

5.3 was branched last week, so contributors will be able to work on WordPress 5.4 milestone since trunk is now version 5.4-alpha.

@earnjam and @wpscholar will be leading the core table, Helping people get set up, learn how to get started, find places to focus on work, etc. They also should have several component leads present that can split off and focus on their areas for people who are interested.

Upcoming Releases

WordPress 5.3 Release Candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 4 is scheduled next Tuesday if needed.

There is still 7 tickets open in the milestone.

@azaozz regrets that things weren’t reported much earlier, during betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.. By the way, two tickets have patches already, one is almost there, and one may be a candidate for 5.3.1. As 5.3 was branched, all fixes are probably going to be committed to trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. (5.4-alpha) but hold on on merging to 5.3 for couple of days to allow easier testing and review. All are (possible) regressions with the way some plugins use particular hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. around image post-processing and image 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. updates.

@joyously reported a feedback found in Alpha/Beta support forum. It was already merged to Gutenberg and looks fixed in 5.3 blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor code. @youknowriad was pinged as Editor focus lead for WP 5.3.

Open floor

@joyously asked about backporting security fixes to old versions request’s status.

@clorith and @audrasjb noted there will be a panel session at WordCamp US. For those who are not attending WordCamp US, questions can be sent via Twitter.

@desrosj added that there was a very large amount of feedback. @chanthaboune and others are working to compile all that feedback so that all of it can receive proper consideration.

#5-3, #contributor-day, #wcus

How you can help with the Network Admin UI during contributor day

A previous write-up explains how you can help test and capture the network admin UI. Here’s a specific version for how you can help during 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/. this weekend.

There are four steps to the workflow at the moment:

  1. Capture a visual record of networknetwork (versus site, blog) adminadmin (and super admin) screens.
    • Ideally on a device/browser combination that has not yet been captured.
    • If comfortable, post the screen captures and notes on make.wordpress.org/flow.
    • If you need access to Make/Flow, ask in #coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-flow on 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/. or around the physical room you’re in (if it’s full of contributors).
  2. Observe screens, actions, and results throughout the network admin.
    • This can happen during or after step 1. You can also just do this without the first step.
    • Look for things that don’t make sense, visual errors, pieces that are difficult on mobile, etc…
  3. Document observations in the screen sweep sheet.
    • This can be with or without a TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker.. With or without a screenshot.
    • Acts as a note so that we know that to come back to as part of the overall admin UIUI User interface improvement effort.
  4. Help with the screen sweep sheet.
    • Open a ticket if there is none. Add screenshots if there are none. Confirm/deny the issue.
    • And patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.. If there’s a ticket on the screen sweep sheet that you can patch, submit away.

While this is an ordered list, you do not need to treat it like one. Pick a step that feels comfortable and concentrate on that. If you need guidance, there are folks in Slack that are always happy to help.

Current captured visual records:

By all means, if you have a device that is already captured, don’t hesitate to capture it in your own way or to skip step 1 entirely and start observing.

Thanks for the help!

#contributor-day, #multisite