Repository name isn't helpful when forking

[freakboy3742]

The name of the pyvideo/data repository is exceptionally generic - while it makes sense in the context of the pyvideo account, if a potential contributor forks the repository into their own Github account in order to make a contribution, they end up with a "/data" repository that isn't especially meaningful:

While an end-user can rename the repository once they've forked it, it would be better as a user-experience if this step wasn't required.

Suggested name: pyvideo-data.

[redapple]

Thank @freakboy3742 for bringing this up. +1 I've been cloning to a custom pyvideo-data/ folder myself

[Daniel-at-github]

It's a good point. The repo name it's harcoded in a lot of places:

• Git submodules
• Internal scripts
• Travis
• ...

If we rename the github repo and add a symlink pyvideo-data => data... will travis and the submodules work?

[freakboy3742]

Yes - I imagine there will be plenty of changes that need to be made in the pipeline, and there will be some friction for any users that have an upstream remote in their own checkouts. The question (to me, anyway) is whether the temporary friction associated with making the change exceeds the long term benefit to contributors of having a "better" repository name. I'll leave that up to project maintainers to decide if that's a worthwhile cost.