godownloader looking for maintainers

[binkley]

• Yes, I'm using a binary release within 2 latest major releases. Only such installations are supported.
• Yes, I've searched similar issues on GitHub and didn't find any.
• Yes, I've included all information below (version, config, etc).

Version of golangci-lint

$ ./bin/golangci-lint --version
golangci-lint has version 1.24.0 built from 6fd4383 on 2020-03-15T11:38:02Z

Config file

$ cat .golangci.yml
cat: .golangci.yml: No such file or directory

Go environment

$ go version && go env
go version go1.14.2 linux/amd64
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/binkley/.cache/go-build"
GOENV="/home/binkley/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/binkley/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go-1.14"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go-1.14/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/binkley/src/go/foo-go/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build928247667=/tmp/go-build -gno-record-gcc-switches"

Verbose output of running

N/A

This QUESTION isn't about any issues with golangci-lint per se. I was perusing the download script (curl -sSfL https://raw.githubusercontent.com/golangci/golangci-lint/master/install.sh | sh -s), and see it is generated by godownloader. Curious, I looked at that project on GitHub, and see:

Call for Maintainers [of godownloader] created Nov 19, 2019

There's a lot of discussion there, including:

1. Is godownloader actually moving to unmaintained?
2. Would moving to, or merging with, goreleaser be better?

I filed this issue to get a view from golangci-lint on changing the generator of the download script, or using a bespoke script. I love shell and code generation, so my curiosity is piqued.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[rcjsuen]

I also noticed this error. I see now that the new installation instructions uses install.sh from GitHub directly so will be replacing the old link with that instead.