💛 Similarly, developers often lack insight into who is actually using the software they make.
So if you’re using an open source tool or a resource developed by a fellow archaeologist, post about it in the replies! I am sure they will appreciate the shoutout.
#digiarchmaintainathon […]
So if you’re using an open source tool or a resource developed by a fellow archaeologist, post about it in the replies! I am sure they will appreciate the shoutout.
#digiarchmaintainathon […]
Original post on archaeo.social
archaeo.social
January 13, 2026 at 6:13 PM
💛 Similarly, developers often lack insight into who is actually using the software they make.
So if you’re using an open source tool or a resource developed by a fellow archaeologist, post about it in the replies! I am sure they will appreciate the shoutout.
#digiarchmaintainathon […]
So if you’re using an open source tool or a resource developed by a fellow archaeologist, post about it in the replies! I am sure they will appreciate the shoutout.
#digiarchmaintainathon […]
✨ Code reviews are constructive, arms length commentary on published research software. In addition to providing structured feedback to maintainers, they help raise awareness of a tool. This is a win-win for developers and users alike!
#digiarchmaintainathon #digitalarchaeology […]
#digiarchmaintainathon #digitalarchaeology […]
Original post on archaeo.social
archaeo.social
January 13, 2026 at 10:45 AM
✨ Code reviews are constructive, arms length commentary on published research software. In addition to providing structured feedback to maintainers, they help raise awareness of a tool. This is a win-win for developers and users alike!
#digiarchmaintainathon #digitalarchaeology […]
#digiarchmaintainathon #digitalarchaeology […]
So far for the #DigiArchMaintainathon I have worked on transferring projects from GitHub to Codeberg, because my values are more closely aligned with Codeberg, and GitHub's recent move to Microsoft's AI division (no way that ends well).
First repo transferred: codeberg.org/bbartholdy/b...
First repo transferred: codeberg.org/bbartholdy/b...
bjorns.website
Personal website
codeberg.org
January 14, 2026 at 1:38 PM
So far for the #DigiArchMaintainathon I have worked on transferring projects from GitHub to Codeberg, because my values are more closely aligned with Codeberg, and GitHub's recent move to Microsoft's AI division (no way that ends well).
First repo transferred: codeberg.org/bbartholdy/b...
First repo transferred: codeberg.org/bbartholdy/b...
✅ Check out our resources page for a very simple practical guide on how to write unit tests, written by @lsteinmann: http://sslarch.github.io/maintainathon/resources#test-your-codes-functionality
#digiarchmaintainathon #digitalarchaeology #ComputationalArchaeology #maintainathon
#digiarchmaintainathon #digitalarchaeology #ComputationalArchaeology #maintainathon
January 15, 2026 at 8:42 AM
✅ Check out our resources page for a very simple practical guide on how to write unit tests, written by @lsteinmann: http://sslarch.github.io/maintainathon/resources#test-your-codes-functionality
#digiarchmaintainathon #digitalarchaeology #ComputationalArchaeology #maintainathon
#digiarchmaintainathon #digitalarchaeology #ComputationalArchaeology #maintainathon
#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 […]
Link […]
Original post on archaeo.social
archaeo.social
January 12, 2026 at 12:13 PM
#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 […]
Link […]
We definitely missed many relevant papers on optimizing for speed and efficiency, so please reply with additional recommendations!
#digiarchmaintainathon
#digiarchmaintainathon
January 14, 2026 at 8:12 PM
We definitely missed many relevant papers on optimizing for speed and efficiency, so please reply with additional recommendations!
#digiarchmaintainathon
#digiarchmaintainathon
👾 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 […]
If you wish to connect […]
Original post on archaeo.social
archaeo.social
January 16, 2026 at 8:27 PM
👾 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 […]
If you wish to connect […]
I'm starting #digiarchmaintainathon today, working further with @jfy133 and Deon de Jager on a new standard for reporting #radiocarbon dates: https://github.com/MIxS-MInAS/miaard/
GitHub - MIxS-MInAS/miaard: Minimum Information about a Radiocarbon Date
Minimum Information about a Radiocarbon Date . Contribute to MIxS-MInAS/miaard development by creating an account on GitHub.
github.com
January 13, 2026 at 8:12 AM
I'm starting #digiarchmaintainathon today, working further with @jfy133 and Deon de Jager on a new standard for reporting #radiocarbon dates: https://github.com/MIxS-MInAS/miaard/
In the spirit of the #digiarchmaintainathon I've updated a couple of Repo READMEs, added cff files and enjoyed the quick "do a release and automatically push it to zenodo" - feature from GitHub. Once it's set up this is such a good and quick way to safeguard a repository, I can really encourage […]
Original post on archaeo.social
archaeo.social
January 13, 2026 at 3:46 PM
In the spirit of the #digiarchmaintainathon I've updated a couple of Repo READMEs, added cff files and enjoyed the quick "do a release and automatically push it to zenodo" - feature from GitHub. Once it's set up this is such a good and quick way to safeguard a repository, I can really encourage […]
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 […]
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 […]
Original post on archaeo.social
archaeo.social
January 15, 2026 at 11:56 AM
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 […]
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 […]
👾🏺We will post threads to explain terms and best practices and to encourage you to join us in a certain task from today until Friday. Feel free to join in, but don’t despair, if you can only do a small task this week. Every small step will count towards your project! 💪
#digiarchmaintainathon […]
#digiarchmaintainathon […]
Original post on archaeo.social
archaeo.social
January 12, 2026 at 8:17 AM
👾🏺We will post threads to explain terms and best practices and to encourage you to join us in a certain task from today until Friday. Feel free to join in, but don’t despair, if you can only do a small task this week. Every small step will count towards your project! 💪
#digiarchmaintainathon […]
#digiarchmaintainathon […]
For #digiarchmaintainathon I did a couple of new releases from Github to Zenodo and ran into a weird problem, with Zenodo not showing my one of my releases. I found out about the /repo/settings/hooks page, where under the tab "recent deliveries" I could see a 401 error on my last release. I […]
Original post on archaeo.social
archaeo.social
January 14, 2026 at 9:31 AM
For #digiarchmaintainathon I did a couple of new releases from Github to Zenodo and ran into a weird problem, with Zenodo not showing my one of my releases. I found out about the /repo/settings/hooks page, where under the tab "recent deliveries" I could see a 401 error on my last release. I […]
RE: https://archaeo.social/@ClemensSchmid/115882042615914290
We should all strive to write efficient code. As @ClemensSchmid also pointed out on the #digiarchmaintainathon resources page, software efficiency makes code more accessible, more reproducible, and more effective in derivative […]
We should all strive to write efficient code. As @ClemensSchmid also pointed out on the #digiarchmaintainathon resources page, software efficiency makes code more accessible, more reproducible, and more effective in derivative […]
January 12, 2026 at 4:00 PM
RE: https://archaeo.social/@ClemensSchmid/115882042615914290
We should all strive to write efficient code. As @ClemensSchmid also pointed out on the #digiarchmaintainathon resources page, software efficiency makes code more accessible, more reproducible, and more effective in derivative […]
We should all strive to write efficient code. As @ClemensSchmid also pointed out on the #digiarchmaintainathon resources page, software efficiency makes code more accessible, more reproducible, and more effective in derivative […]
In the context of #DigiArchMaintainathon, I just uploaded a CFF file to some of my research software, including the Pytheas seafaring simulator. It was so incredibly easy, I do not understand why I did not do this before!
#DigitalArchaeology
#ComputationalArchaeology
#DigitalArchaeology
#ComputationalArchaeology
January 13, 2026 at 7:50 AM
In the context of #DigiArchMaintainathon, I just uploaded a CFF file to some of my research software, including the Pytheas seafaring simulator. It was so incredibly easy, I do not understand why I did not do this before!
#DigitalArchaeology
#ComputationalArchaeology
#DigitalArchaeology
#ComputationalArchaeology
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 […]
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 […]
Original post on archaeo.social
archaeo.social
January 13, 2026 at 8:20 PM
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 […]
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 […]
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 […]
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 […]
Original post on archaeo.social
archaeo.social
January 13, 2026 at 8:03 PM
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 […]
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 […]
@electricarchaeo @BlckheathHopper In case it wasn't clear, this is what I was referring to: https://archaeo.social/@CAA_SSLA/115881087318544124
CAA SSLA (@CAA_SSLA@archaeo.social)
👾🏺 This week we are hosting a week-long #DigitalArchaeology #maintainathon, an opportunity to clean, document and revise older code together! If you’re a #ComputationalArchaeology *st take this time to update your README, add code comments, write a unit tests or consolidate your project roadmap, and post about it using #DigiArchMaintainathon. We’ll boost these posts to extend best practices throughout our wonderful #OpenScience research community! See 👉 http://sslarch.github.io/maintainathon
archaeo.social
January 12, 2026 at 4:00 PM
@electricarchaeo @BlckheathHopper In case it wasn't clear, this is what I was referring to: https://archaeo.social/@CAA_SSLA/115881087318544124
RE: https://archaeo.social/@scschmidt/115882076779565982
Yes! Making a cff is such a simple yet high impact action. Anyone else who's currently working on a manuscript or research compendium should follow @scschmidt's example (and post about it with #digiarchmaintainathon ) […]
Yes! Making a cff is such a simple yet high impact action. Anyone else who's currently working on a manuscript or research compendium should follow @scschmidt's example (and post about it with #digiarchmaintainathon ) […]
January 12, 2026 at 3:44 PM
RE: https://archaeo.social/@scschmidt/115882076779565982
Yes! Making a cff is such a simple yet high impact action. Anyone else who's currently working on a manuscript or research compendium should follow @scschmidt's example (and post about it with #digiarchmaintainathon ) […]
Yes! Making a cff is such a simple yet high impact action. Anyone else who's currently working on a manuscript or research compendium should follow @scschmidt's example (and post about it with #digiarchmaintainathon ) […]