This past Wednesday, the weekly new contributor meeting was held in the #core Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. room. Here is a recap of the meeting. A full chat log is also available.
Participants: @adhun @afercia @alfonso100 @asalce @azaozz @boonebgorges @coderkevin @cousett @davidmosterd @desrosj @flixos90 @harryjackson1221 @jack50n9 @joemcgill @joyously @katmoody @mapk @mp518 @mrasharirfan @nicbertino @pbearne @psdtohtmlguru @ryankanner @sergeybiryukov @sygnoos @thomasplevy @tjnowell @xkon @yahil @mrasharirfan
Discussion Highlights
Ways other than Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. to find where to help
- While Trac is the primary spot, there are several other places to find areas to focus your contribution efforts:
- Everything must pass through Trac eventually. But, Trac is not always the best place for ideas to take shape. Other instances will pop up based on the needs of the Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. & component focuses.
- For finding priorities within Trac, the Next Major Release (currently 4.9) ticket Created for both bug reports and feature development on the bug tracker. list is a good place to start.
Accessibility 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) Contributions
If your expertise is not in code, but rather accessibility, the a11y 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) team meets weekly, every Monday at 17:00UTC in the #accessibility Slack room. All are welcome!
Meetings are held regularly for many of the Core components and Make WordPress teams. Attending these meetings is a great way to get a feel for how progress is made within the project and find ways you can offer help.
New PHPUnit Test section in the Core Handbook
@boonebgorges has recently spent some time constructing a new section of the WiordPress Core Handbook, “Writing PHPUnit Tests“.
Miscellaneous Topics
- @coderkevin inquired if there had been discussions about memory leakage within the test suite. #41641 was mentioned as the ticket to read into for this. The Distributed Host Testing project is also relevant to that ticket.
- Currently, there is no central place for documentation on the test suite’s factory classes. The inline documentation for the
__construct() functions within each factory class is currently the best place for this information.
Tickets Reviewed
- #41743 (Using the_widget on a widget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. that has not been registered results in an undefined index notice.)
Next Week’s Meeting
The next meeting will take place in the #core slack channel on Wednesday, September 6, 19:00 UTC. Please feel free to drop in with any questions or tickets you’d like to discuss!
Thanks to everyone who attended! As always, please feel free to leave a comment below or reach out to any of the moderators (@adamsilverstein, @desrosj, @stevenkword, @welcher) with questions on Slack. Or, feel free to reach out to any core developer or component maintainer with questions specific to certain core areas.
#new-contributors, #summary
