Contributing to WordPress -- WordCamp Savannah 2010

26
Contributing to WordPress Core Andrew Nacin WordPress Core Developer twitter @nacin web andrewnacin.com email [email protected] WordCamp Savannah — August 21, 2010

description

How to Contribute to the WordPress project. Ideas, support, documentation, design, development. Learn about best practices for contributing to an open source project, and some of the development philosophies of WordPress.

Transcript of Contributing to WordPress -- WordCamp Savannah 2010

Page 1: Contributing to WordPress -- WordCamp Savannah 2010

Contributing toWordPress Core

Andrew NacinWordPress Core Developer

twitter @nacin web andrewnacin.comemail [email protected]

WordCamp Savannah — August 21, 2010

Page 2: Contributing to WordPress -- WordCamp Savannah 2010

Make sure WP_CACHE is true. Props nacin.

Page 3: Contributing to WordPress -- WordCamp Savannah 2010

How can you contribute?

Page 4: Contributing to WordPress -- WordCamp Savannah 2010

Ideas

Page 5: Contributing to WordPress -- WordCamp Savannah 2010

Support

Page 6: Contributing to WordPress -- WordCamp Savannah 2010

Documentation

Page 7: Contributing to WordPress -- WordCamp Savannah 2010

Evangelism

Page 8: Contributing to WordPress -- WordCamp Savannah 2010

Testing

Page 9: Contributing to WordPress -- WordCamp Savannah 2010

Translating

Page 10: Contributing to WordPress -- WordCamp Savannah 2010

Design

Page 11: Contributing to WordPress -- WordCamp Savannah 2010

Development

Page 12: Contributing to WordPress -- WordCamp Savannah 2010

How does code makeit into WordPress?

Page 13: Contributing to WordPress -- WordCamp Savannah 2010
Page 14: Contributing to WordPress -- WordCamp Savannah 2010
Page 15: Contributing to WordPress -- WordCamp Savannah 2010

Contributing to open source

• Take constructive feedback.• Don’t take it personal.• Patches welcome!

• Tickets — tasks, enhancements, bug reports • Patches — code, design, documentation • Discussion — comments, weekly chats

Page 16: Contributing to WordPress -- WordCamp Savannah 2010

What makes a great bug report?

Page 17: Contributing to WordPress -- WordCamp Savannah 2010

Our philosophies.

Page 18: Contributing to WordPress -- WordCamp Savannah 2010

Decisions, not options.

Page 19: Contributing to WordPress -- WordCamp Savannah 2010

Preferences have a cost.

• Too many means you can't find any of them.

• They damage QA and testing.

• They make good UI difficult.

• They confuse users.

Do something specific and do it well.

Defaults that work will lead the UI in the right direction.

Page 20: Contributing to WordPress -- WordCamp Savannah 2010

The quality of an interface design is

inversely proportional to the number of designers.

Page 21: Contributing to WordPress -- WordCamp Savannah 2010

If you're too lazy to do the homework and think through the big-picture rationale, I'm too lazy to

add the feature.

Page 22: Contributing to WordPress -- WordCamp Savannah 2010

In the presence of good rationale, maintainers

should be willing to change their mind often.

Page 24: Contributing to WordPress -- WordCamp Savannah 2010

pre-release candidates for 3.0 were downloaded

75,000 times

QUALITY ASSURANCE

Page 25: Contributing to WordPress -- WordCamp Savannah 2010

Follow along! Join us!

• #wordpress-dev on freenode.net• http://wpdevel.wordpress.com• http://core.trac.wordpress.org• wp-svn – mailing list for commits• wp-hackers – plugin and core developers• wp-testers – beta testers• @PatchesWelcome on Twitter

Page 26: Contributing to WordPress -- WordCamp Savannah 2010

Questions?

twitter @nacin web andrewnacin.comemail [email protected]