What is going on with the Workbench module? I haven't read anything new about it for a long time. There hasn't been a release in over a year. Is it dead? Is the whole Workbench Suite dead? That would be a shame.

Comments

hass’s picture

hass commented
Status: Active » Fixed

Very broken. See the critical issues.

dkingofpa’s picture

dkingofpa commented
Status: Fixed » Active

Thanks for your message @hass, but I was hoping to hear an update from the maintainers of the module (Palantir.net). Have they abandoned the suite of modules? Do they have plans for future maintenance? What's a rough timeline for a new version? 6, 12, 18 months? A high-profile module like this needs ongoing care and feeding as well as keeping users informed of it's direction.

bbinkovitz’s picture

bbinkovitz commented

This module suite has definitely not been abandoned but it does demand more attention than we can give it at times. Help QA'ing and patching it is always helpful.

hass’s picture

hass commented

Please add me as o-maintainer.

bbinkovitz’s picture

bbinkovitz commented
Status: Active » Closed (fixed)

The 7.x-1.2 release came out just last week. We are not currently seeking co-maintainers but your continued help filing issues and patches and marking things RTBC is very much appreciated.

Most of the development is happening in the individual submodules of this suite and not in the base Workbench module itself.

hass’s picture

hass commented
Status: Closed (fixed) » Active

If you do not have time to maintain the moule you should grant permissions to others who need this suite now and like to get things fixed. Cases are open here for one or more years and waiting for maintainers review. No progress at all, also for *very* trivial fixes. Look in one of my modules queue, please. Less than 10-15 cases open, nearly zero bug cases - compared to 180 cases in WBM. I spend whole last sunday just to look trough the WBM queue to cose 10 duplicates, tons of support issues, outdated patches and so on and so on.

Something need to happen and change here!

bbinkovitz’s picture

bbinkovitz commented

@hass, a new release of Workbench happened about a week ago. There are currently 19 open issues filed against Workbench, 8 of which are bug reports, and one of which is this issue.

We will let you know if and when we decide to seek out new co-maintainers.

Your help and enthusiasm are very much appreciated.

hass’s picture

hass commented

I mainly have troubles with WBM, but it is the suite, so all of them need help. I know how i pushed for new releases.

hass’s picture

hass commented
Status: Active » Closed (fixed)

Note, this is not really enthusiasm only. I was so stupid to recommend this suite to my customers and need to fix all bugs and usability issues now. THIS drives me crazy.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

Demands and insults will get you no where and continue to have people not prefer to help you. While I understand and want to genuinly apologize for your frustration that things haven't been committed and fixed in a timely manner, they still get fixed when we get to them. We're humans. I also understand you want to help by being able to commit things but we still consider this a Palantir-driven module and not enough resources or attention is a problem we can solve internally and we're not ready to quite open up commit access without a lot of discussion and coordination happening first.

Some things to consider:

  • Workbench is still maintained as it has a recent release that we had been working on for the last two weeks.
  • I see only one issue across all module suite that you participated in that are currently RTBC. The responsibility of testing and marking an issue RTBC does not solely lie on the maintainers. This is why it's Reviewed and Tested by the Community. If you can get others involved in your issues testing and getting them ready to commit and then marking them as so, this can help get things moving more than complaining.
  • It is not anyone's fault except for yourself for recommending the suite to your customers if you consider the modules have such large issues with bug and usability without testing first.
  • You cannot demand to be made a co-maintainer. If you feel a module is abandoned, there is a process you can follow.

Continued harassment in this issue will be referred to the Drupal Community Code of Conduct.