-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CUE has moved to a new home! #1078
Comments
It's been over a year since this happened, so I think we can close this 🎉 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
CUE has moved to a new home! The
cuelang/cue
repository (this repository) and othercuelang/*
repositories have moved to thecue-lang
GitHub organization, and code review has moved from googlesource.com to GerritHub. This post explains the impact and details of the move for users of CUE and contributors, and covers other frequently asked questions.If you are experiencing any problems as a result of the migration, please open an issue.
Follow the latest CUE announcements and news via our official Twitter account: https://twitter.com/cue_lang.
What do I need to do first?
You need to "star" the project in its new home!
Now read on to check if you are affected by the migration.
How am I affected as a CUE user?
Most users will not be affected by this move.
go get
,go install
and friends will continue to work as before. Imports ofcuelang.org/go/...
packages will continue to work, and historic versions of CUE have been retained.Some users will be affected in the following scenarios:
cue-lang/cue
repository. All historic releases have been migrated, but new releases will only exist in thecue-lang
repository.brew install cue-lang/tap/cue
. The old command (brew install cuelang/tap/cue
) will continue to work, but will redirect to the new tap location and echo a warning about following that redirect.cuelang/cue
tocue-lang/cue
(see FAQ) we needed to recreate issues/discussions using ourcueckoo
bot user (issue/discussion numbers were preserved in this process). Each issue/discussion references the original author, links back to the original, the old issue/discussion then links forward to the new location, all old issues have been closed, and thecuelang/cue
repository has been archived. But this does mean that subscriptions to original issues/discussions have been lost, and users will need to resubscribe to issues of interest.https://github.com/cuelang/*
endpoints will need to be updated tohttps://github.com/cue-lang/*
. For convenience,cuelang.org/issue/NNN
automatically redirects to the corresponding issue numberNNN
in the issue tracker (this is how we refer to issues in the project; others are encouraged to do the same because it remains portable).How am I affected as a CUE contributor?
Contributors are affected by two changes:
For more details, please see the contributing guide.
Why is CUE moving?
The GitHub organization https://github.com/cuelang is part of Google's Enterprise GitHub account. Moving the CUE project to https://github.com/cue-lang gives it a neutral home, and gives the project maintainers more flexibility to run the project and build for its long-term sustainability. We plan to move CUE to a foundation in the near future.
Isn't this going to break lots of stuff?
We hope not! As far as possible we have tested this migration, but no doubt there will be some edge cases. If you do run into a problem, please open an issue.
We chose not to transfer the
cuelang/*
repositories tocue-lang/*
because ownership transfer is a complicated and drawn-out legal process. As such, we also can't have an automatic redirect in place from the old repository to the new repository. The "fork" we have created athttps://github.com/cue-lang
also makes it very clear to users and contributors that there has been a change.The short term pain of losing all those hard-earned stars, people updating links, re-subscribing to issues/discussions etc will be far outweighed by the benefits this new home will bring the project.
Where did all the stars go?
Because we were not able to transfer the
cuelang/*
repositories tocue-lang/*
, we leave behind all those hard-earned stars! At the time of writing we have over 3,180 stars - thank you to all those who have supported the project thus far, we look forward to making CUE even better in this new home!To help CUE settle into its new home, please star the project:
What happened to the "Most helpful" discussion leaderboard?
Firstly, a big thank you to all our contributors who help to answer questions via the GitHub Discussions forum!
Migrating the
cuelang/*
repositories to their new home, we used thecueckoo
bot to recreate issues/discussions with the same issue/discussion number. However, this means that all issues/discussions currently havecueckoo
as the author. This also explains why the leaderboard no longer reflects contributions from other contributors. This temporary anomaly will be just that, temporary, and over timecueckoo
will fall off the bottom of the list!I use the
cuelang.org/go/...
packages as dependencies; what do I need to do?Nothing! The remote import path
cuelang.org/go/...
has been reconfigured to point to the new repository. Module versions will continue to resolve viaproxy.golang.org
and verify viasum.golang.org
.How can I find issues/discussions that I created/commented on?
Migrating the
cuelang/*
repositories to their new home, we used thecueckoo
bot to recreate issues/discussions with the same issue/discussion number. However, this means that all issues/discussions currently havecueckoo
as the author!However, the issues, discussions, comments and replies have all been recreated using structured prefixes. For example, the following issue search query finds all issues previously created by the
@gopher
user:Similarly, the following discussion search query finds all comments/replies by previously created by the
@gopher
user:What will happen to cuelang.org?
cuelang.org will be unaffected by the migration.
For contributors to cuelang.org, the repository behind the site is now hosted at https://github.com/cue-lang/cuelang.org.
The text was updated successfully, but these errors were encountered: