New Direction

[damacus]

Hey y'all,

the Test Kitchen project has been around many years and I feel like it's time to formalise all of the small things that happen behind the scenes of managing an OpenSource project

OpenCollective

We want to be open about the costs of running the project for example; email, DNS & all cost money.

Firstly we'll be creating a new OpenCollective over at https://opencollective.com/test-kitchen. This is where we'll submit expenses for items. This is all in the name of being open.

Kitchen.ci Domain

The history of the project began as a sponsored project within Chef (Opscode) and more recently Progress. The domain currently resides with Progress for financial reason (see point 1). With OpenCollective set-up and funded we can ask for this "back". As Progress want to be a sponsor of the project rather than owner.

Maintainers Overhaul!

Or not, you decide. We have teams per Gem, (e.g. @test-kitchen/busser-cucumber-admins ) though I supect many of these teams can now be reorganised into a maintainers, admins and external contributors (i.e. you're signed into GitHub but not in the org). This one might be the most controversial item on the list, and I'm very happy to have a conversation about it.

Nuts & Bolts 🔩

This then leaves us with a few extra admin tasks to take care of. We'll need shared emails, a password safe, and an account for our bot. So it isn't tied to any one person. And lastly, we'll need to decide who gets RubyGems publish access.

I'd really like to hear from the @test-kitchen/org-wide-maintainers and anyone else interested in this project