# AiiDA Team Meeting 2023-11-30

###### tags: `team meetings`
###### time: 11:00 CET

[TOC]

### Present

* Sebastiaan
* Marnik
* Xing
* Kristjan
* Giovanni
* Jason
* Miki

### Catch-up round

*Max. 3 minutes each*

Sebastiaan:
* Prepared [the `v2.5.0` release](https://github.com/aiidateam/aiida-core/pull/6193): PRs remaining
* [ORM: Monkeypatch sqlalchemy to silence inconsequential warnings](https://github.com/aiidateam/aiida-core/pull/6192): This one is blocking. Already approved by Jason. Anyone objection to this solution?
* [Increase user-friendliness of CLI when tasks get lost](https://github.com/aiidateam/aiida-core/pull/6194): expose `verdi devel rabbitmq tasks analyze --fix` under `verdi process revive`. Any other suggestions for the command name>
* **PRs**:
* [ORM: Switch to pydantic for code schema definition](https://github.com/aiidateam/aiida-core/pull/6190): Use pydantic for configuration definition of `Code` subclasses, just as is done for storage backend plugins
* [Engine: Allow `CalcJob` monitors to return outputs](https://github.com/aiidateam/aiida-core/pull/6191)

Marnik:
* **(Draft) PRs**:
* 👌 Return frozendict for stored Dict nodes [[#6185](https://github.com/aiidateam/aiida-core/pull/6185)]: This is a quick & dirty attempt at fixing the issue where once a `Dict` node is stored, changing nested content fails without raising an error.
* 👌 Allow remote copying/symlinking between computers with same hostname [[#6196](https://github.com/aiidateam/aiida-core/pull/6196)]: If I want to use a different scheduler on the same computer for different calculations that need to "remote copy" files between them, or have some data that I have transferred from a different project, copying/symlinking fails since the UUID of the computers are different. Here I suggest to allow copying/symlinking between computers that have the same hostname.

Jason:
* Fill the questionaire of NumFOCUS [CoC](https://forms.gle/WCgrnEi43BweAEDu8), they are providing a CoC that sub-projects can reuse and even handle some management to them.
* PR merged (#6189) [Docker: Disable the consumer timeout for RabbitMQ](https://github.com/aiidateam/aiida-core/pull/6189), with some misc enhancement of image, [adding graphicz and rsync](https://github.com/aiidateam/aiida-core/commit/bf631f18bcda350aab63fab7279b7c4b9ae0df52) and [pinning jedi<0.19](https://github.com/aiidateam/aiida-core/commit/fae2a9cfda461a26e80b648795e45087ea8133fd).
* [The "Community" category](https://aiida.discourse.group/t/about-the-community-category/23) is created for plugin developers to create post and advetise the new update on plugins.
* I really enjoy writing documentation with using [mkdocs-materials](https://github.com/squidfunk/mkdocs-material), which support some fancy and useful but easy to features such as code snippet annotations. Might be fit for aiida-blog.

Kristjan:
* still working on the tests of https://github.com/aiidateam/disk-objectstore/pull/161

Xing:
* **PR**:
* [Add link serialize](https://github.com/aiidateam/aiida-core/pull/6199): defines the yaml constructor and represent for the link. Use caes: e.g. save link in the checkpoint.
* [AiiDA Monitor inside AiiDAlab (Draft)](https://github.com/aiidalab/aiidalab-qe/pull/567): the user can monitor the real-time job status (energy, trajectory) in the GUI. It's a good use case for the AiiDA Monitor.
* [**WorkTee** Support set parameters from protocol](https://github.com/superstar54/aiida-worktree/pull/8): add set_from_protocol for node. By the way, it seems there is not clear standard how to implement `protocol` in AiiDA WorkChain. In QE, we use [`ProtocolMixin`](https://github.com/aiidateam/aiida-quantumespresso/blob/9061ea5df65e4fe95f77309d9abb5a3c7f64bb9f/src/aiida_quantumespresso/workflows/protocols/utils.py#L11C13-L11C13), while in other package, e.g. aiida-siesta, it use [`get_filled_builder`](https://docs.siesta-project.org/projects/aiida-siesta/en/stable/utils/protocols_system.html). The doc is also not clear.

### Specific Agenda Items