Team Meeting April 11, 2016

Just before the 4.5 release we looked back and ahead on the work we do as a team. The following idea’s where discussed:

We need more coders (Andrea Fercia is doing way to much on his own), and we have to find a way to find and keep new coders for our team.

Be less focused on specific tickets, and more focused on tasks. And have somebody responsible for managing a goal, and keeping on top of all tickets pertaining to that goal. That may include asking somebody else to write it or work on it, but that person is keeping on top of that particular goal and whether it’s on track.

Start a mentor program for new contributors, teach them accessibility and have someone available to answer questions, assign a coder a ‘mentor’ to ping on Slack.

Find a way to get funding for the team. Almost all the work is done in our free time and this is part of the reason we are short of hands. Brainstorming about funding:

  • Crowd fund, for example Patreon.com
  • WordPress Agencies
  • Universities
  • WordPress Foundation
  • Accessibility organizations

Joe Dolson is preparing a survey regarding WP and Accessibility, so we can gather data. What AT are people using (they should complete the survey once for each combination they use with WP), their pain points, where they feel WordPress is strong/weak, overall impressions of how WordPress has changed since they started using it including data about when they started using it, what version they’re currently using, if they haven’t updated, etc…

Tickets cleaup

To investigate which tikets need work and which goals we need to set for future releases we organize a tickets focussing accessibility review session on Saturday. A bug gardening, ticket cleaning, bug scrub meeting on Saterday April 16 at 13:00 UTC in the accessibility channel in Slack. Everyone is welcome to join us.

Review the meeting at Slack

#accessibility-team-meetup, #weekly-meetings