Project stewardship?

[stephenreay]

Let me start off by saying that I am very grateful to Moz for open sourcing Qless. Plenty of organisations would never do so. So thank you, and please understand that I simply want this tool to be the best it can.

Having said that, the inactivity is disappointing, and as someone attempting to contribute, quite frustrating too. Is this project still actively used by Moz (the organisation)? If so, is anyone (either an individual or a team) responsible for maintaining it?

Right now, across this 'core' repo and the various language bindings there are over 100 open issues and PR's - many of which are years old.

In several cases, @dlecocq has approved PR's but they're never merged.

In several more cases, a relatively small amount of work might be required to either fix an issue, or bring a non-satisfactory PR to a point where it can be merged - but without a reasonable expectation of it being merged, who is going to bother?

Cheers

Stephen

[sethhochberg]

Very interested in knowing the same. I've used Qless on prior projects and loved it, and my team is currently working through an evaluation process of spinning up a new project possibly using Qless, but I'm a bit nervous about the general inactivity.

If maintainers are needed, thats a different discussion and one we'd be open to having with whomever is left from the current maintainers group.

[bak1an]

Same question here. What would it take to bring a little bit of life back into qless projects?