wikitree-dynamic-tree icon indicating copy to clipboard operation
wikitree-dynamic-tree copied to clipboard

Naming is confusing?

Open sandos opened this issue 1 year ago • 2 comments

I have been disturbed by one thing for a long time, and I have seen no discussion on this, nor any issues raised here!

The naming of this repository is slightly confusing! So this repo contains the code for a lot of apps/views available on wikitree.

"Dynamic Tree" is just one of many applications included in this repository, yet thats the name. I suspect this is what was started with way back, but it always feel like people are talking about one single application when they are mentioning "wikitree-dynamic-tree". For the longest time before diving into this I was super-confused as to why everyone should work on one specific app for hacktober for example.

Same thing with the readme, it talks about the dynamic tree mostly, not exclusively, but still:

This app displays a family tree starting from one person profile at WikiTree

sandos avatar Nov 06 '24 08:11 sandos

As the saying goes: There are 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors, so what's new? :). With hindsight the correct name should probably be tree-apps, or wikitree-tree-apps or wt-tree-apps. The repository owner can change it easily enough. My good friend ChatGPT tells me:

Yes, you can rename a GitHub repository, and it’s relatively straightforward. Here’s how:

  1. Go to the Repository: Open the repository you want to rename.

  2. Navigate to Settings: Click on the Settings tab at the top of the repository page.

  3. Edit Repository Name:

    • In the Repository name section at the top, you’ll see a text box with the current repository name.
    • Update this text box with your new repository name.
  4. Save Changes: GitHub may prompt you to confirm this change. Once you confirm, the repository will be renamed.

Important Notes:

  • URL Redirect: GitHub automatically redirects the old repository URL to the new one, so any existing links will continue to work. However, it’s a good idea to update links and bookmarks with the new URL.
  • Local Git Remote: If you have a local clone of the repository, update the origin remote URL with:
    git remote set-url origin
    

https://github.com/username/new-repository-name.git

- **GitHub Pages**: If you’re using GitHub Pages, you may need to update
the settings if your URL changes.

Renaming does not affect the repository’s content, issues, pull requests,
or settings.

Riël

On Wed, Nov 6, 2024 at 10:31 AM John Bäckstrand ***@***.***>
wrote:

> I have been disturbed by one thing for a long time, and I have seen no
> discussion on this, nor any issues raised here!
>
> The naming of this repository is slightly confusing! So this repo contains
> the code for a lot of apps/views available on wikitree.
>
> "Dynamic Tree" is just *one* of many applications included in this
> repository, yet thats the name. I suspect this is what was started with way
> back, but it always feel like people are talking about *one single
> application* when they are mentioning "wikitree-dynamic-tree". For the
> longest time before diving into this I was super-confused as to why
> *everyone* should work on one specific app for hacktober for example.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/wikitree/wikitree-dynamic-tree/issues/274>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AZWMMSPI2SWAXC46AXT2DQTZ7HHWDAVCNFSM6AAAAABRII2RCGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGYZTOMZYGAYDOMY>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>

udjeni avatar Nov 06 '24 08:11 udjeni

Yes, the repo has evolved well beyond the original dynamic tree (thank you to everyone that contributed new views, updates, etc). A name change is probably warranted. I've put that into our queue to consider.

The README can be edited by anyone working on the repo, so please feel free to add additional information about the other views, rework what's there to be more properly generalized, etc..

bcaseyrls avatar Nov 07 '24 15:11 bcaseyrls