CALL FOR MAINTAINERS

[cheeseplus]

In all caps cause I'd love to let more people in to help on this project cause I know we all love it. Sound off in comments if you'd like to be a maintainer and I'll be adding commit bits in the comings days.

Related to #536

[rickard-von-essen]

I would like to join.

[legal90]

I'd like to join too :)

[bflad]

As a long time user/lurker, I would love to assist!

[tas50]

As a huge consumer of this work count me in

[sethvargo]

Oh me me me

[tiwilliam]

I would love to help

[itmustbejj]

I'll gladly help as well, if you need it.

[cheeseplus]

Ok, everybody in this thread is now a maintainer. We're going by the general Chef RFC rules which is two +1s from maintainers to merge to master assuming no lieutenant vetoes the PR. As of right now I'm really the only lieutenant but we can sort that out depending on who has the most time and/or willpower

[chasebolt]

Count me in if you need more

[rickard-von-essen]

I think we need some sort of guideline on what boxes should contain, which OS/flavors we care about, the general goal of the project etc. So we have something to base decisions on. Otherwise I think there will be some sprawl between boxes and versions and harder to reject issues/PR's.

[cheeseplus]

@rickard-von-essen going to write a vision/roadmap on that front before closing this issue.

[therootcause]

count me in also if you need more.
I maintain a fork, with daily validated .box builds. Among other things, my "interests" are around RHEL7 subscription & vmware tools.
Thank you for this incredibly useful project.

[cheeseplus]

@therootcause we can always use more eyes on PRs and the repo for sure - what is your fork taking care of that we aren't? May be easier to incorporate changes and do some sharing ;)

[cheeseplus]

Closing this now that the MAINTAINERS.md is updated.