Skip to content
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

proposal: dep: move out of #41237

theckman opened this issue Sep 5, 2020 · 2 comments

proposal: dep: move out of #41237

theckman opened this issue Sep 5, 2020 · 2 comments


Copy link

@theckman theckman commented Sep 5, 2020

Hi there,

This is effectively a recreation of #29639, to request another evaluation based on the current state of the world and in relation to this issue: #38158.


Copy link

@mvdan mvdan commented Sep 5, 2020

What has changed since @andybons's comment in #29639 (comment)? That comment clearly outlined that the proposal was rejected, that the repository was going to be archived in the near future, and that anyone is welcome to continue the work in dep via a fork.

That plan is what's being executed in #38158; I don't see a reason to reopen this debate and further delay what has been planned for nearly two years.

@mvdan mvdan added the WaitingForInfo label Sep 5, 2020
Copy link

@andybons andybons commented Sep 5, 2020

Closing as a duplicate of #29639.

As I stated in the original issue:

We will not be transferring the dep repo. It is an important part of Go’s development history and still a useful tool for many. It will remain in the golang organization indefinitely.

That has not changed, even in light of official deprecation.

You are welcome and encouraged to fork the repo if you’d like to continue working on it.


@andybons andybons closed this Sep 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.