Project status

[ernado]

Hi! Currently most of maintainers and project author are out of capacity to actively address issues.
I will update this status weekly until further notice.

I will try to explicitly allocate some resources, but I'm not sure that it will be enough.
While this issue is still pinned, new feature requests and PR's with new features (+ new linters, etc) are mostly frozen. I will continue efforts to stabilize project via fixing bugs, OOM-s and other major issues.
Please don't close existing PR's, they will be reviewed eventually.

Any help with issue triage and debugging (e.g. investigating issues and providing draft solutions) will be very appreciated.

Sorry!

UPD: Known major issues

• CircleCI 4GB Limit OOM Kills #1012 (very high memory usage, please disable unused linter for workaround)
• Homebrew version is outdated #1026 (homebrew version is out of date)
• Can't run linter goanalysis_metalinter 1.24.x: failed prerequisites #995 (doomed failed prerequisites error with cold cache)

[ernado]

UPD: I've allocated some time and started maintaining. Also I'm looking into ways of golangci.com revival for OSS projects, but no ETA.

Please treat the current situation with understanding, I'm still gaining traction.

[nashikb]

FYI, you'll probably want to make sure tests pass before committing to master. In theory everyone should be using a tag, but a lot of people don't and a broken master branch isn't ideal either way.

[ernado]

Currently master is OK, FOSSA is just reporting some kind of false-positive.

[ernado]

Project is stabilized as per v1.25.0, please upgrade.

[agnivade]

Thanks @ernado. Much appreciated ! If you would be open to external sponsors for your project so that you can allocate more time, feel free to let me know if I can help somehow.

[jirfag]

My current focus is to fix the lack of maintainers and their time. What's changed:

1. I've built the guide for contributors.
2. All issues created the first time by a contributor get a help from a bot boring-cyborg with a link to the contribution guide.
3. All contributors after the first PR get merged are invited into GolangCI organization into this team. This team has write access to golangci-lint repository.
   To ensure stability I've made a master branch protected and required CI checks to pass and approved code review before merging.
   So, any team member can approve pull request and merge them when checks pass.

4. I've invited into the team ~40 contributors manually with >= 2 commits in the repository.
5. I've built the core team. I'm going to list team members, write docs about them, etc.
6. I've connected dependabot to automate dependencies updating.

[jirfag]

@twpayne @theckman @iwankgb @bombsimon @ryancurrah @dixonwille @viktorasm @tetafro @uudashr @barthr @LukeShu @sayboras @lopezator @NiseVoid @zchee @tommy-muehle @nakabonne @ksoichiro @ewohltman @JohnStarich @vovapi @tdakkota @saschagrunert @rung @proton-ab @kortschak @jfrabaute @gsora @elliots @diegs @cezarsa @cblecker @beono @benpaxton-hf @be-b10g @ashanbrown @aneeshusa @amenzhinsky @a8m @to6ka @matoous

thank you for all your contributions. I've invited you into the GolangCI organization (check it here). After accepting the invitation you can label issues, review pull requests, and merge approved pull requests in the golangci-lint repo.
The contributing guide is here.

[ldez]

The problem is fixed: the maintenance of golangci-lint is now stable.