Anyone needs a (long-term) contributor for their open source project written in Go?

mugli · May 30, 2022, 2:57pm

Hey folks,

I’m a backend and infrastructure focused dev interested in Go. Unfortunately I don’t get much chance to write Go at work (it’s mostly a Node.js shop), at least not the amount I want to. So looking to be part of interesting open source Go based project where I can contribute regularly and long term (aka, not hacktoberfest style contribution).

I’m interested in a project that is-

web service based (uses and exposes REST/GraphQL/gRPC based API)
use up to date Go
has focus on maintainability and code-quality (and does good code reviews)
has tons of things to do

I’m based in UTC+1 timezone, and prefer async communication over Slack/GitHub etc.

If anyone is looking for a contributor or knows a project that fits the criteria, lemme know

PS. To clarify, I want to volunteer, not looking for a job. But not sure if there’s a better category in the forum to announce availability.

Dean_Davidson · May 31, 2022, 10:37pm

Not my project, but this is one of the larger OS projects in the go ecosystem and they need a new maintainer:

github.com/gorilla/mux

⚠️ The Gorilla Toolkit is Looking for a New Maintainer

opened 04:21PM - 12 Dec 21 UTC

elithrar

help wanted waiting on new maintainer

The Gorilla Toolkit is looking for a new maintainer (or maintainers, plural). As… the last standing maintainer of the project, I no longer have time to fully dedicate to maintaining the libraries across this project. The major libraries — **mux** (https://github.com/gorilla/mux), **schema** (https://github.com/gorilla/schema), **handlers** (https://github.com/gorilla/handlers), and **sessions** (https://github.com/gorilla/sessions) — are all reasonably mature libraries, but ongoing stewardship around bug triage, feature enhancements, and potential "version 2.0s" are all possibilities. The core asks of any new maintainers: * Have a demonstrated history of OSS contributions. This is important, as you need to be trustworthy: _no_ maintainer is better than an adversarial maintainer! * Ideally, you actively contribute for 3-6 months, I merge after you review, and you gain the commit bit on the relevant repos after that period and/or active engagement on your part. * I transition you to admin of the project. **Note**: I don't expect this to be quick or easy - the **websocket** library, with 16k stars & 15k unique clones per week, has been [looking for a new maintainer](https://github.com/gorilla/websocket/issues/370) 3.5+ years, and has yet to have anyone reliably stick. If I don't have any luck finding new maintainer(s) in the next 6 months or so, it's likely I'll mark these projects as in maintenance mode only and [archive](https://docs.github.com/en/repositories/archiving-a-github-repository/archiving-repositories) the repos. Please keep the replies on-topic.

However, it sounds like you are relatively new to Go so that might not be the best fit. They have also not had a lot of luck finding a contributor who can manage the volume of pull requests/issues needed.