My Talk Proposals for Open Source Bridge

Update, April 29: I’m excited to share that both of these proposals were accepted. See you soon, Portland!


I submitted two proposals to Open Source Bridge, an annual conference in Portland, Oregon, for “open source citizens.” The call for papers is now closed, but they let anyone leave comments on proposals that are private to the conference organizers. If you have any feedback on these, or have seen me speak before, it would be awesome if you could leave a comment. Here they are:

Extreme Software Portability as an Art Form

Writing portable software is hard. Throw in thousands of bad and worse shared hosting configurations, a decade of technical debt, the need to cater to a sprawling ecosystem, and PHP — and you have WordPress. We’ve found breaking changes harm our community and unfairly punish our users, so we don’t make them. But that doesn’t mean we don’t innovate or evolve — we’re just forced to get really clever. And it works, with adoption continuing to soar.

Trust, Community, and Automatic Updates

WordPress shipped in October what is perhaps its most polarizing feature ever — automatic updates in the background of self-hosted web software, on by default and no easy way to turn it off. In most open source communities, this would be cause for open revolt. Learn how through trust, communication, and a steadfast commitment to its philosophies, the WordPress core team convinced a skeptical community to go along, even if it meant users giving up some control.

WordPress contributors Mel Choyce and Aaron Jorbin also both submitted proposals: My Journey into Open Source Design and Modernizing a Stagnant Toolbox.

Published by

Andrew Nacin

Lead developer of WordPress, living in Washington, D.C. Follow me on Twitter.

One thought on “My Talk Proposals for Open Source Bridge”

  1. Both topics would be outstanding, but the one I would really like to here more about is the idea of trust. In the end, major brands are about trust; the consumers’ trust that the products will be of certain quality, that they will be fairly priced and that the company will be there to support the product (or service) during those times when there are problems. Trust is also important when a major change (like the automatic updates mentioned above) is implemented. Loss of trust can be catastrophic to a company or the open source movement. Would really like to hear more about Andrew’s perspective on this topic.

Comments are closed.