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

wireguard-go: remove from tree #41710

Closed
wants to merge 1 commit into from
Closed

Conversation

zx2c4
Copy link
Contributor

@zx2c4 zx2c4 commented Jun 8, 2018

This is very disappointing to submit.

This .nix was accepted into nixpkgs in very poor state, and it took some
efforts to even clean it up to be acceptable. During the process, the
original submitter (and maintainer) was nowhere to be found and did not
participate.

Since then, the maintainer of the package has failed to update it, to
the point where the current version in the tree no longer works properly
with the tools. (We intentionally made some breaking changes while we
were shaking out bugs from the first ever darwin release.) But
probably the maintainer of the package isn't really aware of that.

In otherwords, this seems unmaintained. And for a project that's still
based on snapshots, it seems important to have active interested
maintainers who are using this stuff, following the project, and bumping
releases accordingly.

Therefore, I think the choices at hand are: find a new maintainer for
this, or just remove it. I hope you'll do the former; maybe it will come
down to the latter, which is what this commit does.


As a point of clarification, based on an IRC inquiry: this PR here concerns the wireguard-go package. The wireguard-tools and wireguard-modules packages have different maintainers from this one, and those maintainers have been very on top of things for a long time now. So this PR has nothing to do with those two packages, but rather only wireguard-go.

This is very disappointing to submit.

This .nix was accepted into nixpkgs in very poor state, and it took some
efforts to even clean it up to be acceptable. During the process, the
original submitter (and maintainer) was nowhere to be found and did not
participate.

Since then, the maintainer of the package has failed to update it, to
the point where the current version in the tree no longer works properly
with the tools. (We intentionally made some breaking changes while we
were shaking out bugs from the _first ever darwin release_.) But
probably the maintainer of the package isn't really aware of that.

In otherwords, this seems unmaintained. And for a project that's still
based on _snapshots_, it seems important to have active interested
maintainers who are using this stuff, following the project, and bumping
releases accordingly.

Therefore, I think the choices at hand are: find a new maintainer for
this, or just remove it. I hope you'll do the former; maybe it will come
down to the latter, which is what this commit does.
@zx2c4
Copy link
Contributor Author

zx2c4 commented Jun 8, 2018

CC: @Mic92 @kirelagin

@zx2c4
Copy link
Contributor Author

zx2c4 commented Jun 8, 2018

As an update in activities, I've now emailed @kirelagin in order to direct his attention toward this PR.

@xeji
Copy link
Contributor

xeji commented Jun 9, 2018

closing in favor of #41735

@xeji xeji closed this Jun 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants