Repository name isn't helpful when forking

Open
#707 3 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
25/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
github
Domain
developer-experience

Research direction

No files, tests, or code entry points are mentioned. Review the repository settings and GitHub's fork-renaming behavior, then confirm whether the repository can be renamed from data to pyvideo-data without disrupting existing links or contributors.

Written by the indexing model from the issue text.

Description

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:

screen shot 2018-12-03 at 8 32 01 am

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.

Dominant language
Python
Stars
486
Forks
290
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pyvideo/data

All issues in pyvideo/data

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.