This repository was archived by the owner on Jul 29, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 29, 2023. It is now read-only.
Upstreaming / Uploading to CRAN #10
Description
Thanks, @JanMarvin, for the work you're doing to update RQDA.
Will the changes here be upstreamed to Ronggui/RQDA and/or will a release be made on CRAN? The current installation process with the dependency hell it creates seems to be a nightmare, and it being unarchived on / resubmitted to CRAN would make a world of a difference.
Activity
JanMarvin commentedon Jun 27, 2020
Good question. To be honest I've no clue. I've always felt that pushing upstream is the right thing to do, but to be frank I feel that RQDA upstream is abandoned. There hasn't been activity for some time, CRAN must've been reaching out before archiving, so I'd say upstream has lost interest.
Then again, I'm not sure, I haven't been in touch with Ronggui so no clue what his motivation is. I just saw an opportunity for myself to do some GUI coding in R and that's all. To really provide upstream with clean pull requests for all my changes would be quite time consuming (in the beginning there were various fixes and cleanups here and there) and I won't do that for a dead project or one that I have no real interest in.
And that's another story. I don't use RQDA. I'm not even a qualitative researcher (never have been) and my years in academia are gone for good. This leads to problems
Specifically due to (2) I'd like to see someone else or better multiple people take leadership over whatever the new RQDA should be. Maybe someone will use my codebase or maybe I have just pushed RQDA from it's deathbed for a little while.
So right now it's just not decided what will be the future course of action. Installing a few dependencies once and running a single line of
devtoolsis fine for me right now.The best thing for you right now might be opening issues about not working things. Maybe start working on open issues?
stragu commentedon Jul 13, 2020
This will of course mean more work, but to guarantee sustainability for this important package, I wonder if going through the process of making it an ROpenSci project is an option you'd consider?
That way, if the maintainer decides to drop it, the organisation will facilitate finding someone else to take over.
https://ropensci.org/software-review/
JanMarvin commentedon Jul 13, 2020
Thanks for the idea, but I have no desire to do so.
JanMarvin commentedon Oct 28, 2020
I have moved RQDA to this Organization repository. Mostly to make it more visible. Aside from that there is no secret plan or hidden agenda.
BroVic commentedon Oct 28, 2020
Thank you, @JanMarvin for the great work!
JanMarvin commentedon Nov 22, 2020
Hi @Ronggui since there is activity in your branch, maybe you want to join this discussion?
BroVic commentedon May 25, 2021
Hello everyone, what's the latest on this?
JanMarvin commentedon May 25, 2021
Hello @BroVic, nothing has changed on my end. My code is public and working (at least I was told so). No one else has stepped up offering to work on RQDA and I don't use it at all. I haven't checked the changes upstream and wasn't contacted, so not sure how comparable they are.