This is part one in a series on What I've Learned About Open Source Project Management.
When I threw the WordPress Plugin Boilerplate up on GitHub a couple of years ago, it was merely meant to be a place for me to share how I [used to] start off most of my plugin-specific projects.
Sure, it’s changed over time (as things do as we gain more experience), but it’s also grown into something that’s received a number of contributions both of which are around ideas for what should or shouldn’t go into the plugin, as well as a variety of pull requests to solve issues – some defined, some not – all from very generous people.
What started off as a small personal project, has grown into a project – although that I still consider small – has a significant enough level of interest and activity that I’ve had to introduce a little bit of project management into maintaining it.
This was obviously something I never set out to do, but it’s something that’s become necessary. So with that said, I thought I’d do a short series on what I’ve learned about open source project management.
Over the next few posts, I’ll cover an idea or two that I’ve learned – at least thus far – that I believe to be cornerstones in open source project management.
