Stefano Costa

There's more than potsherds out here

Faccio l’archeologo e vivo a Genova

  • La chiesa di San Bartolomeo a Marzano (Torriglia)

    La chiesa di San Bartolomeo a Marzano (Torriglia)

    Marzano è la frazione del comune di Torriglia (GE) dove sono cresciuto. Un paesino piccolo, luogo di origine dei miei antenati Costa. In questo periodo di isolamento ho avuto la fortuna di passare qui molti mesi e ho raccolto vecchi e nuovi appunti sulla sua storia, per quanto minore e frammentaria.


    La chiesa di San Bartolomeo è l’unica chiesa di Marzano. Non è molto grande e viene variamente definita come cappella, oratorio o chiesa sussidiaria. La sua posizione centrale sulla piazza del paese (che è intitolata a Felice Cavallotti ma è chiamata da tutti “piazza della chiesa”) la rende facilmente riconoscibile. Non credo sia l’edificio più antico esistente in paese, ma è sicuramente quello su cui le notizie storiche sono più numerose, per quanto scarne. E con la storia della chiesa inevitabilmente si racconta anche la storia della comunità.

    I maggiori dettagli storici si ricavano da un articolo del profilico don Giovanni Carraro, pubblicato sul notiziario parrocchiale nel 1938. Una descrizione architettonica più dettagliata che riprende in parte alcune notizie storiche si ricava dalla scheda di catalogo CEI. Riporto il contenuto dell’articolo quasi integralmente con alcuni commenti e soprattutto in ordine cronologico.

    L’articoletto di don Carraro

    La “grande cappella” dedicata a San Bartolomeo Apostolo fu edificata nella prima metà del XVII secolo. Tuttavia, nelle carte dell’archivio parrocchiale viene spesso indicata come cappella dedicata a San Terenziano, vescovo tudertinus (e non terdonensis). In effetti questo dualismo permane ancora oggi: il giorno di San Bartolomeo (24 agosto) viene celebrata la messa, ma è nel giorno dedicato a San Terenziano (San Ransiàn in dialetto, il 3 settembre) che si svolge la festa popolare più laica, quella con i frisceu per capirci. La grande tela che si trova all’interno della chiesa ritrae comunque entrambi i santi insieme a San Rocco, Santa Lucia e Santa Apollonia. La presenza di San Terenziano a Marzano è interessante ed è solo una tra le molte località dell’Appennino dove San Terenziano persiste, talvolta da un millennio. Significativo che le date siano così ravvicinate e a pochi giorni di distanza dal 29 agosto in cui ricorre la Madonna della Provvidenza / Madonna della Guardia.

    La facciata della chiesa oggi

    L’atto di fondazione della cappella fu rogato nel 1648 assegnando una dote di 15 lire annue su terreni vincolati: 10 lire per 8 messe l’anno e 5 lire per riparazioni.

    Nel 1677 fu costituito un censo di 44 soldi su terra l. d. Canivella e un altro censo di 24 soldi.

    Nel 1694 fu rinnovato lo strumento di dotazione della chiesa, autorizzando i massari a riscuotere la somma dalle 27 famiglie, tra cui 5 Guano, 6 Fascia, 2 Pregola, 12 Costa. Vediamo che almeno tre di questi cognomi rimangono tuttora tra quelli caratteristici di Marzano, pur con una differenza di grafia.

    Nella visita pastorale del 28 agosto 1707 si parla di un oratorio campestre intitolato a San Terenziano martire e si descrive lo stato lacunoso delle suppellettili. Nello stesso anno, G. Casazza lasciava una terra detta Fasolai del valore di mezza Genovina.

    Nel 1775 fu concesso di benedire il nuovo altare (che molto probabilmente è quello attuale), purché avesse le misure prescritte.

    Nel 1850 fu dato in locazione per 6 anni un terreno con due castagni e un cerro, detta fascia della chiesa, e un altro terreno detto dell’orto, per 50 lire.

    Il pavimento in graniglia alla veneziana porta la data del 1862 e il nome di Giacomo Costa.

    Nel 1887 viene consentita la costruzione di una nuova casa addossata al coro (esistente ancora oggi), che quindi rende impossibili successivi ampliamenti dell’edificio.

    Nel 1896 viene restaurata dentro e fuori, e provveduta di volta a botte. Nel 1897 viene rinfrescata la facciata e nuovamente nel 1927.


    I lavori di restauro più recenti sono di circa 20 anni fa.

  • All my source code repositories are now on Codeberg

    All my source code repositories are now on Codeberg

    I have moved all my personal source code repositories to Codeberg! Codeberg is the free home for your free projects. Because free and open source software deserves a free and open source platform.

    Codeberg.org is a provider for git source code hosting, based on the Gitea software. Gitea is open source, so there are many servers around, large and small, and there is no centralization. Gitea is very easy to use and it follows the same visual and conceptual paradigms that are common on other platforms. Git itself of course is and remains decentralized. For this reason I could easily switch many providers since I started using Git around 2008: repo.or.cz, gitorious. But that’s the technical side of it.

    Codeberg is run by Codeberg e.V., a no profit organization based in Germany. That means the platform is not run with the purpose of making money (not a bad thing per se, of course) or gathering user data, or accumulating enough social klout to sell the entire platform. It’s a service for the community, just like Wikipedia and OpenStreetMap. And there’s more: you can join Codeberg e.V. and become an active member. You’ll need to pay a small annual fee (which helps cover the costs of infrastructure) and you can participate in the discussions and decisions that shape the future of Codeberg. When I decided to move my repositories to Codeberg, I thought it was an excellent opportunity to give a strong support to this initiative and encourage more users to join us.

    Gitea is open source and it’s not difficult to run your own server. But, as any sysop knows, running thousands of separate servers doesn’t scale, that is, the costs of hosting 1000 repositories on 1000 separate servers are a lot higher that keeping those same 1000 repositories on 1 server only. Keeping a server running and up to date takes time, too. So I think it’s better to keep some of the advantages of centralized platforms and change what is really wrong with them: the software must be free, the governance must be open, the funding should come from users.

    .org hosting on .com was a historical mistake we all made. Time to correct it!

    Andreas Shimokawa

    I took the move to Codeberg as an opportunity to improve my good practice in software development and repository management:

    • I’m not creating “vanity” organizations like I did in the past: all repositories are under the steko user and I will consider creating an organization only when there is an actual community around a project (like we did for Total Open Station)
    • I’m trying to avoid overengineering with planned releases, issues, and anything that puts stress where fun and passion should be
    • I’ll be signing all Git commits with my GPG key
    • I will never again cite a source code repository in an academic paper: instead I will upload the snapshot to Zenodo, get a DOI and cite that (I did this mistake too many times in the past, even recently, only to realize how volatile these URLs can be)

    If you are an open source developer, I encourage you to join me on Codeberg!


    What’s wrong with GitHub?

    In the past 10 years the (apparently) unstoppable trend has been of concentrating the development of most open source software on GitHub, a proprietary service that was acquired by Microsoft last year. When that happened, some people became worried upon realizing that one of the giant monopolies had taken possession of their favourite platform. However, GitHub was a proprietary service all along, and it was made possible by venture capital. It was silly to make it a sacred place, as was teaching students Git as merely the tool behind GitHub, or using GitHub Pages as the “best” option for your website. Yes, there are millions of developers using GitHub, and it makes a lot of things easy, for free… but that comes at a price. I had started deleting repositories from GitHub last year, now only a few ones remain but I will delete those as well. While my personal repositories are moving to Codeberg, at this time Total Open Station remains on GitHub (of course I will try to move it as well, but that’s not a decision I can take by myself and it’s not even on the table).

    Some people moved to Gitlab.com, the flagship website of the company with the same name. The Community edition of Gitlab is open source, and it’s used by Debian, Gnome, Framasoft and other large projects. I had been using Gitlab.com for a few years and I dislike it from many points of view, mostly descending from the fact that it’s funded by venture capital. There were many revealing episodes: asking female employees to wear high heels; putting forward a ‘no politics at workplace’ stance, in order to keep quiet how much they’re looking for big contracts with all branches of the US government including Immigration and Customs Enforcement (ICE). They messed with users’ privacy and retracted introducing telemetry after public outrage. And I’m not even touching the technical side, since GitLab started as a simple GitHub clone and is now a behemoth all about putting your projects in Kubernetes. I have deleted and rectracted almost all repositories and I will delete everything shortly (my user account may remain there, empty, because I don’t like name squatting). In short, if you self host Gitlab, it may be fine, but I would never recommend putting your open source efforts on gitlab.com.

    The old Bitbucket, where I had many of my early Mercurial repositories, is dropping support for Mercurial and suffers from all the same problems of other proprietary platforms. I converted all those repositories and I’m moving those as well, even the old ones that I consider archived, because I think there’s some value in them.

  • Archeologia nel Mediterraneo e colonialismo: seconda puntata

    Questo articolo è stato scritto nel 2012 ed è rimasto in bozze per 8 anni. Mi pare ancora degno di vedere la luce del sole e lo pubblico tale quale con qualche aggiornamento ai link.

    Riprendendo il discorso iniziato qualche tempo fa su archeologia italiana e colonialismo, metto sul piatto altri appunti.

    Il primo punto importante, che ho dato per scontato in precedenza, è che tutto questo ragionamento si applica a quel particolare sottoinsieme dell’archeologia rappresentato dalla ricerca universitaria o accademica in genere, l’unica che in modo sistematico si dedica alla ricerca sul campo all’estero.

    Non penso che ci siano davvero parametri per giudicare se un ricercatore o un gruppo di ricerca siano colonialisti o meno. I problemi di cui ho parlato sono dei temi di riflessione, che conducono il discorso nell’ambito della questione colonialista e fanno diventare una gomena il filo che nessuno può negare ci leghi al colonialismo con la F maiuscola. Sul rapporto tra colonialismo e fascismo di ieri nell’Italia di oggi ci sono spunti in più di un punto di questa intervista a Wu Ming 2. Incluso un riferimento alla rivista Interventions: international journal of postcolonial studies, purtroppo costosissima.

    Avere una pratica colonialista facendo archeologia a volte è semplicemente un fatto. Non essere colonialisti facendo archeologia nel Mediterraneo è difficile, secondo me. Avere una teoria colonialista è una cosa diversa.

    Io penso che nel ventunesimo secolo la parola chiave sia strumentalità: ovvero intendere un luogo, con il suo patrimonio archeologico, semplicemente come uno strumento (indispensabile) per condurre la propria ricerca e per accrescere il proprio prestigio accademico. È evidente che questo concetto non è limitato alle ricerche svolte all’estero, e già questo mi sembra un elemento molto importante, perché apre la strada ad una riflessione sul “colonialismo dietro casa”, sugli archeologi che arrivano da fuori a imporre la loro agenda ad una comunità, a una società.

    Va considerato il punto importante dei finanziamenti per la ricerca. In Italia una parte importante della ricerca all’estero è finanziata dal Ministero degli Esteri (il quadro è ben documentato sul sito web del Ministero). Di questo tema ho avuto modo di parlare con Andrew Bevan alcuni mesi fa. Il confronto con le esperienze straniere ‒ in modo particolare di ex (?) potenze coloniali ‒ è importante ma per qualche motivo mi voglio soffermare sull’Italia e sugli italiani.

    Il discorso sulla ricerca dell’esotico è molto complesso, e probabilmente va nella direzione di una riflessione più profonda sull’identità. Ma identità personale e identità politica si incontrano sempre, anche quando non vorremmo.

    E non dimentichiamo infine di pensare anche all’Italia colonizzata. Non credo esista un elenco di tutte le missioni di ricerca archeologica straniere in Italia. Ma certamente sarebbe interessante averlo, e sarebbe molto lungo. Non solo si scava e si cammina per l’Italia, ma si organizzano anche incontri di alto profilo (e non da ieri).

  • I deleted my Keybase account

    Keybase was acquired by Zoom, the videoconferencing company. In case you never heard of Keybase, it’s a service providing “identity” proofs tied to cryprographic keys, pulling together the various digital identities that many of us have online.

    My Keybase account was deleted. None of the proofs exists anymore, even those that I had published on a few websites that I don’t even use anymore (like Twitter). I had never used it except for that vanity ‘look at my identities’ feeling. And to think that in the beginning many respected FOSS leaders jumped in like it was an amazing solution to GPG usability issues… Now it’s filled with fake accounts eager for cryptocurrency.

    As many have noted, Keybase was bound to be sold from the beginning since it was based on venture capital funding. It may be difficult to put it in practice, but my resolution is to never create new accounts on web services provided by VC funded startups. And even without the VC, the Keybase server and infrastructure always was a proprietary black box ‒ you have no way of running your our Keybase server. Clever marketing had this centralization pictured as the best solution to the wide fragmentation that makes many possible uses of cryptographic keys difficult for most people.

    Of course I had never uploaded my private keys to Keybase, despite this being strongly encouraged by the official documentation. But there’s a good chance that some people did that, and it doesn’t sound too good.

    I don’t think I will look for a replacement, even though a few alternatives have already been announced (keys.pub, openpgp proofs). My current GPG key is found at keys.openpgp.org and many email clients can retrieve it on the fly thanks to WKD.

  • A new home for the Total Open Station project

    As announced in a previous blog post, the Total Open Station project has a new home!

    More specifically, we’re still on GitHub but I have moved the main repository from my personal GitHub account to the “totalopenstation” organization, with myself and @psolyca as owners.

    This seems like a simple step but, in fact, it is the most important improvement that Total Open Station has ever got. It means that what has been a personal project for 12 years is now a collective effort, with a bus factor of 2.

    Before this change, we put a lot of effort to define how the new project will work, with a detailed CONTRIBUTING document (partly inspired by the great example of the Gitea project) and a Code of Conduct (based on the Contributor Covenant). To ensure code quality, all changes must be approved through a review process before being merged into the master branch. This is enforced for all contributors, myself included! There is a process in place to expand the team with new contributors on any part of the application, including code, data samples and design.

    We also gave official status to our Matrix chat room at https://matrix.to/#/#totalopenstation:matrix.org so if you’re looking for casual tips or questions, please drop us a message there!

    We are now looking forward to sharing the next release with all our users and with this in mind we introduced another important change: sponsorship. You can now support our work with a recurring donation, either via GitHub sponsors or Liberapay. Since the project is run as a volunteer effort, sponsorships will help us cover the cost of operating websites, testing hardware devices, and eventually buy a dedicated domain name.

    If you use Total Open Station please let us know and maybe give us a star ★ on GitHub.

    This post was originally published on the Total Open Station project blog.

  • Towards a better website

    For a few months now, this website, the one that shows my personal blog and other pages about my activities and interests, has been improved. You should see no difference however.

    First of all, it still runs on WordPress. I have removed many tools and plugins though, in order to collect less data about my readers and put less of my content in the hands of large internet corporations. In short I have taken several steps to give you more privacy. This is much more and much better than sticking a cookie banner on the home page.

    It’s still common among the tech crowd to think that the best website is a static website, and I agree with the philosophy when I look at inspiring examples like the Low-Tech Magazine. But when I look at all those static websites hosted at GitHub Pages (owned by Microsoft), and most of them load many MBs of external Javascript dependencies just to show a dynamic menu, not to count Disqus comments and Google fonts etc. my general reaction is a big no-no. Not to mention the resources that are consumed when offloading site generation to a third party server. In the future, I want to explore how this website could run on a low-energy self-hosted device but for now I’m following the road to optimization with WordPress.

    I removed the Jetpack plugin, a stifling and pervasive do-it-all offer from WordPress.com that includes, among other features, site monitoring and visitor statistics (of course I never used Google Analytics). It’s all been wiped. I don’t have any numbers about most visited pages or posts and it’s a very good thing. I don’t write to reach mass audiences. I have better feelings towards my blog since I removed Jetpack.

    I had already removed the AMP plugin, a silly act of surrender to the Google monopoly. Will this give me less page views? I don’t really care, since I’m not selling anything here and all I have to offer is good content. But AMP is fast I hear you say! Sure, AMP is fast if you’re under the Google surveillance lens. Instead, my website is offered in HTML to everyone. And RSS/Atom, of course.

    I also removed all external dependencies, and now even fonts are loaded from the same domain steko.iosa.it thanks to the OMGF plugin. This makes the website load faster, despite the race to have everything on a CDN.

    If you run your blog on WordPress, I can only recommend you try for yourself the same steps!

    I also added some niceties, such as the ActivityPub plugin that lets you follow the blog from any Fediverse account (you can also comment without even visiting the website!). Of course you can follow my other native Fediverse account at https://octodon.social/@steko

    The website is faster and consumes less resources because I moved to a new server and I’m now running the latest version of PHP, that improves performance in a significant way. The server is in Nuremberg and is hosted by Hetzner.

    Of course, the best thing I can offer on this website is to continue publishing interesting content. Thank you for reading.

  • I libri che ho letto nel 2019

    I libri che ho letto nel 2019

    Come tradizione, anche questo 2020 il primo articolo che scrivo è dedicato ai libri che ho letto l’anno prima. Questo anche se i libri son pochi e anche se là fuori le cose vanno piuttosto male, perché i libri sono importanti e perché ci sono alcun* affezionat* che immagino in trepidante attesa.

    Lo scorso anno avevo chiuso dicendo che avrei letto solo libri di autrici. Così ho fatto, mi è piaciuto moltissimo e ho anche raccolto una lista inesauribile di altri libri per gli anni a venire. È una impresa femminista implicita, anche se solo alcuni titoli hanno davvero questo spirito. Si tratta anche di una ricerca di equilibrio.

    Ho anche letto più in inglese che in italiano. Il numero complessivo è davvero minimo, un po’ perché in primavera il mio vecchio lettore di ebook ha iniziato a perdere colpi, un po’ perché a novembre sono diventato di nuovo papà.

    Maja Lunde, La storia delle api

    Il libro è arrivato a Natale e non avrei potuto chiedere di meglio. Tre storie che si intrecciano da lontano, tre piccoli personaggi eroici che salvano un pezzetto del mondo.

    Margaret Atwood, The handmaid’s tale

    Quando si legge un classico, la domanda è sempre: ma perché non l’ho letto prima? Ma è sempre il momento giusto, e forse la distopia di Gilead è meno assurda oggi che quando è stata scritta. Ma al di là del valore rivoluzionario di questo libro, c’è un testo molto raffinato di continuo “scoperchiamento” della realtà e perdita di ingenuità. Il finale è da capogiro e mi ha lasciato grande soddisfazione. Ovviamente non ho visto serie TV ma non mi dispiacerebbe leggere il seguito pubblicato da poco.

    Claire Cameron, L’ultima dei Neanderthal

    Una lettura archeologica, per me che ho conoscenze molto generali della preistoria non molto diversa da quella che potrebbe fare chiunque altro. Una lettura stimolante, che taglia corto su tutti i dettagli e prova a calarci dentro le storie e la testa di questi nostri antichi e “sfortunati” antenati. Secondo me la narrazione funziona, così come funziona lo specchio del presente che mi ha ricordato le vicende della ricerca in corso all’Arma Veirana, qui in Liguria. Giustamente, fortissimamente femminile. Se solo più autori avessero il coraggio di scrivere il Paleolitico….

    J.K. Rowling, Harry Potter

    L’ultimo titolo in realtà è una scatola. Ho deciso che potevo concedermi una lettura leggera, leggerissima, e mi sono messo a leggere la saga di Harry Potter. Mi sono fermato all’inizio del Principe mezzosangue per problemi tecnici, quindi sono ancora fermo lì. Mi è piaciuto moltissimo. Una storia interminabile, zeppa di cliché, di impostazione a tratti infantile oppure al contrario faticosissima da leggere, però in fin dei conti indubbiamente epica. E quindi degno di essere letto, anche se non fosse eccezionale, se vi stessero antipatici i maghetti o gli inglesi, se vi sta antipatico il film (anche a me ha dato fastidio l’unico che ho visto anni fa, ma mi era piaciuto Animali fantastici e dove trovarli) e mille altri motivi.

    Chiaro, Rowling è moraleggiante, ripetitiva allo sfinimento, forse qualche capitolo è scritto appositamente per fare da sceneggiatura e ho dovuto rileggere due volte il finale dell’Ordine della fenice per capire cosa succede. Ho letto tutto in lingua originale perché mi pareva un buon modo di godermi l’opera e così è stato. Non pretendevo di trovare un capolavoro ma vorrei comunque finire gli ultimi libri.

    Cosa vorrei leggere nel 2020

    Per la prima volta provo a condividere alcuni nomi che vorrei leggere nel 2020 (ho già iniziato una raccolta di saggi e articoli di Michele Ainis). Suggerimenti benvenuti, soprattutto se tengono conto di quello che ho scritto. Alcuni sono nomi che ho appuntato da solo, altri sono suggerimenti che ho ricevuto su Mastodon.

    • Ayòbámi Adébáyò, Stay with me
    • Elena Ferrante
    • Ursula K. Le Guin
    • Fatema Mernissi
    • Octavia Butler, Xenogenesis series
    • Donna Haraway
  • Total Open Station 0.5

    Total Open Station 0.5

    Total Open Station 0.5 is here!

    This release is the result of a short and intense development cycle.

    The application is now based on Python 3, which means an improved handling of data transfers and a general improvement of the underlying source code.

    An extensive test suite based on pytest was added to help developers work with more confidence and the documentation was reorganized to be more readable.

    There are only minor changes for users but this release includes a large number of bugfixes and improvements in the processing of data formats like Leica GSI, Carlson RW5 and Nikon RAW.

    The command line program totalopenstation-cli-parser has four new options:

    • --2d will drop Z coordinates so the resulting output only contains X and Y coordinates
    • --raw will include all available data in the CSV output for further processing
    • --log and --logtofile allow the logging of application output for debugging

    If you were using a previous version of the program you can:

    • wait for your Linux distribution to upgrade
    • install with pip install --upgrade totalopenstation if you know your way around the command line on Linux or MacOS
    • download the Windows portable app from the release page: this release is the first to support the Windows portable app from the start – for the moment this release supports 64-bit operating systems but we are working to add a version for older 32-bit systems.

    But there’s more. This release marks a renewed development process and the full onboarding of @psolyca in the team. With the 0.6 release we are planning to move the repository from the personal “steko” account to an organization account and improve the contribution guidelines so that the future of Total Open Station is not dependent on a single person. Of course we have already great plans for new features, as always listed on our issue tracker.

    If you use Total Open Station please let us know and maybe give us a star ★ on GitHub.

  • Total Open Station 0.4 release

    Total Open Station 0.4 release

    This article was originally published on the Total Open Station website at https://tops.iosa.it/

    After two years of slow development, I took the opportunity of some days off to finally release version 0.4, that was already available in beta since 2017.

    No open bugs were left and this release is mature enough to hit the repositories.

    Find it on PyPI at https://pypi.python.org/pypi/totalopenstation as usual.

    Windows users, please note that the TOPS-on-a-USB-stick version will have to wait a few days more, but the beta version is equally functional.

    What’s new in Total Open Station 0.4

    The new version brings read support for 4 new formats:

    • Carlson RW5
    • Leica GSI
    • Sokkia SDR33
    • Zeiss R5

    Other input formats were improved, most notably Nikon RAW.

    DXF output was improved, even though the default template is not very useful since it is based on an old need from the time when TOPS was developed day to day on archaeological excavations.

    The work behind these new formats is in part by the new contributor to the project, Damien Gaignon (find him as @psolyca on GitHub), who submitted a lot of other code and started helping with project maintenance as well. I am very happy to have Damien onboard and since my usage of TOPS is almost at zero, it’s very likely that I will hand over the development in the near future.

    The internal data structures for handling the conversion between input and output formats are completely new, and based on the Python GeoInterface abstraction offered by the pygeoif library. This allows going beyond single points to managing lines and polygons, even though no such feature is available at the moment. If you often record linear or polygonal features that you’re manually joining in the post-processing stage, think about helping TOPS development and you could get DXF or Shapefiles with the geometries ready to use (yes, Shapefile output is on our plans, too).

    There were many bugfixes, more than 100 commits, 64 by Damien Gaignon and 52 by myself (to be honest, many of my own commits are just merges!).

    This version is the last built on Python 2, and work is already ongoing towards a new version that will be based on Python 3: a more mature codebase will mean a better program, without any visible drastic change.

    Photo by Scott Blake on Unsplash

  • I left my role of editor of the Journal of Open Archaeology Data

    After serving for 7 years as the co-editor of the journal together with Victoria Yorke-Edwards, I have chosen to step down from my role as editor, while remaining on the Editorial Board. I had been on the Editorial Board before.

    Recently I have become rather busy with work and family commitments, with only a minor involvement in academic archaeology to guarantee the time and effort that is required for running JOAD. To ensure that JOAD continues to be successful, this decision was necessary. This announcement arrives after one year of transition – we did not abandon the ship and continued publishing open archaeology datasets.

    The new editors, Alessio Palmisano and Carmen Ting, will bring forward the journal’s mission with support from Anastasia Sakellariadi who has taken the very important role of editorial manager for the journal at Ubiquity Press.

    As I look back to the past few years, the global scenario of open research data has changed a lot, becoming both more and more common but also more integrated with other facets of the broader open science movement, in archaeology too.

    I think JOAD has a tremendous potential to improve all archaeological disciplines as an open science good practice. The peer review process is almost always a chance for authors to improve their work and the datasets they are about to publish, thanks to the many reviewers that volunteered to foster our activity. You can register now to become a reviewer in your field of specialization.

    There are now other data journals that, while missing the specificity on archaeology, are geared towards a systematic habit of data sharing via data descriptor papers. This is both a challenge to the idea of a specific journal for each disciplinary field (something that mega-journals partly achieved, in the footsteps of PLOS One) and a big move towards open access publishing for research data, whatever the actual plan we choose to get there. I am convinced that the Journal of Open Archaeology Data will play its role even in this changed environment.