# AiiDA Team Meeting 2022-04-06
###### tags: `team meetings`
###### time: 10am CET
[TOC]
### Present
* Marnik
* Chris
* Simon
* Louis
* Jason
* Francisco
* Sebastiaan
* Giovanni
### Catch-up round
*Max. 3 minutes each*
Marnik:
* Going to give a small AiiDA/AiiDAlab talk+tutorial at my home university of Antwerp in the week of May 16th.
* `aiida-upgrade` is up and running. Still might add some more features, feel free if you have suggestions on what to prioritise.
Sebastiaan
* **Releases**
* [`aiida-core==1.6.8`](https://github.com/aiidateam/aiida-core/blob/v1.6.8/CHANGELOG.md): warnings for incompatible RabbitMQ versions
* **Merged PRs**
* Docs: add section on RabbitMQ compatibility [[#5469]](https://github.com/aiidateam/aiida-core/pull/5469)
* **Open PRs**
* Remove remaining django remnants [[#5468]](https://github.com/aiidateam/aiida-core/pull/5468): Fixes, simplifies and cleans up legacy code that was once taken from Django that now has more succinct solutions using the standard library.
* Computer: fallback on transport for get_minimum_job_poll_interval default [[#5457]](https://github.com/aiidateam/aiida-core/pull/5457)
Simon:
* Fixed plumpy test issues [[#228]](https://github.com/aiidateam/plumpy/pull/228).
* In talks with representatives from Microsoft to run AiiDA tutorial on AiiDAlab instance sponsored by Microsoft Azure.
* Worked with Louis on the declarative workchain.
Jason:
* [Open issue] Protect methods such `run` from WorkChain being override https://github.com/aiidateam/aiida-core/issues/5467
* Another caching issue when running process_A -> process_B, aiida uses the same name for remote path of process B and unable to copy to exist path.
* aiida-optimade migrate to v2.0 [PR](https://github.com/aiidateam/aiida-optimade/pull/331) open.
Chris:
* Rewrote aiida-lammps (with Jonathon Chico) <https://github.com/aiidaplugins/aiida-lammps/pull/35>
* Moving to aiida-core 2.0 etc
* Starting to work on workchains, inline with common workflows
Francisco
* Summary for 2.0 and participating in the company collab (see below).
Giovanni:
* Only comment: not call it `ctx` for the sub-namespace of nodes
* Suggestion after discussion: `base`
* Working on contract with company to fund ~1 year to develop plugins and (private) workflows
Louis
* Quick demo on [DeclarativeChain](https://github.com/louisponet/aiida-tools/#declarative-chain)
### Specific Agenda Items
#### Outstanding issues for 2.0 release ([milestone](https://github.com/aiidateam/aiida-core/milestone/18))
* Last refactorings
* Refactor `Node` methods ([discussion](https://github.com/aiidateam/aiida-core/discussions/5465)): instead of inheriting methods from mixins, the node now has an object (`NodeContext`) to better "containerize" these functions.
* [PR-5439](https://github.com/aiidateam/aiida-core/pull/5439) for `NodeRepositoryMixin`
* [PR-5442](https://github.com/aiidateam/aiida-core/pull/5442) for `EntityAttributesMixin`
* [PR-5445](https://github.com/aiidateam/aiida-core/pull/5445) for `EntityExtrasMixin`
* [PR-5446](https://github.com/aiidateam/aiida-core/pull/5446) for `comments`
* Refactor `AbstractRepositoryBackend` ([issue](https://github.com/aiidateam/aiida-core/issues/5451)): to remove the 'hardcoded' requirement in the `NodeRepository` to use the local filesystem as a temporary sandbox to put files while constructing the node and then store them all at once in the backend repository.
* Not necessary for 2.0
* Last fixes for outstanding problems
* Remove remaining django remnants ([PR #5468](https://github.com/aiidateam/aiida-core/pull/5468))
* The `get_minimum_job_poll_interval` default should be set by the `Transport` plugin instead of the `Computer` instance (an explicit non default value can still be set on the computer) ([PR #5457](https://github.com/aiidateam/aiida-core/pull/5457)).
* Not necessary for 2.0
* Fix the place where the default user is being stored (from the `User` class to the `StorageBackend`) so that it loads the correct one on switching backends ([PR #5460](https://github.com/aiidateam/aiida-core/pull/5460)).
* Reinstate old profile after using the `profile_context` ([PR #5461](https://github.com/aiidateam/aiida-core/pull/5461)).
* Add a validation to check that nodes are from the same backend in `validate_link` ([PR #5462](https://github.com/aiidateam/aiida-core/pull/5462)).
* <https://github.com/aiidateam/aiida-core/pull/5448> ("concolitdates" SQLite backend)
* Last Tests:
* Testing the repository migration and maintainance ([discussion](https://github.com/aiidateam/aiida-core/discussions/5379)) -> Migration seems tested, did people run maintainance?
* Testing the archive migration ([discussion](https://github.com/aiidateam/aiida-core/discussions/5407))
* Finishing details:
* Run the tests with full verbosity to eliminate warnings before releasing ([issue 5282](https://github.com/aiidateam/aiida-core/issues/5282))
* Make sure key external packages/plugins are updated to 2.0 ([issue 5284](https://github.com/aiidateam/aiida-core/issues/5284)): send poll through slack?
* plugin migration script for AiiDA v2.0([issue 5335](https://github.com/aiidateam/aiida-core/issues/5335))
* Event after the release, reach out to advertise just before the release.