The inaugural New Contributors Meeting was held on Wed July 5th at 19:00 and had a great turnout with lots of questions asked in the #core channel (read the full archive ).
The informal agenda was to try and answer as many general questions as possible and then move over to 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. scrub/ticketticket Created for both bug reports and feature development on the bug tracker. review portion.
Discussion Highlights
- Working with git in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. – some links for getting setup and using git for core contribution:
- Applying patches – quick links in the 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/ chat on how to apply a 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. via the command line
- Unit Testing – some links on how to get setup with and using unit tests for core contribution:
Tickets Discussed:
- #33756 – Improve docs for sanitize_title()
- #38828 – Update_blog_details() performance improvement ideas
- #38310 – Improve “wp_update_term” documentation
The next meeting will take place in the #core slack channel on Wed, July 12th at 19:00. Please feel free to drop in with any questions or tickets you’d like to discuss!
Thanks to everyone that attended and please feel free to leave a comment below or reach out to any of the moderators with questions.
Moderators: @flixos90, @welcher, @stevenkword, @desrosj