pros and cons of GitHub forks vs. templates

[JackDougherty]

@ilyankou - I think you've already discovered these pros and cons of GitHub forks versus templates, but I just want to clarify them and make sure we both agree on the best option before going forward with releasing the new version of this and storymaps.

Templates are easier for new users to create multiple copies of our code, and to name them individually upon creation. Forks are limited to one copy, with the same name as ours, unless the user knows how to get around those.

But looking ahead to future users, I see no easy way to do a pull request from a template repo to the original repo it came from. GitHub web interface simply doesn't add the original repo as an option when you click "pull request" in a template. This means that easiest way for future users to update their code is (a) tell them to use GitHub Desktop to move lots of files, or (b) migrate their Google Sheet and media & geojson files to a new template of the code.

Given the current choices, I am fine with sticking with templates, but wanted to check with you to see if we agree.