Support Updates To & From Forks

[DBNess]

Let's figure out a structure that allows:

1. Fork owners to make changes to the Talks I Want to Give template, including adding themselves to the Talkers list (e.g. Add Vanessa Hurst to the list of Talkers #2)
2. Sasha (@sursh) to make changes to her personal Talks I Want to Give files that do not overwrite fork owners who want to keep their templates updated.

(Note: this discussion began in #2)

[DBNess]

Idea: Maintain master branch as template, personalized individual branches for our own talks.

E.g. In DBNess/talks-i-want-to-give, I maintain both a master branch that I routinely update from sursh/talks-i-want-to-give and a personal dbness branch where I put my own Talks I Want to Give. I also display my personal dbness branch as default on GitHub for gathering feedback.

[lhagemann]

what about a separate file "Talkers List" ... which is what is merged via PRs, thereby allowing forks to have their own individual ReadMe and other files. For example I've added a bio.md file to my repo.