“Initial commit” is so uninspiring yet we’ve all committed it somewhere!
I’ve recently found myself creating a noticeable handful of repositories for various projects and it got me thinking: whats in a first commit? It’s the commit that hangs around like a bad smell for years after you make it. It appears in github in that placeholder .gitignore, or in that tiny file that never gets changed. So why think about it?
For the first time in 12+ months I made a code contribution to open source and it feels awesome! I’m delighted to say homebrew now includes PHP 7.1 (less than 48 hours after release).
A lot of hard work goes into FOSS and the communities around it; and most of my time has been community centric and not code. In part its because I’m busy on the community side and partly a sense of cautious sense of ‘someone else would be better at making that contribution’.
Last night I had one of my random project ideas: lets survey PHP user groups across the world and see if there’s any pattern of having a Code of Conduct (and if so, which one).
Whilst not a definitive list, http://php.ug is a great starting place with 242 listed user groups - enough to make a splash I’d say!
Now manually viewing (translating if required) and tracking down a code of conduct for 242 user groups is no mean feat so I put out a tweet asking if anyone had some time to spare.