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?

[ztombol]

@schrepfler Right. You even said "packages." Sorry, my bad!

[colourmeamused]

Just posting to ask if there are any updates, since I don't think we have a mailing list for BATS. Like others, I'll chip in where I can (about to have a look at #161 ). But it will be great if the project is maintained by a larger group using BATS like Red Hat / Docker / Chef?

[jubianchi]

I'd really be glab to help here, be it as a reviewer, maintainer or whatever.

[fearphage]

I'd be glad to help out as well.

In reference to pulling all the bats-* under one location, I checked and https://github.com/bats is already taken although not heavily used it seems. I'm not sure if they'd be willing to vacate. I have not asked.

What's the status of additional maintainers? Are there any?

[harschware]

Given the call for maintainers was made 10 months ago and we have add at least one volunteer: @jubianchi, @sstephenson could you grant him maintainer status? Assuming that happens, @jubianchi would you be willing to set up a Google group or something similar for a mailing list? Maybe we can have a discussion there to create an initial list of PRs to merge. I suggest we would bump the current master to an 0.5.0 release (since there has been some commits since 0.4.0) and then identify about 4 or 5 PRs to merge for an intended 0.6.0 to get the ball rolling. All that can get discussed on a mailing list, if we can get at least one person granted the needed privs to get the ball rolling.

[mbland]

FYI: I invite folks to check out the new Bats v1.0.0 release:

https://github.com/bats-core/bats-core/releases/tag/v1.0.0

We've resolved a number of open issues from this original repo, fixed a few more, and greatly improved performance—while maintaining compatibility with the v0.4.0 interface. It should be a drop-in replacement for v0.4.0, more or less; but issues illustrating the contrary are welcome.

[madnight]

@sstephenson please archive this repository and link to https://github.com/bats-core/bats-core

[mandric]

Is there any reason this repository is not archived and linked to the newer one? It's still confusing how it is now.

[DazEdword]

Just another heads up, bats current development status is a bit confusing for someone finding it via Github, so it would really be helpful to archive this repo, or at the very least add a few lines acknowledging the existence of bats-core in this README. Also thanks all involved, it's being really useful! 👍

[xmik]

I agree with @DazEdword, therefore I'm linking this PR here: #248

[ssbarnea]

Yep, please archive it to save people time! It is a small gesture. We did not ask to delete it, only to archive it.