Dear all, The most important thing is to have a person willing to take the responsibility of being archivist/librarian for the SIG data. The choice of technical implementation is not so important. Best, Christian-Emil ________________________________ Fra: Crm-sig <[email protected]> på vegne av George Bruseker via Crm-sig <[email protected]> Sendt: onsdag 10. september 2025 12:18 Til: Dominic Oldman <[email protected]> Kopi: crm-sig <[email protected]> Emne: Re: [Crm-sig] issue 704 New Tool for Managing CIDOC CRM SIG Issues
Dear Dominic, Do you have another system in mind? We had a discussion in the last SIG about this, you might recall. The list serv and drupal solution is very heavy and time consuming; it is a high bar, high friction way of getting into things. We need a light and functional solution that allows broad participation, doesn't cost money (or as little as possible since we have no funding) and is low bar access (people don't have to learn things). It should also meet the current ability to tag issues with the CRM version, class, property, cross reference issues etc. If you know of solutions better (or just different, worth thinking about) than github / lab, please put them forward. Ears open. Or if someone wants to do wide market research, great, please do! Gitlab is suggested because our resources are limited and it has an issues system, it can easily line up. Also FORTH already uses it and it can be directly linked to releases. This is how version management tends to be done these days. Here are other options that I know about: Github - Linkedart uses, very successful model, everyone contributes, talks and collaborates, is commercial though (no cost to enter issues though) Jira - heavy expensive clunky Redmine - open source free, very clunky - FORTH has used it in the past (we assume FORTH is hosting) Discourse - Arches uses, quite beautiful interface, but heavy setup investment, not sure about costs I know of others but I don't think they are even in the competition. But if you have knowledge of other systems that are up to the task, please throw them into the mix and we can discuss it here and in person in Herakleion. Best, George On Wed, Sep 10, 2025 at 11:40 AM Dominic Oldman <[email protected]<mailto:[email protected]>> wrote: It would be great if we could actually do an options appraisal rather than just single out a particular technical solution. It would be good to just review what we want to get out of the system going forward and the people we would like it to serve - and possibly engage. I don't know much about Gitlab and its suitability but can we start with some criteria? What is good and bad about the current system, etc. I would contribute to this appraisal. D On Tue, 9 Sept 2025 at 12:35, George Bruseker via Crm-sig <[email protected]<mailto:[email protected]>> wrote: Dear all, Please find linked a document with homework related to issue 704. THe issue was the proposal of a modern tool for managing issues according to industry standards. https://docs.google.com/document/d/1lPj9VMl4sD3yZkozsJYvYXgQ2fb1AoM8Pj3uXeHwROQ/edit?usp=sharing The discussion was taken up in the context of updating the website and general tooling upgrade. Stephen and I were tasked with coming up with a proposal for a system to handle issues in a more streamlined and standard manner which would encourage greater participation. The linked document outlines a proposal to move our issue management to gitlab, currently already used by FORTH to manage versioning of CIDOC CRM. One issue that is perhaps with digging into more as we consider this tool change is if it has any implications on our existing workflow for raising issues. I think probably it doesn't. It has always been the case that anyone on the list could raise an issue, but now it would be much more straighforward for them to do and for others to follow. The document is open for all to edit and comment on. Please feel free to offer ideas and comments either here or in the doc (eventually in a publically commentable issue in gitlab hopefully!). Best, George On Mon, Sep 8, 2025 at 8:00 AM Eleni Tsouloucha <[email protected]<mailto:[email protected]>> wrote: Dear George, dear Stephen, in the last meeting you volunteered to come up with a proposal concerning replacing the mailing list and current issues management with github (issue 704<https://cidoc-crm.org/Issue/ID-704-the-future-of-mailing-list-issues-management>). Is this something you're willing to devote time to ahead of the meeting in October? Please let me know, All the best, -- Eleni Tsouloucha Philologist - MA Linguistics & Language Technologies Center for Cultural Informatics Information Systems Laboratory - Institute of Computer Science Foundation for Research and Technology - Hellas (FORTH) Address: N. Plastira 100, GR-70013 Heraklion, Grece email: [email protected]<mailto:[email protected]>, [email protected]<mailto:[email protected]> Tel: +30 2810391488 _______________________________________________ Crm-sig mailing list [email protected]<mailto:[email protected]> http://cidoc-crm.org/crm-sig-mailing-list
_______________________________________________ Crm-sig mailing list [email protected] http://cidoc-crm.org/crm-sig-mailing-list
