Self-nominating for the go-team

[till]

Hi,

not entirely sure what the process is, but I'd like to contribute to the build packs to make the experience smoother.

E.g. I'd like to address some build challenges in go-generate and also work on integrating it into the go-family build pack.

Till

[dmikusa]

That's wonderful. I hope the process is simple. Here's a rough outline...

• For small things/small changes, you can just send a PR. For now, we're a little short-handed, but if you @ mention me I will do my best to help keep things moving.

• Bigger changes, it's best to start a discussion thread first or reach out on Slack. That will give the group a chance to discuss what you're proposing and make sure we're all in agreement on the path forward, before you start work, so we're respectful of your time. If what your proposing is all within one buildpack language family, then this is a good path forward.

• Really big changes would need an RFC. These would typically be things that go across buildpack language families, like if we want to coordinate something across the project. It could also be for things that might result in a major change of direction for a buildpack language family, like "hey, let's consolidate a bunch of buildpacks" or "hey, let's stop supporting XYZ".

As far as contributor/maintainer status. It's merit-based and activity-based, so if you submit some PRs or help out with work on the project, you or someone else can nominate you. The first step is a contributor, then a maintainer. The contributor and maintainer roles are described in our community docs, but in a nutshell, the contributor role is for folks who want to casually commit changes & help with the project, and the maintainer role is for folks who want to be more involved and help shape the future direction of the project.

Hope that helps! Happy to answer any further questions about the process.

[till]

Cool, and fair. I had reached out on the Paketo Slack (Go channel) previously, should I try again?

[dmikusa]

Sorry, that's my fault. I missed that notification. Yes, let's start a conversation there. I've got another individual that is looking to help with the Go buildpack as well. We can all talk and get things moving forward on Slack.