Fully migrate old roadmap

[chrisjsewell]

The goal is to close all issues from the "old" roadmap project here: https://github.com/orgs/aiidateam/projects/3 and move them here, closing eventually that project board.
Not all items from there should be moved, in some cases those should just become issues

High:

• Refactoring out RabbitMQ (@sphuber todo)
• maximum recursion depth reached" when submitting ~200 workchains [GP: should this just be a highly-important issue? Probably not needed to be in the roadmap. Or better: we shoudl have a general roadmap item on "robustness", as this is an important item, and this should just be a linked issue] ("maximum recursion depth reached" when submitting ~200 workchains aiida-core#4876) (remove from roadmap)
• General overview of AiiDA capabilities on the docs @giovannipizzi
• General improvements to usability
• Template computer/code setup and new code registry configs (Usability: Make it easier for users to setup known computers and codes #4)
• Subproject - Improve profile backups [@ramirezfranciscof] (Usability: Make it easier to backup and restore full AiiDA installations #11)
• push/pull @chrisjsewell

Mid:

• Clever caching policy involving RemoteData @unkcpz (Defect: Improve the caching policy when the RemoteData is cleaned up #13)
• Testing framework for workflows
• Rethink the distribution between what is set during computer setup (immutable) and computer configure [@ramirezfranciscof] (Usability: Make computers and codes entities more flexible #12)
• ContainerizedCode: Add support for running codes within Docker containers @sphuber Usability: Allow users to relaunch a previously completed process with minimal required setup #9
• Domain-agnostic AiiDA core (domain-specific materials-science plugins) (dependent on data migration for plugins) (@mbercx)
• Migration of data nodes for plugins (@mbercx)
• REST-API workflow management (dependent on serialization/deserialization)
• Investigate how to ensure easy "re-running" of a calculation sequence that is stored in the AiiDA provenance graph @sphuber Usability: Allow users to relaunch a previously completed process with minimal required setup #9
• verdi computer delete should allow user to delete computers with associated nodes [GP: issue rather than roadmap?]

Low (@chrisjsewell)

• Hierarchical graph visualization [GP: issue rather than roadmap?] (@eimrek)
• Make the optimade structure first-class citizen that can import/export to AiiDA @unkcpz (Future: Allow users to use the optimade structure as first-class citizen that can import/export to AiiDA #15)
• Cross-computer Scheduling
• Two-factor identification @giovannipizzi
• Support Python-based codes (@sphuber) (Usability: Make it easy to run Python-based codes #19)
• Hide data when exporting, keep only the metadata (e.g. the fact there is a node) (@sphuber) (Usability: Allow exporting of (parts of) the provenance graph with just metadata #18)
• CLI generation for ORM classes (merge discussion with REST API generation of data classes)
• REST-API plugin (early one, GraphQL) - discuss first serialization/deserialization
• CLI for repository browse [GP: issue rather than roadmap?] (@giovannipizzi)
• Standardised serialisation/deserialisation of data nodes [GP: to be framed as a user-story, now it's a technical task for an issue] (@sphuber) (Usability: Provide generic mechanism to serialize and deserialize data from and to AiiDA data #17)
• Create query builder from natural language @unkcpz

[sphuber]

I will convert the following items to separate issues:

• Investigate how to ensure easy "re-running" of a calculation sequence that is stored in the AiiDA provenance graph
• ContainerizedCode: Add support for running codes within Docker containers

Also the following entries are really the same I think:

• REST-API workflow management (dependent on serialization/deserialization)
• REST-API plugin (early one, GraphQL) - discuss first serialization/deserialization

[ramirezfranciscof]

I can do the migration for:

• Subproject - Improve profile backups
• Rethink the distribution between what is set during computer setup (immutable) and computer configure

Note: probably also won't have much time today, but try to do it tomorrow or early next week.

[unkcpz]

I'll do the migration for:

• Make the optimade structure first-class citizen that can import/export to AiiDA
• Create query builder from natural language
• Clever caching policy involving RemoteData

Maybe also convert already the AEP in the discussion for new docker aiida image

Note: don't have time this week, but will do it next week.