#digiarchmaintainathon — Public Fediverse posts

Step one: remind myself how the code works because I last looked properly six years ago 😭

Step two: resolve the outstanding issues (https://github.com/joeroe/rintchron/issues), which are mostly about improving the robustness of response parsing to deal with unusual data (and performance, but I might leave that)

Step three: adapt the tests so that they don't fail on CRAN if the remote server the package depends upon is down

Help is always welcome, of course! #DigiArchMaintainathon

Unfortunately mostly what I've been doing so far in #DigiArchMaintainathon week is maintaining my sanity in the face of university bureaucracy.

But with what's left I will try to get my #Rstats package wrapping the #IntChron chronological data API ship-shape and ready for CRAN.

https://github.com/joeroe/rintchron

This package has actually been in a mature state for years now, but I've put off CRAN submission because it can be really tricky to meet its internet connectivity policies with API packages.

Unfortunately mostly what I've been doing so far in #DigiArchMaintainathon week is maintaining my sanity in the face of university bureaucracy.

But with what's left I will try to get my #Rstats package wrapping the #IntChron chronological data API ship-shape and ready for CRAN.

https://github.com/joeroe/rintchron

This package has actually been in a mature state for years now, but I've put off CRAN submission because it can be really tricky to meet its internet connectivity policies with API packages.

Unfortunately mostly what I've been doing so far in #DigiArchMaintainathon week is maintaining my sanity in the face of university bureaucracy.

But with what's left I will try to get my #Rstats package wrapping the #IntChron chronological data API ship-shape and ready for CRAN.

https://github.com/joeroe/rintchron

This package has actually been in a mature state for years now, but I've put off CRAN submission because it can be really tricky to meet its internet connectivity policies with API packages.

Unfortunately mostly what I've been doing so far in #DigiArchMaintainathon week is maintaining my sanity in the face of university bureaucracy.

But with what's left I will try to get my #Rstats package wrapping the #IntChron chronological data API ship-shape and ready for CRAN.

https://github.com/joeroe/rintchron

This package has actually been in a mature state for years now, but I've put off CRAN submission because it can be really tricky to meet its internet connectivity policies with API packages.

Unfortunately mostly what I've been doing so far in #DigiArchMaintainathon week is maintaining my sanity in the face of university bureaucracy.

But with what's left I will try to get my #Rstats package wrapping the #IntChron chronological data API ship-shape and ready for CRAN.

https://github.com/joeroe/rintchron

This package has actually been in a mature state for years now, but I've put off CRAN submission because it can be really tricky to meet its internet connectivity policies with API packages.

RE: https://archaeo.social/@CAA_SSLA/115893524040726408

Yesterday I updated the roadmap for open-archaeo, which is a list of open source archaeological software and resources (https://open-archaeo.info). while it's fairly comprehensive, it could really benefit from a focused attempt by people who specialize in specific sub-disciplines to identify the software in their domains of expertise. If you'd like to contribute in this way, please check out the roadmap and/or get in touch!

https://github.com/zackbatist/open-archaeo/blob/master/ToDo.md#deep-dives

#DigiArchMaintainathon

RE: https://archaeo.social/@scschmidt/115888509446346811

Following this excellent tip from @scschmidt I learned about cffr (https://docs.ropensci.org/cffr/), a package that automates generation of CITATION.cff for R packages using existing package metadata and keeps it up to date with a GitHub Action. Neat!

#Rstats #DigiArchMaintainathon

RE: https://archaeo.social/@lsteinmann/115889067811195822

And the discussion with @lsteinmann and @scschmidt reminded me that I haven't archived open-archaeo in a while so I generated a new version on Zenodo too: https://doi.org/10.5281/zenodo.18235862 !!

#DigiArchMaintainathon #DigiArch #DigitalArchaeology

For the #DigiArchMaintainathon I just updated the open-archaeo roadmap: https://github.com/zackbatist/open-archaeo/blob/master/ToDo.md

This involved checking off some completed items on our to do list, adding a few new ones, and restructuring the document for greater clarity.

I also added definitions to tags that previously did not have one 😅

#DigiArch #DigitalArchaeology #ComputationalArchaeology

I'm starting #DigiArchMaintainathon today, working further with @jfy133 and @ddj-sa.bsky.social on a new standard for reporting #radiocarbon dates: https://github.com/MIxS-MInAS/miaard/

#DigiArchMaintainathon motivated me to finally write a blog post about the integration of #futhark code into #rstats packages. I've done this last year for my ggpointgrid package and wanted to document the workflow since then.

Link: https://nevrome.de/blog/posts/2026-01-12-futhark-in-ggpointgrid.html

This is a bit nerdy, admittedly, but maybe still interesting for people that come to R from a #functionalprogramming background. At least I myself will need this again eventually, so I'm glad that the #maintainathon gave me the push.

#DigiArchMaintainathon motivated me to finally write a blog post about the integration of #futhark code into #rstats packages. I've done this last year for my ggpointgrid package and wanted to document the workflow since then.

Link: https://nevrome.de/blog/posts/2026-01-12-futhark-in-ggpointgrid.html

This is a bit nerdy, admittedly, but maybe still interesting for people that come to R from a #functionalprogramming background. At least I myself will need this again eventually, so I'm glad that the #maintainathon gave me the push.

#DigiArchMaintainathon motivated me to finally write a blog post about the integration of #futhark code into #rstats packages. I've done this last year for my ggpointgrid package and wanted to document the workflow since then.

Link: https://nevrome.de/blog/posts/2026-01-12-futhark-in-ggpointgrid.html

This is a bit nerdy, admittedly, but maybe still interesting for people that come to R from a #functionalprogramming background. At least I myself will need this again eventually, so I'm glad that the #maintainathon gave me the push.

#DigiArchMaintainathon motivated me to finally write a blog post about the integration of #futhark code into #rstats packages. I've done this last year for my ggpointgrid package and wanted to document the workflow since then.

Link: https://nevrome.de/blog/posts/2026-01-12-futhark-in-ggpointgrid.html

This is a bit nerdy, admittedly, but maybe still interesting for people that come to R from a #functionalprogramming background. At least I myself will need this again eventually, so I'm glad that the #maintainathon gave me the push.

#DigiArchMaintainathon motivated me to finally write a blog post about the integration of #futhark code into #rstats packages. I've done this last year for my ggpointgrid package and wanted to document the workflow since then.

Link: https://nevrome.de/blog/posts/2026-01-12-futhark-in-ggpointgrid.html

This is a bit nerdy, admittedly, but maybe still interesting for people that come to R from a #functionalprogramming background. At least I myself will need this again eventually, so I'm glad that the #maintainathon gave me the push.