rCDK Maintainer Wanted.

[zachcp]

• Do you use rcdk or depend on it?
• I'm looking to hand off the maintenance reins.
• If you're interested, comment on this thread or shoot me an email.

( cc: @rajarshi )

[egonw]

@zachcp, @rajarshi, what about moving it under the hood of the Blue Obelisk? I co-maintain another R package or two and can help out.

[rajarshi]

I'd be open to that

[zachcp]

I think that's a great idea. What do you need? And thank you

[egonw]

What do you need?

I would suggest:

• move this repo to github.com/cdk or github.com/blueobelisk
• check/set up write credentials for everyone
• get me up to speed with making CRAN releases (been a while)

[egonw]

@rajarshi, @zachcp, shall I go ahead?

[rajarshi]

Yes, fine from my side. But as @zachcp is the current maintainer, I'd look for confirmation from him

[zachcp]

@egonw that sounds like a plan. I would probably move all of the following repos:

• rcdklibs - basically just provides the CDK uberjar
• rcdk - functionality on top of the jar
• rinchi - maybe obsolete with new CDK code?
• fingerprint - i would recommend re-wrapping CDK fingerprints
• depict - fns to wrap the DepictionGenerator

I've invited you as the Owner of this organization. You can move the repos and give me Contributor access on the new repos. We can bump a release to add you as the Primary maintainer on each of those packages - I THINK thats all that will be needed for CRAN. On the release side - the jar stuff is straighforward but the build step for CDKR can be a pain.

[zachcp]

Egon let's hold on moving these repos until I'm finished with the releases

[zachcp]

So the current status is:

• RCDK: 20250910 vbump #156 minor fixes to keep up with CRAN standards.
• RCDKLIBS: 20250910 vbump rcdklibs#6 we will not be able to use the standard CRAN release mechanism to host JARs. The size has become a problem and a new way of getting the JARs would be required.