I work for a community college in their IT department. My job is paid for by tax payer dollars, so it is my opinion that all my work should be publicly accessi

I work for a community college in their IT department. My job is paid for by tax payer dollars, so it is my opinion that all my work should be publicly accessible. My boss agrees with me on this. As such, I've done very little that can actually be useful outside of our scope of work. Whatever I can though, I either blog about in the form of a tutorial/how-to or publish code on github (only 1 project so far). I like the idea of writing blog posts/how-tos which can double as internal documentation. Right now though, I'm working on trying to develop a consortium of other like-minded individuals in which we can brainstorm ideas, implement them in open source tools, then distribute them in the various forms -- either VMs, puppet manifests, docker templates, openshift gears, etc. The idea is to lighten the duties for the typical sys admin and make it easier for smaller schools to implement highly tested, rigorous deployments with minimal insight on the actual workings. It's amazing how much academia suffers from large corporations/consulting firms that gouge these smaller schools based solely off the fact that they can because they lack both qualified individuals as well as competitive salary offerings.