The induction corrected an assumption I’d been carrying: I thought contributing to WordPress meant writing code. It doesn’t. The project is organized into teams — Core, Design, Polyglots, Support, Documentation, Photos, among others — and only some of them touch the codebase at all.

Three things stuck with me.

The first is that every contribution goes through community review. Nothing is published automatically. Someone else looks at your work and decides whether it meets the standard, which is a very different feeling from pushing to your own repository.

The second is that the contribution is tied to a public WordPress.org profile. This work doesn’t disappear when the semester ends. Whatever I publish stays there, credited, indefinitely.

The third is the one I keep thinking about: the whole model rests on open licensing. Without a clear rule about who can use what, a project this size collapses. Thousands of people contributing to something they don’t own only works if the terms are unambiguous from the start.

That last part connects directly to what we’re studying in this course. A license isn’t legal paperwork you skim past — it’s the thing that decides whether knowledge circulates or stays locked up. For the Photo Directory the license is CC0, which is about as permissive as it gets. When you publish there, you give up your rights over the image and release it effectively into the public domain. No attribution required, commercial use allowed, no conditions.

I’ll admit that made me hesitate. You put hours into a photo — the trip, the waiting, the editing — and handing it over with no strings feels strange at first. But the point of the project isn’t to collect credit. It’s for the material to exist and be usable.

The open question I’m left with is how strict the photo review process actually is. What gets accepted, what gets rejected, and on what grounds. I’ll find that out the hard way and report back.