Hello all,
I have a couple of small personal projects I've been working on over the years and I was wondering if they would be of use to anyone:
1. nginx configuration generator
N.new('annotalia.com') { proxy(2666) } >> gen[:machine1]
N.new('.eshao.es') { pppr } >> gen[:machine2]
N.new('research.dsoglobal.org') { doku } >> gen[:machine3]
Ends up as a fully configured proxy to port 2666, a domain that supports perl/python/php/ruby, and a doku configuration respectively. It only generates the nginx configuration, but I've found it really helpful to setup my multiple sites. Currently, it supports most normal use-cases (like subdomains, specifying log locations, etc.) as well as specific applications like Wordpress, Rails, and Mailman. And of course, extensible.
An example configuration file can be found at: <http://dl.dropbox.com/u/146184/config.rb>, just so you can get an idea of how concise it is.
- -
2. Puppet configurations
I use puppet extensively to manage all my machines and have a ton of configurations which are accompanied by documentation on setup and any miscellaneous gotchas. Although FreeBSD-exclusive, I put a lot of thought into each file and code elegance (using macros, etc.) which might be helpful to others.
An example manifest can be found at: <http://dl.dropbox.com/u/146184/mailman.pp>.
- -
3. Blogging platform using Etherpad as a backend
I love writing in Etherpad. So much, I made an entire blogging platform which is controlled from within Etherpad. You edit configuration, tags on posts, and posts themselves (in Markdown) in Etherpad and everything gets cached locally as static HTML on the backend.
An example "Etherblog" can be found at <http://annotalia.com>.
- - - -
My assumption is that (1) would be suitable for github, (2) should go somewhere in the puppet wiki/github, and (3) should be discussed with the Etherpad folks first. But I honestly have no clue where to start and even less of an idea of whether these are valuable enough to bother open-sourcing. I do know that all of this needs to be cleaned up and I am only willing to do the work if someone will benefit.
So HN, please lend me your advice on:
* If you would find any of these projects personally interesting or useful?
* How you would go about open-sourcing the projects? Any good guides out there?
* Most importantly, if any of you would be willing to mentor me through the process, I'd really appreciate it. My email is in my profile. Would be great to have someone comment on my code quality and guide me through brainstorming anyone I need to contact, putting something up on github, and publicizing the projects.
Sorry for the long post and thank you for your time!
- Edwin
Recently I started to think along these lines: code not being used and/or worked on is slowly decaying (due to bitrot :) ). Personally i would opt to share even if it's not perfect. Practice makes perfect and that's what you can do by making your work available to others and thus allow them to 'judge' your work. Your question seems to imply that this is part of why you're considering sharing your work. From a practical viewpoint: it might be good to think about maintenance and support, although i presume most open source project first need to be used at all before this becomes problem. I hope this makes any sense.