Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

repo : upcoming transfer to ggml-org #11801

Closed
Feb 11, 2025 · 3 comments · 8 replies
Discussion options

Summary

Transfer repository ggerganov/llama.cpp to ggml-org/llama.cpp

When: 15-16 Feb
Location: https://github.com/ggml-org/llama.cpp

Important

New llama.cpp package location: ggml-org/llama.cpp
Update your container URLs to: ghcr.io/ggml-org/llama.cpp


All git commands and external links should continue to work as they do now since Github will automatically redirect them. But to avoid confusion it is recommended to update your remote urls after the repo is transferred:

git remote set-url origin https://github.com/ggml-org/llama.cpp

The existing collaborators will be automatically transferred to the new repository.

TODO:

You must be logged in to vote

Replies: 3 comments · 8 replies

Comment options

The repo at https://github.com/ggml-org/llama.cpp doesn't yet (51 minutes after your message) exist, and the https://github.com/ggml-org site says "ggml.ai" not "ggml.org" but https://github.com/ggml-ai doesn't exist (ya might wanna grab it), but anyway congrats and long live gglml.ai/org!

Update: 👍

You must be logged in to vote
5 replies
@ggerganov
Comment options

ggerganov Feb 11, 2025
Maintainer Author

Thanks! The https://github.com/ggml-org/llama.cpp repo will appear after the transfer is completed.

@d-kleine
Comment options

What will happen to the ggerganov/llama.cpp repository, will it be archived or deleted?

@ExtReMLapin
Comment options

It will be transfered, are you even reading @d-kleine

@d-kleine
Comment options

Apologies for not being versed with repo transfer. I just wanted to clarify what will happen with ggerganov/llama.cpp repo once moved because that has not been explicitly stated. Also the Transferring a repository doc does not clearly say what will happen with the original repo on GitHub, if it remains visible there or not.

@ExtReMLapin
Comment options

@d-kleine There is no such thing as "original repo", because it doesn't get duplicated/removed, it gets moved.

It's like selling your car and your wife asking "What will happen with the original one !" well it's not there anymore, but github (for the repo, not for your car) will automatically place a redirection to the new URL.

The same thing happen when you rename your repository, using old link redirects to the new one automatically

Comment options

ggerganov
Feb 15, 2025
Maintainer Author

The transfer is now completed.

There seems to be one problem though - I am not sure what to do about the llama.cpp package:

https://github.com/users/ggerganov/packages/container/package/llama.cpp

It seems to be attached to my personal account. Should I create a new package on ggml-org? If I do so, then anyone who is using the containers from the above package would have to change to the new ggml-org package - is that correct?

cc @ngxson this might affect HF inference endpoints

You must be logged in to vote
2 replies
@ngxson
Comment options

ngxson Feb 15, 2025
Collaborator

It seems to be attached to my personal account. Should I create a new package on ggml-org? If I do so, then anyone who is using the containers from the above package would have to change to the new ggml-org package - is that correct?

I think we can publish to both ghcr.io/ggerganov/llama.cpp and ghcr.io/ggml-org/llama.cpp for a while, I don't know (yet) how it can be done but I'm sure it's possible and cost no extra upload time for the CI. This should allow a smooth transition, then we can disable the registry under ggerganov in the future.

@ggerganov
Comment options

ggerganov Feb 15, 2025
Maintainer Author

Ok, let's try to figure out how to publish to both registries and I'll put a notice in the README to start using ghcr.io/ggml-org/llama.cpp. Hopefully this would be enough visibility for people to switch over.

Comment options

I noticed that after the repo transfer Roadmap link in README.md doesn't work anymore:
https://github.com/users/ggml-org/projects/7 - new link leads to 404
ggml : roadmap - old link still works fine

You must be logged in to vote
1 reply
@ggerganov
Comment options

ggerganov Mar 4, 2025
Maintainer Author

Updated the link back to ggerganov/projects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
6 participants
Morty Proxy This is a proxified and sanitized view of the page, visit original site.