On Tuesday, September 16th, I attended my first dev event, a meeting of the Rochester Python User Group, or RocPy, with my HFOSS Dev class.
The meeting started with an overview of what the group is, what they do, and some of their philosophies, since the class brought in so many new faces. They also gave a shout out to some other developer organizations in town: LUGOR, the Linux User Group of Rochester, and Interlock Rochester, a local hackerspace/makerspace. One of the RocPy regulars discussed some Python articles he had come across. I found the one on "Unpythonic Python" particularly interesting.
Ryan Brown (ryansb) gave a talk on the open courseware on which the HFOSS Dev class is deployed. The courseware is deployed via OpenShift, and can be found on GitHub.
Several shorter lightning talks also took place.
Ross Delinger (rossdylan) gave one warning not to push your .git directory to production. He demonstrated how one could reconstruct your source code from your .git. This could theoretically have negative repercussions if you are working on a project that isn't open source.
Remy Decausemaker (decause) demonstrated software that uses a Markov chain to mix two or more text sources and produces (somewhat) readable result, often to hilarious affect. Remy uses this software for wupotus.tumblr.com [NSWF], which mixes Wu Tang Clan lyrics and Barack Obama speeches. It is also used for kingjamesprogramming.tumblr.com, which mixes the King James Bible, Structure and Interpretation of Computer Programs, and Why's Poignant Guide to Ruby. The source code is available on GitHub.
Liam Middlebrook (Loothelion) showed a Python script that he created that creates an issue on the GitHub repositories of projects that don't have licenses encouraging the maintainers to create a license. The source code for the script is on his GitHub.
Of course, there was a shout out for the Software Freedom Day hackathon at RIT.
Overall I enjoyed the experience; I'd definitely go back. In the future, I'd like to be able to contribute something, such as a lightning talk. A lesson learned for the future, for RocPy and probably other dev events, is to bring my labtop, so I can be in channel.