📢 We are back after the summer break this Friday, 4th September to connect, recap developments during the break, share blog post ideas and have a good discussion. 😃 Hope to see you there! 👩‍💻

Our next meeting will take place on Friday, 6th March. It will be an exciting one, as we would like to elect a new "steering board" (aka the people writing here and the emails 😉). These are really quite manageable positions, as the three can share the load how they feel appropriate and it is not […]

And as a friendly reminder, we hold monthly meetings where we host amazing speakers, organize collectively-maintained projects, and discuss all things relating to scripting languages in archaeology! (we also sometimes spill out into other #DigitalArchaeology and #ComputationalArchaeology topics […]

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 […]

CAA SSLA@caa-ssla.archaeo.social.ap.brid.gy · 8mo ago

👾🏺 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 […]

👾 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 […]

📈 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 […]

🔭 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 👉 […]

🌐 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 […]

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 […]

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 […]

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 […]

CAA SSLA@caa-ssla.archaeo.social.ap.brid.gy · 8mo ago

🐾 A roadmap is a documented plan of action that structures future work. Having a checklist of things to do (and already done!) can help garner momentum while also making your plans more transparent for prospective users. Roadmaps should document what features are planned over short- and […]

🤖 Continuous integration (CI) automates tasks that always need to be done after you update your codebase e.g. building a software, testing, generating documentation, or producing accessible outputs. This is great, as it ensures robust software development. Want to learn more? Check out our short […]

RE: https://archaeo.social/@zackbatist/115894441545778394 ✨ Advertisement block for open-archaeo.info ✨ It's your first resource if you are looking for a software tool to solve your #DigitalArchaeology or #ComputationalArchaeology problem. And if you know a good one: Have a look whether it is […]

Zack Batist@zackbatist.archaeo.social.ap.brid.gy · 8mo ago

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 […]

✅ Testing your code involves including additional logic to test whether your code is operating as you expect it to. Aside from supporting users with different computational environments, they’re a great way to slow down and think about the code you’re writing and whether it supports your goals […]

📚 Plenty of research has been done to encourage better software engineering practices, among archaeological and non-archaeological researchers alike. We compiled a brief list of papers addressing challenges in this space, and we encourage you to take a gander […]

🐾 A roadmap is a documented plan of action that structures future work. Having a checklist of things to do (and already done!) can help garner momentum while also making your plans more transparent for prospective users. Roadmaps should document what features are planned over short- and […]

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 […]

SCSchmidt@scschmidt.archaeo.social.ap.brid.gy · 8mo ago

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 […]

📜 Check: Is your code properly licensed? ⁉️ If not, go and give one of your repositories a license now! It is such a quick and easy way to improve the re-usability of your contribution. Have a look at our small introduction, if you need guidance 👉 […]

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 […]

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 […]

💛 Open source projects thrive on community support, and acknowledging contributors is important. If you’re leading a collaborative project that produces open source software, members of your team will surely appreciate a public acknowledgement of their work! Account for how people contribute […]

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 […]

✨ 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 […]

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

📝 A README is a plaintext file that includes a detailed description of a project. It typically includes: * A broad overview of the project, why it was developed, and the rationale behind its implementation * Instructions for how to install or run the code * Links to other related tools or […]

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 […]

Clemens Schmid@clemensschmid.archaeo.social.ap.brid.gy · 8mo ago

#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 […]

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 ) […]

SCSchmidt@scschmidt.archaeo.social.ap.brid.gy · 8mo ago

RE: https://archaeo.social/@CAA_SSLA/115881966254704540 When @zackbatist wrote his short explanation on citation file format he took a package by me and Simon Maddison as a positive example. Which shames me into admitting that it is the only repo I have on github, which has a CFF. 😳 I will […]

#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 […]

RE: https://archaeo.social/@CAA_SSLA/115881966254704540 When @zackbatist wrote his short explanation on citation file format he took a package by me and Simon Maddison as a positive example. Which shames me into admitting that it is the only repo I have on github, which has a CFF. 😳 I will […]

CAA SSLA@caa-ssla.archaeo.social.ap.brid.gy · 8mo ago

🧭 A very easy task to make your code more easily citable is the so-called Citation File Format, a CFF. This file is a yaml-style plaintext document giving metadata on your repository (author, date of release, version etc). This can be picked up by zotero or another citation manager. For a small […]

🧭 A very easy task to make your code more easily citable is the so-called Citation File Format, a CFF. This file is a yaml-style plaintext document giving metadata on your repository (author, date of release, version etc). This can be picked up by zotero or another citation manager. For a small […]