When everyone is text its easy to endow more powers to them than you
realize. A quick frolic through the svn logs will quickly establish
the ones that are all talk from the ones that are all walk.

For those whom don't know,

SVN is to open source software as a wrench is to a plumber. Essential.
Why? Consider this scenario, your driving down the street and you come
to an intersection. The street light is out and crashing isn't one of
your fondest hobbies so you'll be waiting for a nod from the other
drivers before risking your fenders. This is not a very effective way
to manage a valuable resource such as an intersection.

Open Source Project Code may not be an intersection but its certainly
a resource we don't want to crash with. Codewise, that would mean not
writing over anyones changes. So, how can a vast team of international
software developers possibly cooperate to write good software?

The answer is a wonderful piece of code specifically designed to
prevent such collisions. Subversion aka SVN is what is known as a
Source Code Management system. A software project is in good hands
under its watchful eyes for all changes that are ever made are saved
and checked for conflicts. Coders whom submit code to the system can
be sure they aren't stepping on anyones toes because the system won't
let conflicting code be accepted until its adjusted.

Confused?

Suppose, your standing in the lobby of a very busy building. You would
like to get to your favorite floor. Its the same floor your wonderful
significant other happens to be on. The elevator door opens and you as well
as a dozen other hurried trekkers file in. Soon all the buttons are bright and glowy with the different destinations of your newly acquainted travel companions.

Being the contemplative person that you are, you pause for a moment and contemplate how the elevator is about to handle its task. I group of people have demanded it take them to each of their own destinations and it is but a humble single machine. The answer? It takes turns of course. And its the same way with SVN. Coders commit their code in turn and can thus check out what other coders have written along the way.

That way, the code base grows and the conflicts are kept to a minimum through good communication and organization. Thus, it goes without saying that having some good Source Code Management Skills is vital to working in the Open Source World. I'd highly recommend starting the journey if your not already an SCM traveler.

Life's better in the source code. You get to play with the newest before
its new. You have passage into the inner workings of the juggernauts of digital tech. And in my opening case, I mentioned that I was checking
the svn log. Developers whom commit code leave notes as to why they did what they did. Even if you don't code at all, reading the log can give you valuable insights as to the health and evolution frequency of an Open Source Project. If nothing else you'll start to get a sense for how work proceeds with an open source project, and how much effort is put into the software every single day.

Leave a note if you would like me to create a SVN movie so
you too can enjoy the wonders of the source code spectator world.
The more response the more likely things happen. :D

Notes
Words that should be words...

glowy

everytime

How do you suppose "anytime" became a word?
People made mistakes everytime and it stuck.