# AiiDA Team Meeting 2022-05-18
###### tags: `team meetings`
###### time: 10am CET
[TOC]
### Present
* Simon
* Sebastiaan
* Jason
* Giovanni
* Leopold
* Marnik
* Kristjan
### Catch-up round
*Max. 3 minutes each*
Sebastiaan:
* **Planning**
* Opened new [milestone for v2.1](https://github.com/aiidateam/aiida-core/milestone/46). I have added some closed and open issues that I think should go in. Let us know if you have other features you would like to go in.
* **Open PRs**
* Deprecate `Profile.repository_path` [[#5516]](https://github.com/aiidateam/aiida-core/pull/5516): This is specific to the `psql-dos` backend and so is moved there.
* Refactor the `Code` data plugin [[#5510]](https://github.com/aiidateam/aiida-core/pull/5510): Original `Code` is deprecated and original functionality is now implemented into two separate classes, `InstalledCode` and `PortableCode`, which represent the old "remote" and "local" code. The constructors are simplified and CLI commands to setup a new instance are generated dynamically from the entry points. Approved by Jason and ready to go.
* REST API: make the profile configurable as request parameter [[#5054]](https://github.com/aiidateam/aiida-core/pull/5054): Rebased and ready to go. I would vote to merge this and mark it as an experimental feature for people to use and test out.
* **Merged PRs**
* Make storage backends pluginnable and dynamically loaded through entry points [[#5501]](https://github.com/aiidateam/aiida-core/pull/5501): Being used by the `aiida-s3` proof-of-concept. Should mark that this is an experimental feature and should be used at own risk. Not quite sure how migrations would work yet.
* Remove legacy `tests/utils/configuration.py` [[#5500]](https://github.com/aiidateam/aiida-core/pull/5500): just clean up of tests
* Deprecate the method `aiida.get_strict_version` [[#5512]](https://github.com/aiidateam/aiida-core/pull/5512): no replacement because it is not really needed
* **Misc**
* Create new API token for `aiidateambot` account on Dockerhub and use that for deploy action. Who can/knows how to generate this token?
Simon:
- Completed first version of the *AiiDAlab on Azure* terraform template.
- In the process of setting up deployment for tutorial @ University of Antwerpen.
Jason:
- Not too much to report.
- Review Code refactoring PR https://github.com/aiidateam/aiida-core/pull/5510
- `aiida-code-registry` for aiidalab's quick setup.
Giovanni:
- Beside general maintenance, please identify 1 or 2 main issues that you want to work on related to AiiDA (in the next ~3 months, focus on high priority ones) and report in the next meeting, so we prepare a roadmap and know who will work on them. Examples: critical bugs (recursion errors), sharing capabilities, containerized codes, REST API changes/improvements, ...
- Check topics here: https://github.com/aiidateam/aiida-core/wiki/AiiDA-release-roadmap, don't pick more than 2 (3 max), be realistic
- Finalize choice of date of tutorial, write on aiida.net/events (people start asking), define "organizing committee"
- Spoke with people at PSI who also plan to work on Kubernetes @ CSCS (I will put Simon in contact with them on the next occasion)
Leopold:
- Where to add regression test for [profile switching issue](https://github.com/aiidateam/aiida-core/issues/5506) - in the system tests?
- Just some [ideas/discussion](https://github.com/aiidateam/aiida-code-registry/issues/60#issuecomment-1129424537) on how to make it more convenient to distribute computer/code configurations
Marnik:
- This Friday presentation + AiiDA tutorial + AiiDAlab testrun @ University of Antwerp.
- Re Gio's point on main issues to work on: mine will be updating the tutorial material to 2.0 and task farming with `aiida-hyperqueue`.
Francisco:
- Adding a couple of quality of life features to the `verdi group list`: from [#4572](https://github.com/aiidateam/aiida-core/issues/4572) changed the list order to use label as criteria in [#5523](https://github.com/aiidateam/aiida-core/pull/5523) and now working on autocomplete.
### Specific Agenda Items
High priorities during brainstorming:
- recursion error: high priority (Sebastiaan interested but not sure how to check/debug)
- RabbitMQ replacement (Chris mentioned he's interested; good to have a discussion on features etc. before starting implementation)
- REST API (and web interface) for AiiDAlab (Simon)
- GP: start from common workflows?
REST API for workflow management prototype: https://github.com/aiidateam/aiida-restapi