Added a spooky poem, "Sirits of the Dead" from upstream

This is the unmodified upstream version, which wasn't in version
control. Go figure.

I created a new directory and file, and saved the poem with my
text editor. Then, I used:
  git add spooky_poems/spirits_of_the_dead.txt
to stage the new file. I suppose that I could have also used:
  git add -A
to just stage everything.
Finally, I used:
  git commit
and typed this message.
Modified "Spirits of the Dead" to be less spooky

Although this may be an ongoing effort, these changes are complete
enough to allow the entire poem to still make sense. If this were
code, we would ensure that the commit continues to compile.

I updated the poem with my text editor, then just ran:
  git commit -a
The "-a" option tells Git to autoatically stage any files that
were modified or deleted, This option would not be sufficient
if I added new files too.
WIP: Attempt to make the poem less spooky again

Not sure if this will work...
Revert "WIP: Attempt to make the poem less spooky again"

This reverts commit 16bdc0573c6ecca93d5139de996e8cb98cfecf26.

Oh no! Commit 16bdc05 actually made the poem more spooky.
Reverting by:
  git revert HEAD
Significant revision to make "Spirits of the Dead" more happy

I got in trouble for accidently committing a more spooky version
of "Spirits of the Dead" directly to master. I'll use branches
from now on.

I created a branch by:
  git branch ImprovePoem-Brian
then checked it out with:
  git checkout ImprovePoem-Brian
I suppose I could have just used:
  git checkout -b ImprovePoem-Brian
which would do both things in the same step. Then, I verified that
I was on my new branch with:
  git branch
Finally, I committed the improved version.

I'll share this branch later, so that it can be reviewed by
others before merging to master.
More changes to make "Sprits of the Dead" less spooky, and legal

These changes aesthetically depend upon the previous commit, but are
logically distinct, so I'm keeping this as a seperate commit.

Also added a copyright file to clarify the license of the
now-derivative work. Since this is a new file, simply running:
  git commit -a
will not include it in the final commit. I have to run:
  git add -A
then
  git commit
Merge branch 'ImprovePoem-Brian'

* ImprovePoem-Brian:
  More changes to make "Sprits of the Dead" less spooky, and legal
  Significant revision to make "Spirits of the Dead" more happy

My changes were approved, so I'm merging the branch to master. Since
I'm merging *into* master, I used:
  git checkout master
to get on the correct branch.
Then, since we're using a "branchy" workflow, I used:
  git merge --no-ff --log ImprovePoem-Brian
to do the merge. The "--no-ff" option forces git to create a distinct
merge commit, even if it could just "fast-forward" and put the commits
directly on top of master; this makes the repository more organized
when working with multiple branches simultaneously. The "--log" option
automatically creates a summary message for the merge commit, listing
the first line of all the commit messages in the branch to be merged.
Renamed "Sprits of the Dead" to "Spirits of the Departed"

Git stores the rename / move of a file as a deletion of the old name,
then a creation of the new name. However, Git's tools are smart enough
to realize that this is semantically a rename operation if the content
of the files are identical or even similar.

I have to use:
  git add -A
to stage all of the changes (the deleted file + the new file). Once
staged, Git will start to see change as a rename.

Then I commit normally with
  git commit
Since this is a minor change, I am breaking the rules and committing
it directly to master. Try and stop me!
Update "Spirits of the Dead" to be more pleasant

I'm committing this directly to master. What could possibly go wrong?
Substantial changes to make "Spirits of the Departed" happier
Merge branch 'ImprovePoem2-Brian'

* ImprovePoem2-Brian:
  Substantial changes to make "Spirits of the Departed" happier

Conflicts:
	spooky_poems/spirits_of_the_departed.txt

Oh man, what a hassle! I tried to merge my branch with:
  git commit --no-ff --log ImprovePoem2-Brian
but someone already changed the same lines in master before
I could make this merge.

The good news is that some of the changes we made were identical
and Git is smart enough to resolve this conflict itself. However,
some of the changes needed to be resolved manually.