It was a (fun!) challenge revisiting my old code. Might not have done it, if not for the Maintainathon. Thanks, @CAA_SSLA and @zackbatist , for having this idea!
RE: https://archaeo.social/@CAA_SSLA/115881087318544124
πΎ For those who might have missed it, earlier this month we organized the inaugural Digital Archaeology Maintainathon --- an opportunity to clean, document and revise older code together. We wrote a brief summary of the event here: https://sslarch.github.io/maintainathon/2026-recap.html
Thank you to all those who posted about this hidden labour using the #DigiArchMaintainathon tag, and to everyone else who followed along and boosted these experiences!
π€πΊπ€
πΎ We are very happy to have done this #DigiArchMaintainathon πΎπΊ! It was a great way to connect with people and showcase the work that needs to be done in #DigitalArchaeology and #ComputationalArchaeology. Software does need constant work and so many people are doing it.
If you wish to connect with the SIG SSLA, please check out our homepage π https://sslarch.github.io/, join our googlegroup or meet us at the @CAA_int in Vienna this year!
π Weβve showcased many great projects throughout the week, many of which are developed by junior researchers and volunteer labour. If any of these are especially interesting to you, consider reaching out to offer support! This can take the form of contributions to the code base, helping promote the project, or even financial donations.
Even a small donation shows deep appreciation, and can help motivate labour performed largely by volunteers and precarious workers!
#DigiArchMaintainathon πΎπΊ
@CAA_SSLA
A very good resource to learn more about documentation is the dedicated @coderefinery lesson!
Check it out for yourself! https://coderefinery.github.io/documentation/
#DigiArchMaintainathon #ComputationalArchaeology #DigitalArchaeology #ResearchSoftware
π Something that always needs to be done, is documenting code. We all seem to lack behind in this task. So, why not take half an hour today to write a short documentation on one of your repositories? Just as a start? Read more about documenting code here π
https://sslarch.github.io/maintainathon/resources#writing-comprehensive-documentation
#DigiArchMaintainathon #DigitalArchaeology #ComputationalArchaeology #Maintainathon
π Do you publish your code properly?
While commercial platforms like GitHub and GitLab may provide very useful collaboration features, they should not be trusted as long-term stewards of software or data. Professional archives are better suited for this. There are some options. Check out our small intro π https://sslarch.github.io/maintainathon/resources#archive-your-code-in-a-long-term-repository
#DigiArchMaintainathon #DigitalArchaeology #ComputationalArchaeology #Maintainathon
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.