My introduction slides to WordCamp London 2016 Contributor Day, held on Friday 8th April 2016 at the Graduate Centre, London Metropolitan University. For the version without notes, see http://www.slideshare.net/Gamajo/wordcamp-london-2016-contributor-day-introduction-60750237

1. Contributor Day

2. Welcome!
Gary Jones: @GaryJ
Welcome to WordCamp London Contributor Day.
My name is Gary Jones, and I’m one of the organisers for the WordCamp, and specifically this contributor day.
In this introduction, we’ll go through a few necessary bits of administration and explain how the day will run.

3. Fire Exits
No fire drills planned all weekend.
Primary exit is through the external door by registration and meet outside the front of the building.
If blocked, the secondary exit is to follow the green fire exit signs.

4. Hands up if you use
WordPress for your
job
Most of those with hands up, earn their income building on top of the efforts of others who have created the free software we know as WordPress. Today is the day
that we can all give back through our own contributions.

5. Everyone CAN
Contribute
I want to thank you for volunteering your time to contribute back to WordPress.
The fact you’ve made the effort to come along already shows me that you feel you can contribute. And you can, in many ways.

6. Do I need to be a
Developer?
One of the misconceptions about Contributor Days is that you need to be a developer to understand what’s going on, but that’s simply not true. You can have no
coding abilities whatsoever, and still make a big impact.
Designers, documentation writers, those who can speak multiple languages, those who have a willingness to help others and can find or work out solutions; all of the
people with those skill sets, and more, can contribute.

7. Hands up if you are
new to Contributing
Hands down if you’ve ever run WordPress trunk to test a plugin against it.
Hands down if you’ve filed a bug ticket on WordPress Core Trac.
Hands down if you ever answered a someone else's support forum question.
Hands down if you’ve ever given feedback on a user interface mockup or upcoming feature proposal.
These all examples of contributing that folks may not realise.

8. Hands up if this is
your first
contribution day
Contribution Days are just like contributing at home or work, except we get the benefit of like-minded people being in the same room, allowing easier discussion and
group efforts.
They are often attached to WordCamps, like this one, but sometimes run as standalone events, like WordUp Brighton Feb 2015, or WP London in Nov 2014 events.

9. Running Order
Let’s focus on how today will run.

10. Start Time End Time Activity
09:30 10:00 Introduction & Groupings
10:00 11:00 Session 1
11:00 11:30 Break
11:30 13:00 Session 1 (continued)
13:00 14:00 Lunch
14:00 15:00 Session 2
15:00 15:30 Break
15:30 16:30 Session 2 (continued)
16:30 17:00 Closing Reviews
17:00 End
Day is split into two sessions, morning and afternoon.

11. Tea & Coffee
Available all day, just opposite the door at the back.
My suggestion is to keep cups on the floor, to reduce the risk of spilling drinks on laptops and other devices.

12. Lunch
Lunch is free, and will be served between 1pm and 2pm. Available just outside the room.
If you have dietary requirements and you can’t find the right food, let me know. Everyone else, please stick to the main selection food.

13. Toilets
Ladies just outside the door.
Men downstairs, in the same place.
Disabled downstairs by the mens, or through The Junction and go straight on.

14. WIFI
Network: metNet
Login: On your badge
The university has provided WiFi codes to be used throughout the duration of the event, and you should find this printed on your badges. You should have got these
when you registered this morning.
Unfortunately the wifi won’t work with a proxy, so you won’t be able to use that.

15. WIFI
Google (Public DNS)
8.8.4.4
8.8.8.8
Open DNS (Public DNS)
208.67.222.222
208.67.220.220
If you’ve been to an event like this before, you’ll know that one of the usual problems is that of wifi connections.
If you have difficulty connecting to a website, and you know how, try changing your network connection to use public DNS. On screen are the Google and Open DNS
IPs.

16. Cables
Trip hazard: Extension leads, device power cables.
We have some plug adaptors by WP Engine

17. Feel free to switch
teams between
sessions
You don’t have to stick with the same team all day, but please only change at lunchtime between the two sessions.

18. Teams
• Accessibility
• BuddyPress
• Core
• Community
• Design
• Documentation
• Flow
• Meta
• Mobile
• Polyglots
• Support
• Themes
• Training
• TV
We’ve got team leads for half of these teams, and they are going to do a 1-2 minute introduction about their team.
Rian (Accessibility)

19. Accessibility
Rian
Henry (BuddyPress)

20. BuddyPress
Henry
John (Core)

21. Core
John
Tammie (Design)

22. Design
Tammie
Tom (Meta)

23. Meta
Tom
Taco (Polyglots)

24. Polyglots
Taco
Sarah (Themes)

25. Themes
Sarah

26. Other Teams
Community, Documentation, Flow,
Mobile, Support, Training, and TV
No pre-assigned team lead, but we can help you get started with them, and anyone can step up to oversee the group for today.

27. Community
Community: This team oversees official events, mentorship programs, diversity initiatives, contributor outreach, and other ways of growing our community.

28. Documentation
Documentation: This team is responsible for all things documentation, including the Codex, handbooks, developer.wordpress.org, admin help, inline docs, and other
general wordsmithing across the WordPress project. Needs help with HelpHub.

29. Flow
Flow: The flow team patrols flow across the entire WordPress ecosystem on every device they have at hand. They test, document, and report on the WordPress user
experience. Flow can follow the Design team.

30. Mobile
Mobile: They design and develop the iOS and Android WordPress apps.

31. Support
Support: Answer questions in the support form and on the #wordpress IRC channel.

32. Training
Training: The training team creates downloadable lesson plans and related materials for instructors to use in a live workshop environment.

33. TV
TV: They approve and publish all videos on WordPress.tv as well as helping WordCamps with video post-production and captioning and subtitling of published videos.

34. Groupings
Show of hands for each team.

35. Teams
• Accessibility
• BuddyPress
• Core
• Community
• Design
• Documentation
• Flow
• Meta
• Mobile
• Polyglots
• Support
• Themes
• Training
• TV

36. Getting Started
If you’ve got a team lead, then they can suggest how to get started, but you could also find out yourself.

37. Go to
make.wordpress.org

38. Pick the group you
are interested in
You’ll see white boxes, one for each team.

39. Look for Handbook
or Get Involved
section
Linked across the top blue section, or in the sidebar.
Mobile team links to GitHub.

40. “Getting Started at A
Contributor Day”

41. New Contributor
Session
Because some of the teams will require you to be working on a live copy of WordPress, we’ve got a session for new contributors, that John is going to run.
Igor will help with installs.

42. Team Locations
Approx!
Upstairs: Accessibility (L), Core (L) (and New Contributor Session), Design (L), and Flow.
Downstairs: Polyglots (L), Docs, Support, BuddyPress (L), Themes (L), Meta (L), Mobile, Community, Training and TV.

43. Upstairs

44. Downstairs
Breakout room 4 below this one.
Breakout room 1, 2, 3 are the glass-fronted rooms.
Looks for signage.

45. If you’re not sure,
ask!
Ask your team lead, ask me, ask the relevant group on Slack.

46. Any Questions?
Ask me later: @GaryJ

47. Let’s Get
Contributing!