Spock: Inactive Spock project admins

Created on 7 Jun 2018  路  16Comments  路  Source: spockframework/spock

There are a lot of unhandled and unanswered PR's and issues in Spock. Releases are unfrequent, and sorely missed.

Could the Spock maintainers consider adding more admins to the project, to increase adoption, activity and release rates?

Cc: @ldaley @leonard84 @sbglasius @pniederw

Most helpful comment

Sorry I've been absent these last 4 month due to private reasons. I'll try build momentum again. That being said I was essentially the only active (now again ;) ) member which contributed a bit to the fatigue. Having more people willing to help by reviewing PRs, improving documentation, or testing the current SNAPSHOT builds on as many projects as possible will definitely help to improve motivation. If you are seriously interested in helping out you can join gitter spock channel and message me.

All 16 comments

I agree, there is work on the project and there seem to be fixes which are very nice to have, but no release for over a year. So would there be the possibility of giving some feedback and maybe some reasons of why there is so much silence?

I have started resorting to forking the repos and making the needed changes due to the consistent lack of momentum that revisions are reviewed and merged.

I think it would be better to invite those who wants to contribute to this repo. Forking off will bring confustion to the community. I for one would like to see a momentum going forward

I agree 100%. I was forking out of personal use and necessity because I needed to make some progress on some of my big issues rather than waiting for unknown ETR.

Regarding the popularity of spock I think that being very conservative with changes is a good thing.

However there are a few upcoming challenges that should be tackled in the near future:

  • Someone to sort through and label open issues and pull requests
  • Patch releases: Fixing obvious bugs in a way that does not break the existing API
  • Compatibility with new Java and Groovy versions (so the project keeps its momentum and people do not turn away)

In the more distant future I think that JUnit 5 support and exceptions from https://github.com/ota4j-team/opentest4j is one of the most important aspects that we as a community should try to put together.

Although I'd love to see stable improvements for Spock, maintaining an FOSS project for a long time can be quite tedious and time consuming so it is fairly understandable if a maintainer is not always reacting instantly.

@tburny I agree. The thing is, the admins do not react at all. Not having time is understandable and fine, but no answer for months is worrisome.

I try to squeeze in as much time as I can, but my deeper knowledge of the build process and code base limits me to being active here and not merging pull requests or building the code.

I'll see if I can get a reaction from the other admins.

Cc: @ldaley @leonard84 @sbglasius @pniederw

Completely agree with what's been said up to now. We all realise that working on a side-project is not always easy, but leaving things as they currently are and not merging/releasing is not a solution. I'm pretty sure there will be volunteers that might help with the actual development (with at least some guidance or reviews from the core admins).

Happy to help if developers or documentation writers are needed!

Same here, although not very experienced in open source work I am more than happy to help out :)

I'd volunteer for sifting through all the pull requests and open tickets to at least categorize (priorize?) them.

@tburny I remember we (with @sbglasius and some volunteers) did it at Gr8Conf Europe 2016 to make the release of Spock 1.1 possible (with a good result in the end :) ). It's definitely a good idea (to close duplicates and ensure something is still a problem in master) and maybe @sbglasius as a contributor could be helpful here - there is also a Gitter which were used to synchronize the activities.

Sorry I've been absent these last 4 month due to private reasons. I'll try build momentum again. That being said I was essentially the only active (now again ;) ) member which contributed a bit to the fatigue. Having more people willing to help by reviewing PRs, improving documentation, or testing the current SNAPSHOT builds on as many projects as possible will definitely help to improve motivation. If you are seriously interested in helping out you can join gitter spock channel and message me.

@leonard84 good to see you back. I'll pitch in where I can, but probably most with cheers and encouragements. Let me know what I can do besides that.

For the others who want to help you can check out the https://github.com/spockframework/spock/labels/help%20wanted label.

For the others who want to help you can check out the https://github.com/spockframework/spock/labels/help%20wanted label.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

YaroSpace picture YaroSpace  路  7Comments

robfletcher picture robfletcher  路  7Comments

donbeave picture donbeave  路  5Comments

kriegaex picture kriegaex  路  5Comments

ShunmugamAiyappan picture ShunmugamAiyappan  路  5Comments