Description
CUE has moved to a new home! The cuelang/cue repository (this repository) and other cuelang/* repositories have moved to the cue-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!
- Visit https://github.com/cue-lang/cue;
- Click on the star icon in the top right, as usual;
- Tweet/encourage your friends who might have starred the original project to do the same!
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 of cuelang.org/go/... packages will continue to work, and historic versions of CUE have been retained.
Some users will be affected in the following scenarios:
- Users who manually install from GitHub release assets must now reference releases in the
cue-lang/cuerepository. All historic releases have been migrated, but new releases will only exist in thecue-langrepository. - Installing CUE via Homebrew now uses a different tap location:
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. - Users will need to subscribe to issues/discussions that have been migrated to the new repository. Because we have not transferred the CUE repository from
cuelang/cuetocue-lang/cue(see FAQ) we needed to recreate issues/discussions using ourcueckoobot 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/cuerepository 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. - Links to
https://github.com/cuelang/*endpoints will need to be updated tohttps://github.com/cue-lang/*. For convenience,cuelang.org/issue/NNNautomatically redirects to the corresponding issue numberNNNin 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:
- The CUE project now requires a Developer Certificate of Origin for contributions.
- Code review has moved from googlesource.com to GerritHub.
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 to cue-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 at https://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 to cue-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:
- Visit https://github.com/cue-lang/cue;
- Click on the star icon in the top right, as usual;
- Tweet/encourage your friends who might have starred the original project to do the same!
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 the cueckoo bot to recreate issues/discussions with the same issue/discussion number. However, this means that all issues/discussions currently have cueckoo 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 time cueckoo 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 via proxy.golang.org and verify via sum.golang.org.
How can I find issues/discussions that I created/commented on?
Migrating the cuelang/* repositories to their new home, we used the cueckoo bot to recreate issues/discussions with the same issue/discussion number. However, this means that all issues/discussions currently have cueckoo 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:
is:issue is:open "Originally opened by @gopher"
Similarly, the following discussion search query finds all comments/replies by previously created by the @gopher user:
"Original reply by @gopher"
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.