Status of the project

[lopezator]

This been quiet for over a month (the last commit is from 14th of July at time of writing):

d2b1eea

Issues & PR's seem to be stacking.

Is @jirfag on a long vacation maybe? :)

Any news?

[pierrre]

Are there other maintainers ?

[lopezator]

AFAIK there aren't, and looking to the https://github.com/golangci/golangci-lint/graphs/contributors dosn't look there is another major contributor other than @jirfag

[ernado]

No worries, jirfag is on vacation and will be available in couple of weeks.

[Helcaraxan]

Thank you very much for the update @ernado. It is much appreciated. 🙂

Given that there are a few relatively critical issues for which PRs have been opened is there any way in which another maintainer / contributor could have a look, merge the fixes and do a 1.17.2 patch release?

I am mostly thinking about the following PRs:

• Make generation of demo.svg deterministic #625 to unblock / fix CI for other PRs.
• fix invalid dependencies #605 (which overlaps with and replaces go.mod: fix timestamp on module replacement for bodyclose #629, update deps; fix go 1.13 #614 and fix go mod problem #583).

and the patch release would also include #594 and #610 that have already been merged.

[pierrre]

I think that #604 is blocking for Go 1.13.
But if we merge #605, I will be able to install from source, with a tagged version.

[laverya]

I think a lot more people are going to start hitting #605 soon, now that Go 1.13 has been officially released. Is there any chance that things could be expedited @ernado?

[jirfag]

Guys, I'm so sorry that all processed stopped because of me being the sole maintainer :( I was on a vacation (thank you @ernado).

To fix it, I'm looking for co-maintainers. Also, I've taken another vacation for the next 3 days to merge all accumulated pull requests, I hope I have time to merge them all.

[lopezator]

Now that @jirfag is back and opened the co-mantainers issue I'll close this. Thanks for the feedback.