Call for maintainers

[bootstraponline]

It'd be nice to have more maintainers for Slather. If you've contributed in the past & are interested, comment here.

[ksuther]

I'm lightly paying attention to issues and PRs that are filed.

It seems like many of the issues are now related to some sort of coverage problem outside of slather, but the issue gets posted here because there's not really any great way of figuring out coverage problems otherwise. I'm not sure if there's any way we can improve error messages or the read me to help with that.

[ksuther]

I've been added to the RubyGems owner list so I can perform releases now.

Other than general maintenance, here are some things that slather could use in the future:

• Remove gcov support for Xcode 5 and 6. This is a breaking change, so we'd have to go to slather 3.0. Xcode 7, 8, and presumably 9 use llvm-cov so there's no reason to keep dragging the old support forward.

• Better binary matching and more verbosity in terms of exactly slather is searching and what binaries it is matching. Maybe something like merging --binary-file and --binary-basename into a single --binary parameter that can take an exact path or perform pattern matching. We can also make it clearer that multiple binaries can be matched at once. Most issues people have are with the initial setup and binary matching.

• Support multiple coverage services in one run (Is there a way to have multiple coverage services? #133).

[serges147]

@ksuther Do you know is it possible to get "conditional" coverage as well? Currently I see always 100% for the metric. Only "files", "classes" and "lines" are available.

[BrunoMazzo]

I've done a coverage implementation for the Xcode groups on a fork. I still have to organize the code, but it is already working. I had not done a PR because I thought the project had died, but now I'm going to test a little more and then do the PR.

[ksuther]

@serges147 Sorry, forgot to reply to this. Conditional coverage isn't available as far as I know. I believe llvm-cov will show branch coverage in colorized output, but I don't think slather is parsing it.