It might provide little direct value to your development process, but the real question is, why are you posting this project on the internet? Do you think ther

It might provide little direct value to your development process, but the real question is, why are you posting this project on the internet? Do you think there is a chance it will be useful to others, and that they might contribute back patches that you will find useful? If so, it makes sense to make that as easy as possible. Otherwise you are sabotaging your own goals and putting unnecessary barriers between you and your potential contributors. Sign-up aside, all you would need to do is type "git init" and then set up a one-line script that will do a commit and push it to github. If you want to be nice, you'll type in a message. Voila, you now have a way to: * let people subscribe to your project * automatically maintain and announce your changelog * let them fork your project, make changes, and send those changes back to you as a diff which you can comment on online * merge those changes back into your tree with a single click / command Additionally, while you might be confident managing a single code tree, there are things that filesystems don't do well, like branching. I find being able to try new things and setting them aside for a while is invaluable. It lets me be bold and work on whatever I fancy, without having to worry about what I was doing before. Don't think of git as revision control, think of it as a little robot that lets you do controlled operations on code trees, like you can with files.