#resque — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #resque, aggregated by home.social.
-
The next #RESQUE consultation hour:
17th of June, 9-10am CEST
https://www.resque.info/news/2026-06-01-consultation%20hours.htmlThe Research Quality Evaluation (RESQUE) framework provides recommendations for responsible #ResearchAssessment for hiring and promotion in #psychology
www.resque.infoThe session will also highlight specific topics such as applying RESQUE in #ClinicalPsychology with the clinical expansion pack.
See also previous post for more links and info:
https://mastodon.social/deck/@jrboehnke/116652740649620274 -
As an example of an application, the #RESQUE assessment is used in the #OpenScience Award of the #OpenScience workgroup of the German Psychological Society's Section #ClinicalPsychology & Psychotherapy.
The workgroup furthers exchange about open science topics in research and practice settings:
https://www.dgps.de/fachgruppen/fgkl/aktivitaeten/ag-open-science/ [German] -
You can read more about #RESQUE and community responses in this excellent issue of #MetaPsychology
https://conferences.lnu.se/index.php/metapsychology/issue/view/297Topic-specific expansion packs are developing, eg., a #PrePrint for #ClinicalPsychology and #PsychotherapyResearch
https://osf.io/preprints/psyarxiv/6gwr8_v1 -
Another opportunity to work w #RESQUE
The Research Quality Evaluation framework provides recommendations for responsible research assessment beyond typical metrics for hiring and promotion in #psychology:
www.resque.infoMaybe of interest for other areas as well?
-
In the #RESQUE evaluation scheme („Research Quality Evaluation scheme for psychological research“), there is an indicator for publications: “Correctness of computational results has been independently verified“.
With CODECHECK, you can request and upload a verification certificate. This gives you "extra points“ in our evaluation scheme, as this is a real quality criterion.
#researchAssessment #CoARA @aufdroeseler https://nerdculture.de/@aufdroeseler/116165190898955396
-
I learned from @PLOSBiology about the Research Evaluation System for Quality Evaluation #RESQUE, which provides guidelines for responsible research evaluation:
:doi: https://doi.org/10.1371/journal.pbio.3002553
The RESQUE system was originally developed for psychology, but the creators are confident that it can be applied to other fields:
👉 https://nicebread.github.io/RESQUE/
Happy are those scientometrcans who not only have what to measure, but also what to measure)
-
@davetron5000 @Damax Not #MySQL; it's no longer fully #FOSS, but #MariaDB is. You'd have to look at #resque yourself before deciding to fork it, fix it, find alternatives, or build something new. I don't have the strong opinion you do about that, but will assume that someone gave it more than a passing thought.
New isn't always better, but neither is it inherently #NIHsyndrome. Nothing prevents using other #DBs, #ORMs, or #queues if willing to forego #conventionoverconfiguration.
-
@davetron5000 @Damax Probably not, but that's kind of an argument for Rails building something new that doesn't require upstream support or commercial licenses. Last I checked, #resque was struggling to find #maintainers, so a fresh start may be warranted. You'd have to look at their open issues and code to form your own opinion, though.
-
@davetron5000 @Damax Unlike #resque, #sidekick reserves certain features for commercial licenses. I can see why an open source framework might want to find a truly #FOSS alternative that will be maintained alongside the framework itself.
-
Blogged: Jitter to the start time of your #resque jobs in #ruby
https://blog.gripdev.xyz/2023/08/21/ruby-resque-jobs-and-jitter-with-resque-scheduler/
-
@mat We are using Postgres. We were on a mix of #DelayedJob and #Resque, but recently totally replaced Resque with #Sidekiq. We're migrating DJ jobs over as we need to/touch them in any significant way.
We've moved everything to latency-based queues - Sidekiq and DJ both - and it's been a great change!
-
It's been years since I last used #DelayedJob. Like, the early 2010's or so? Back then it was a mix of DJ and #Resque. Then #Sidekiq came on the scene, I moved over pretty quickly.
Anyhow, the point is, I was under the impression that DelayedJob doesn't have a mechanism to recover from jobs that crash/SIGKILL’d (like, think OOM or something). And to be fair, DJ itself doesn't. But the ActiveRecord backend does, though it's not really advertised. https://github.com/collectiveidea/delayed_job_active_record/blob/97f26a3e1b82b338cd8270aad988c75b82ea5c86/lib/delayed/backend/active_record.rb#L57
