gistr
gistr copied to clipboard
ropensci
change maintainer on cran
@ScientificProgrammer when you get a chance, could you submit a new version to cran changing the maintainer to you? not urgent, but any correspondence from cran will go to me right now, so it'd be good to have it go to you instead. thanks!
@ScientificProgrammer did you get a chance to work on this? Happy to help if needed. Thank you!
@ScientificProgrammer it's been a few years now - can you please make this change?
@maelle I think if we don't hear back from Eric within a week or so (since it's been 2 years almost), should we archive this pkg? or put another call out for maintainers?
@ScientificProgrammer thanks for your work on gistr. If you don't answer within one week, we'll put on a call for a new maintainer. Thank you for your understanding! (I found no email address for your profile)
@sckott wrote:
@ScientificProgrammer it's been a few years now - can you please make this change?
@maelle I think if we don't hear back from Eric within a week or so (since it's been 2 years almost), should we archive this pkg? or put another call out for maintainers?
@maelle wrote:
"@ScientificProgrammer thanks for your work on gistr. If you don't answer within one week, we'll put on a call for a new maintainer. Thank you for your understanding! (I found no email address for your profile)"
Hi Scott and Maëlle:
Firstly, thank you for your patience and grace with me. Around the time that I took on the role of maintainer for this package, I also started a new job (and in a different career field no less). That change coincided with the release of Quarto.
When I volunteered to be the maintainer for ropenci/gist, I had a decent understanding of knitr and RMarkdown, along with a tenuous grasp of pandoc, but I don't think I was aware of Quarto's pending release. Since then, I've been telling myself that I'd spend some time becoming proficient with Quarto before making changes to ropenci/gist, and, well...here we are.
Fortunately, by sheer luck, I've spent the last month studying Quarto because I'm determined to become proficient with it. I thought I'd just learn it by using it, but, as I'm sure you can relate, I always seemed to be racing against some deadline. Every time, rather than slowing down and trying to learn Quarto, I'd just fall back to my comfortable place with RMarkdown.
During my recent experimentation with Quarto, I've learned that, although the actual Quarto code chunk syntax is different than RMarkdown's, the two platforms mirror each other so well at a logical level that I'm becoming proficient with Quarto faster than I thought I would.
I'd be disappointed to see the ropenci/gist package retired, but, if you're willing to take another chance on me, I'm willing to put in some some real effort to try and freshen it up. About two years ago, Maëlle gave me a very helpful introduction to being an ropensci dev.
She also offered to give me some one on one help if I needed it. If the offer still stands, I'll take it.
Sincerely, Eric
PS
Maëlle: I regret any confusion. You already have my email and contact info. If I need to make some changes to my personal repo or this one to make my identity clearer, just let me know. I'll send you a reply email momentarily. Thanks for being so engaged and helpful!