I’m a regular public speaker on free software, licensing, and software development. Recent talks include:

Machine Learning and Open Licensing: An Introduction for Attorneys (FSF-E Legal Network Summit 2017)

A very high-level introduction to machine learning for attorneys, and the legal challenges it may bring to us in the near future. Each of the last 10-12 slides could be an individual paper in and of themselves.

Free as in…? (Free Software Foundation Libre Planet 2016)

Thinking through the FSF’s Four Freedoms as a work of political philosophy, especially in light of the capability approach of Sen and Nussbaum.

Don’t Try This at Home: Very Open Platforms (Monktoberfest 2015)

The Bavarian Beer Purity Law, HTML, Wikipedia templates, and what they have in common.

Trademarks for Open Collaboration (Linux Foundation Collaboration Summit 2014)

How trademarks interact with open source. (I’ve given similar talks repeatedly as a CLE.)

Open Data: the Next Frontier for Open Law (Linux Foundation Open Compliance Summit Japan 2014)

Open data is the next area of challenge for open law.

Creative Commons; Open Source Hygiene; (Wikimania 2014)

I gave three talks at Wikimania 2014:

  • An introduction to Creative Commons 4.0 for Wikimedians, with Kat Walsh;
  • Open Source license hygiene for Mediawiki developers, with Stephen LaPorte; and
  • a keynote on how trust and sharing work together.

Open Source 201 (Open Source Initiative DC Symposium on Open Government 2013)

A brief introduction to more advanced Open Source licensing topics for a government audience.

Open Culture, Open Data, Open Source (Wikimania 2013)

On the state of the art in, and tensions between, open source licenses and open data.

From here to there: observations from mass-market Free Software (Free Software Foundation Libre Planet 2010)

Usability, access, and internet services, through the lens of Mozilla and GNOME.

Duke, Open Source, and Free Software (“Technical and Social Foundations of the Internet”, Duke University, 2009)

This was originally planned to be a talk about open source, but in response to student questions much of the talk covered my Duke experience, my blogging experience, and other non-open-source topics.

Pre-law talks

These talks were given before I became an attorney, speaking to engineering audiences.

GNOME in 2010, aka GNOME is people (GUADEC 2006)

The people behind the future of GNOME — everyone and anyone can be the future of GNOME, not just the rockstars.

An Intro To StopBadware.org (Asilomar Microcomputer Workshop 2006)

An introduction to StopBadware.org, with a particular focus on internet governance issues.

Why Everyone Needs A Bugmaster (talk, paper) (Linuxconf.au 2005)

This talk, and formal paper, were given at LCA 2005. It focused on why organizations should want a bugmaster, and what a bugmaster looks like anyway – both in terms of their activities and their skills and temperament.

How GNOME Learned To Stop Worrying and Love The Bug (talk, paper) (Ottawa Linux Symposium 2003)

This talk and paper were given at OLS 2003 and focused on a high-level overview of GNOME QA processes (including Bugzilla) and how they might be useful to other large projects, like the Linux kernel. Should be useful to anyone trying to get their project interested in Bugzilla.

Innovation in legOS and GNOME (MIT Sloan School 2003)

A talk given to Eric Von Hippel’s classes at MIT’s Sloan School of Business. The focus is on what conditions cause communities to form and thrive, and how businesses can work with such communities. Hopefully interesting to anyone curious about the interaction between Free Software and Big Business.

GNOME Organization (slides, audio) (GUADEC 2003)

My GUADEC 2003 talk on the structure and organization of GNOME, focusing on the developer-centric model we have. Probably not of interest to anyone outside of GNOME, but hopefully quite useful to GNOME people interested in GNOME’s structure as it was a decade ago.

Bugzilla Sanity (GUADEC 2002)

A general introduction to best bugzilla practices. It contains a number of GNOME-specific comments, as well as in-jokes, but it should be quite useful for people looking for a start on best practices for developers and bug filers who use Bugzilla.