h1. Developer Meeting 2022-01-17

Updated information in the course of the meeting is %{color:green}in color%. Every participant is welcome to add and adapt.

h2. Participants

* Andreas Olschnögger
* Alexander Watzinger
* Bernhard Koschiček-Krombholz
* Christoph Hoffmann
* Nina Richards
* Stefan Eichert

h2. Administrative

* Protocol (during meeting)
* Upcoming vacations in internal wiki -> %{color:green}Please add vactions > 2 days%
* Feature freeze about one week before releases

h2. New maps

* #1628 New maps, [[New maps|draft]], everyone with ideas/request should contribute before -> %{color:green}Andis first quest.%
* Is Bootstrap version relevant?
* Also minor backend UI issues to start for Andreas.
* Maybe a small meeting with Christoph and Alex?  -> %{color:green}First Christoph and Alex; than Christoph, Andi, Alex%

h2. New CIDOC and super events

#1506, with removal of P117 we have to decide what to do with existing links, options are
** Remove it -> kind of "rude" because projects are using it to structure events  -> %{color:green}No.%
** Implement as a two link relation -> cumbersome, costly and error prone  -> %{color:green}No.%
** %{color:green} Include the archaeological CIDOC CRM -> Can be useful later%
** Add a new shortcut in our model -> would shift responsibility to the API  -> %{color:green}Alex will develop the shortcut to version 7.1.0. At the moment, we keep the API as it is.%

h2. Project task overview %{color:green} in internal wiki%

* CONNEC presentation site and meeting date -> %{color:green}Hopefully everything done in February%
* Server moves %{color:green}-> Looking good, THANADOS and CONNEC should be done in February. THANADOS Frontend Meeting Alex and Stefan%
* INDIGO/ARCHE update %{color:green}-> Need general more specification.%
* #1620 How to enter natural events %{color:green}-> Everbody is fine with the draft%

h2. Guideline drafts

With growing OpenAtlas team and cooperations, guidelines are getting important. To avoid the usual pitfalls when creating guidelines we want to make sure that they are:
* Agreed on
* Up to date
* Understandable, precise and feasible (less is more) 

There are some drafts we could look at and discuss how to proceed:
* Development [[standards]]
* Mission statement, Nina prepared a draft %{color:green}-> Put on the website, not redmine%
* Code of conduct, there is a small one in the code base ("CoC":https://github.com/craws/OpenAtlas/blob/main/CODE_OF_CONDUCT.md) and Nina prepared a new draft