Call for Maintainers

[sstephenson]

Hi everyone,

My plate’s been full with other work for the past year or so, and I haven’t given Bats the attention it deserves. I’m sorry about that.

I’m looking for one or two people who’d like to step up and take over maintenance of the project.

Your first task would be to work through the major outstanding issues and ship a solid, stable Bats 1.0. I’m happy to work closely with you on prioritizing the work and answering any questions you have about the code base.

Beyond that, I’d leave the future direction of the project up to you.

Please use this thread to nominate yourself and tell me why you’d like the job. Let’s get a conversation going.

Thanks!

[mislav]

/cc @ztombol @jasonkarns for 👀 since I know they are big users of Bats.

[schrepfler]

So what's the plan, move to a dedicated github space and make it more of a community effort? Having bats and the assert library merged together or as a parallel bats/bats bats/batslib and optional community modules?

[sstephenson]

To reiterate, the short-term plan is to ship Bats 1.0, and the long-term plan is to hand over future decisions about the direction of the project to the new maintainer(s).

[jasonkarns]

I'm able and willing to help maintain bats. However, I am not able to be the lead maintainer.

[compwron]

I use eco but not bats so I am not useful here, but would using something like https://jazzband.co/ help?

[ztombol]

I would love to help out. My other responsibilities (job huntung etc.) will definitely not let me take part as much as @jasonkarns (judging from his excelent activity over at bats-core, bats-assert and bats-docs), but I will still help as much as I can.

[cinterloper]

Id like to help out

[kaos]

I'm not very well known to you, but have used bats in a semi-large project at work, which I hope we'll be able to open source some time in the not too far future (read as "hopefully later this year, or maybe sometime during 2017").

As such, I'd like to see bats prosper, and would love to be a part of making that happen.

Edit: Oh, and as reference on previous bash work, the only thing I have to show for is my experiments with ticktick which I made a rather big rewrite of to resolve some hard to fix outstanding issues.

[nstrug]

Hi, we're making extensive use of BATS at Red Hat, both for internal testing and for use on customer projects involving Red Hat Satellite and CI. I would be very happy to take over maintenance of the project. I'm also pushing for it to be officially shipped in RHEL which would get more QE resources etc behind it.

[schrepfler]

That's a great news, will you ship only core bats or also the matcher libs in separate packages?

[ztombol]

Nice! Looks like we're gathering the manpower Bats needs!

I've been going through the issue tracker and been writing up a list of issues, features and annoyances that come up over and over again and we could look into addressing as we move towards 1.0. I'll post it here as soon as it's ready. Probably on the weekend, or early next week.

@schrepfler Do you mean the bats-* libraries? I wouldn't bet on it. I still think they're better off as a separate install. But we can certainly discuss it again.

[schrepfler]

Of course they can be separate, I meant more of a question for @nstrug, are they going to ship bats-* libs as installable packages/rpm's?