SlideShare a Scribd company logo
zeropointdevelopment.com for WordCamp Brisbane 2018 #WCBNE
WordPress
In 2014 Matt said..
@DeveloperWil #WCBNE
Organisations… should
dedicate 5% of their
people to working on
something to do with
core
https://ma.tt/2014/09/five-for-the-future/
WordPress gives us..
• A Voice
• A Career
• An Income
• A Place to Learn New Skills
• A Community
• Friendships and Business Colleagues
@DeveloperWil #WCBNE
In 2014 Matt said..
@DeveloperWil #WCBNE
..whatever it might
be that helps move
WordPress mission
forward
https://ma.tt/2014/09/five-for-the-future/
@DeveloperWil #WCBNE
“It is vital for the future success of
WordPress to have a healthy group of
contributors.”
Welcome to Trac – enhanced wiki and issue tracking
system
– Follow development timeline
– Contribute to a ticket
If you are new
– Find some “First Good Bugs”
– core.trac.wordpress.org/tickets/good-first-bugs
@DeveloperWil #WCBNE
Refs: make.wordpress.org/core make.wordpress.org/core/handbook
@DeveloperWil #WCBNE
@DeveloperWil #WCBNE
@DeveloperWil #WCBNE
The process (high-level):
Build and configure local dev site
– Download WordPress from Subversion (SVN) repo
– Build site from /src/ using Node.js, npm and Grunt
– Configure site in /build/
– Clean SVN with diff, revert, up, grunt
– Apply a patch file from the ticket if there is one
• patch -p0 < 44360.1.patch
@DeveloperWil #WCBNE
Ref: deliciousbrains.com/developers-guide-contributing-wordpress-core/
The process (high-level):
Development & Testing
– Apply your code and test with PHPUnit
– Create a patch file with SVN diff > 44360.2.patch
Attach patch on updated Trac ticket and submit
Clean SVN ready for next ticket
@DeveloperWil #WCBNE
Ref: deliciousbrains.com/developers-guide-contributing-wordpress-core/
WordPress consumes Gutenberg packages which are
all managed by GitHub
github.com/WordPress/gutenberg
@DeveloperWil #WCBNE
Ref: deliciousbrains.com/developers-guide-contributing-wordpress-core/
Join core-related channels on slack
– #core
– #core-js
– #core-editor
– #core-php
– #core-restapi
@DeveloperWil #WCBNE
Ref: make.wordpress.org/chat
@DeveloperWil #WCBNE
Extending functionality, embracing
new technology and designs
• New services and APIs to integrate with
• New ways that users want to interact with
• Unique/niche functionality requirements
• Compliment new core functionality
• Submit plugin zip for review to include in SVN repo
– developer.wordpress.org/plugins/wordpress-org
@DeveloperWil #WCBNE
Ref: make.wordpress.org/core/handbook/best-practices/coding-standards
Ref: make.wordpress.org/plugins #pluginreview
• New devices
• New design concepts
• Unique/niche design requirements
• Submit theme zip for review to include in Directory
– Theme Check Plugin
wordpress.org/plugins/theme-check
– Theme Upload
wordpress.org/themes/getting-started
@DeveloperWil #WCBNE
Ref: make.wordpress.org/themes/handbook/review/required
Ref: make.wordpress.org/themes #themereview
@DeveloperWil #WCBNE
“Raising the quality of the WordPress
user experience”
• Automated unit testing
– QUnit (JavaScript) , PHPUnit (testing & writing new)
• Beta testing pre-release versions
– Plugin: wordpress.org/extend/plugins/wordpress-beta-tester
• User Testing
– UI, Gutenberg
– Features: make.wordpress.org/core/features
@DeveloperWil #WCBNE
Ref: make.wordpress.org/core/handbook/testing
Ref: make.wordpress.org/test #core-test
“The Theme Review team maintains the official
Theme Review Requirements, the Theme Unit Test
Data, and the Theme Check Plugin.”
“The team is open to anyone..”
@DeveloperWil #WCBNE
Ref: make.wordpress.org/themes/handbook/get-involved/become-a-reviewer
@DeveloperWil #WCBNE
“..expertise across the project to
improve the accessibility of WordPress
core and resources.”
WordPress Accessibility Coding Standards (WPACS)
“All new or updated code released in WordPress must
conform with the WCAG 2.0 guidelines at level AA.”
- en.wikipedia.org/wiki/Web_Content_Accessibility_Guidelines
@DeveloperWil #WCBNE
Ref: make.wordpress.org/accessibility
Ref: make.wordpress.org/accessibility/handbook/get-involved
“We need people who know to test accessibility
and/or use assistive technology that test existing and
new functionality”
• Testing existing patches for Trac tickets
• Gutenberg
@DeveloperWil #WCBNE
Ref: make.wordpress.org/accessibility
Ref: make.wordpress.org/accessibility/handbook/get-involved
@DeveloperWil #WCBNE
“While we try to be proactive in
preventing security problems, we do
not assume they’ll never come up.”
Make sure WordPress is the cause!
– Debug Bar plugin
wordpress.org/extend/plugins/debug-bar
– Backtrace Script
gist.github.com/scribu/625769
Create new ticket on Trac
– core.trac.wordpress.org/newticket
@DeveloperWil #WCBNE
Ref: make.wordpress.org/core/handbook/testing/reporting-bugs
Ethical reporting
– Give reasonable time to correct issue before going public
– HackerOne
hackerone.com/wordpress
– WordPress.com or WP Mobile App
hackerone.com/automattic
Bug Gardening
– Test & confirm bug reports
make.wordpress.org/core/handbook/testing/bug-gardening
@DeveloperWil #WCBNE
Ref: make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities
@DeveloperWil #WCBNE
In 2014, non-English downloads
surpassed English downloads.
- Matt: State of the Word 2014
• WordPress Core files .pot files
• Plugins
• Themes
• Codex
• Documentation
• Pretty much everything!
@DeveloperWil #WCBNE
Ref: make.wordpress.org/polyglots
#polygots
@DeveloperWil #WCBNE
“WordPress is used by 59.4% of all the
websites whose content management system
we know. This is 32.2% of all websites.”
- w3techs.com
• WordPress.org support forums
• Slack
wordpress.slack.com
• LinkedIn groups
WordPress Developers, WordPress Experts,
WordPress
• Facebook groups
Advanced WordPress, WordPress Australia, Genesis
WordPress, +00’s more
@DeveloperWil #WCBNE
Ref: make.wordpress.org/support
#forums
• Training
make.wordpress.org/training
• WordPress.tv
make.wordpress.org/tv
– Edit videos
– Lower thirds
– Uploading to .tv
@DeveloperWil #WCBNE
Ref: make.wordpress.org/support
#forums
@DeveloperWil #WCBNE
“..keeping content current with each
WordPress release and adding new content
and screenshots..”
• Contributor Handbooks
• WordPress inline docs
• developer.wordpress.org
• Codex
– Moving to HelpHub
@DeveloperWil #WCBNE
Ref: make.wordpress.org/docs
#docs
@DeveloperWil #WCBNE
At local WordPress meetups
and national WordCamps
• No previous speaking skills required
• People are interested in what you have to say!
• Talk about: a project, a plugin, a feature, a theme, a
caching module in NGNIX that makes WordPress go
faster – ANYTHING!
• Speak for 10 mins or just as long as you are
comfortable to do
@DeveloperWil #WCBNE
@DeveloperWil #WCBNE
At local WordPress meetups
and national WordCamps
• Your time is precious and appreciated!
• Updating meetup.com, setting up/packing down
tables and chairs, meet & greet, graphic design,
planning, sponsor wrangling, marketing
• Front-row seats
• Free conference ticket
• Learn new skills: meet & greet, AV, time
management
• Network your legs off
@DeveloperWil #WCBNE
@DeveloperWil #WCBNE
Absolutely yes, you can and you should!
• Strongly advise using meetup.com
• A venue
• Funding and sponsorship
– Meetup fees USD $14.99/month (AUD ~$21)
• Your time and commitment
• A team of good people to help
• Some topics to discuss
• A format: coffee & chat, AV presentations
@DeveloperWil #WCBNE
“As of the end of Q2 2018, there were 617 official
Meetup groups.”
- Meetup Chapter
• At least one event per month
• Abide by the "Five Good Faith Rules”
• Step-down as organiser to co-organiser
@DeveloperWil #WCBNE
“As of the end of Q2 2018, there were 617 official
Meetup groups.”
- Meetup Chapter
• WordPress Community Support (WPCS) pays
Meetup fees & maybe venue fees
• Commit to at least three months
• Swag, Slack #community-events #community-team
@DeveloperWil #WCBNE
Download My
“Ultimate WordPress Event Organiser Setup Guide”
zeropointdevelopment.com/WCBNE18
Password: Contributor
@DeveloperWil #WCBNE
[Front Cover] zeropointdevelopment.com
[2,4] Automattic
[5] zeropointdeveloment.com
[7,8,9] wordpress.org
[13] wordpress.slack.com
[14,17,20,23,26,28,31] zeropointdevelopment.com
[33,35] flightpath.blog cc Alex Shiels
[37] WPSydney Meetup Group
[Back Cover] zeropointdevelopment.com
@DeveloperWil #WCBNE
▪ Using WordPress since 2008
▪ Consultancy, Development, APIs & Security
▪ Organiser WPSyd Meetup & WordCamp Sydney
@DeveloperWil #WCBNE
zeropointdevelopment.com
@DeveloperWil
♥ Pizza & Craft
Beer

More Related Content

Contributing Back to WordPress - Getting Involved in the Community

  • 1. zeropointdevelopment.com for WordCamp Brisbane 2018 #WCBNE WordPress
  • 2. In 2014 Matt said.. @DeveloperWil #WCBNE Organisations… should dedicate 5% of their people to working on something to do with core https://ma.tt/2014/09/five-for-the-future/
  • 3. WordPress gives us.. • A Voice • A Career • An Income • A Place to Learn New Skills • A Community • Friendships and Business Colleagues @DeveloperWil #WCBNE
  • 4. In 2014 Matt said.. @DeveloperWil #WCBNE ..whatever it might be that helps move WordPress mission forward https://ma.tt/2014/09/five-for-the-future/
  • 5. @DeveloperWil #WCBNE “It is vital for the future success of WordPress to have a healthy group of contributors.”
  • 6. Welcome to Trac – enhanced wiki and issue tracking system – Follow development timeline – Contribute to a ticket If you are new – Find some “First Good Bugs” – core.trac.wordpress.org/tickets/good-first-bugs @DeveloperWil #WCBNE Refs: make.wordpress.org/core make.wordpress.org/core/handbook
  • 10. The process (high-level): Build and configure local dev site – Download WordPress from Subversion (SVN) repo – Build site from /src/ using Node.js, npm and Grunt – Configure site in /build/ – Clean SVN with diff, revert, up, grunt – Apply a patch file from the ticket if there is one • patch -p0 < 44360.1.patch @DeveloperWil #WCBNE Ref: deliciousbrains.com/developers-guide-contributing-wordpress-core/
  • 11. The process (high-level): Development & Testing – Apply your code and test with PHPUnit – Create a patch file with SVN diff > 44360.2.patch Attach patch on updated Trac ticket and submit Clean SVN ready for next ticket @DeveloperWil #WCBNE Ref: deliciousbrains.com/developers-guide-contributing-wordpress-core/
  • 12. WordPress consumes Gutenberg packages which are all managed by GitHub github.com/WordPress/gutenberg @DeveloperWil #WCBNE Ref: deliciousbrains.com/developers-guide-contributing-wordpress-core/
  • 13. Join core-related channels on slack – #core – #core-js – #core-editor – #core-php – #core-restapi @DeveloperWil #WCBNE Ref: make.wordpress.org/chat
  • 14. @DeveloperWil #WCBNE Extending functionality, embracing new technology and designs
  • 15. • New services and APIs to integrate with • New ways that users want to interact with • Unique/niche functionality requirements • Compliment new core functionality • Submit plugin zip for review to include in SVN repo – developer.wordpress.org/plugins/wordpress-org @DeveloperWil #WCBNE Ref: make.wordpress.org/core/handbook/best-practices/coding-standards Ref: make.wordpress.org/plugins #pluginreview
  • 16. • New devices • New design concepts • Unique/niche design requirements • Submit theme zip for review to include in Directory – Theme Check Plugin wordpress.org/plugins/theme-check – Theme Upload wordpress.org/themes/getting-started @DeveloperWil #WCBNE Ref: make.wordpress.org/themes/handbook/review/required Ref: make.wordpress.org/themes #themereview
  • 17. @DeveloperWil #WCBNE “Raising the quality of the WordPress user experience”
  • 18. • Automated unit testing – QUnit (JavaScript) , PHPUnit (testing & writing new) • Beta testing pre-release versions – Plugin: wordpress.org/extend/plugins/wordpress-beta-tester • User Testing – UI, Gutenberg – Features: make.wordpress.org/core/features @DeveloperWil #WCBNE Ref: make.wordpress.org/core/handbook/testing Ref: make.wordpress.org/test #core-test
  • 19. “The Theme Review team maintains the official Theme Review Requirements, the Theme Unit Test Data, and the Theme Check Plugin.” “The team is open to anyone..” @DeveloperWil #WCBNE Ref: make.wordpress.org/themes/handbook/get-involved/become-a-reviewer
  • 20. @DeveloperWil #WCBNE “..expertise across the project to improve the accessibility of WordPress core and resources.”
  • 21. WordPress Accessibility Coding Standards (WPACS) “All new or updated code released in WordPress must conform with the WCAG 2.0 guidelines at level AA.” - en.wikipedia.org/wiki/Web_Content_Accessibility_Guidelines @DeveloperWil #WCBNE Ref: make.wordpress.org/accessibility Ref: make.wordpress.org/accessibility/handbook/get-involved
  • 22. “We need people who know to test accessibility and/or use assistive technology that test existing and new functionality” • Testing existing patches for Trac tickets • Gutenberg @DeveloperWil #WCBNE Ref: make.wordpress.org/accessibility Ref: make.wordpress.org/accessibility/handbook/get-involved
  • 23. @DeveloperWil #WCBNE “While we try to be proactive in preventing security problems, we do not assume they’ll never come up.”
  • 24. Make sure WordPress is the cause! – Debug Bar plugin wordpress.org/extend/plugins/debug-bar – Backtrace Script gist.github.com/scribu/625769 Create new ticket on Trac – core.trac.wordpress.org/newticket @DeveloperWil #WCBNE Ref: make.wordpress.org/core/handbook/testing/reporting-bugs
  • 25. Ethical reporting – Give reasonable time to correct issue before going public – HackerOne hackerone.com/wordpress – WordPress.com or WP Mobile App hackerone.com/automattic Bug Gardening – Test & confirm bug reports make.wordpress.org/core/handbook/testing/bug-gardening @DeveloperWil #WCBNE Ref: make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities
  • 26. @DeveloperWil #WCBNE In 2014, non-English downloads surpassed English downloads. - Matt: State of the Word 2014
  • 27. • WordPress Core files .pot files • Plugins • Themes • Codex • Documentation • Pretty much everything! @DeveloperWil #WCBNE Ref: make.wordpress.org/polyglots #polygots
  • 28. @DeveloperWil #WCBNE “WordPress is used by 59.4% of all the websites whose content management system we know. This is 32.2% of all websites.” - w3techs.com
  • 29. • WordPress.org support forums • Slack wordpress.slack.com • LinkedIn groups WordPress Developers, WordPress Experts, WordPress • Facebook groups Advanced WordPress, WordPress Australia, Genesis WordPress, +00’s more @DeveloperWil #WCBNE Ref: make.wordpress.org/support #forums
  • 30. • Training make.wordpress.org/training • WordPress.tv make.wordpress.org/tv – Edit videos – Lower thirds – Uploading to .tv @DeveloperWil #WCBNE Ref: make.wordpress.org/support #forums
  • 31. @DeveloperWil #WCBNE “..keeping content current with each WordPress release and adding new content and screenshots..”
  • 32. • Contributor Handbooks • WordPress inline docs • developer.wordpress.org • Codex – Moving to HelpHub @DeveloperWil #WCBNE Ref: make.wordpress.org/docs #docs
  • 33. @DeveloperWil #WCBNE At local WordPress meetups and national WordCamps
  • 34. • No previous speaking skills required • People are interested in what you have to say! • Talk about: a project, a plugin, a feature, a theme, a caching module in NGNIX that makes WordPress go faster – ANYTHING! • Speak for 10 mins or just as long as you are comfortable to do @DeveloperWil #WCBNE
  • 35. @DeveloperWil #WCBNE At local WordPress meetups and national WordCamps
  • 36. • Your time is precious and appreciated! • Updating meetup.com, setting up/packing down tables and chairs, meet & greet, graphic design, planning, sponsor wrangling, marketing • Front-row seats • Free conference ticket • Learn new skills: meet & greet, AV, time management • Network your legs off @DeveloperWil #WCBNE
  • 37. @DeveloperWil #WCBNE Absolutely yes, you can and you should!
  • 38. • Strongly advise using meetup.com • A venue • Funding and sponsorship – Meetup fees USD $14.99/month (AUD ~$21) • Your time and commitment • A team of good people to help • Some topics to discuss • A format: coffee & chat, AV presentations @DeveloperWil #WCBNE
  • 39. “As of the end of Q2 2018, there were 617 official Meetup groups.” - Meetup Chapter • At least one event per month • Abide by the "Five Good Faith Rules” • Step-down as organiser to co-organiser @DeveloperWil #WCBNE
  • 40. “As of the end of Q2 2018, there were 617 official Meetup groups.” - Meetup Chapter • WordPress Community Support (WPCS) pays Meetup fees & maybe venue fees • Commit to at least three months • Swag, Slack #community-events #community-team @DeveloperWil #WCBNE
  • 41. Download My “Ultimate WordPress Event Organiser Setup Guide” zeropointdevelopment.com/WCBNE18 Password: Contributor @DeveloperWil #WCBNE
  • 42. [Front Cover] zeropointdevelopment.com [2,4] Automattic [5] zeropointdeveloment.com [7,8,9] wordpress.org [13] wordpress.slack.com [14,17,20,23,26,28,31] zeropointdevelopment.com [33,35] flightpath.blog cc Alex Shiels [37] WPSydney Meetup Group [Back Cover] zeropointdevelopment.com @DeveloperWil #WCBNE
  • 43. ▪ Using WordPress since 2008 ▪ Consultancy, Development, APIs & Security ▪ Organiser WPSyd Meetup & WordCamp Sydney @DeveloperWil #WCBNE zeropointdevelopment.com @DeveloperWil ♥ Pizza & Craft Beer