Migration of other domains

[edan-bainglass]

AiiDA ecosystem is scattered across "domains" (aiida.net, aiidateam.github.io/aiida-registry, aiidalab.net, various docs, etc.). Consolidate here?

[giovannipizzi]

My comments:

• OK to have the registry on aiida.net - the old one should point or redirect to the new one
• OK to have the docs on aiida.net, if this helps in making things simpler, and also if it helps with the search. (Important to assess hwoever carefully pros/cons - if it takes a month of work ot make it work with limited advantage, I would probably not do it). However, I think it's important to limit this to aiida-core, and the few packages we really maintain as a core AiiDA team. Essentially this should be the repos under github.com/aiidateam. We should go through them, move away those we don't maintain anymore, or archive them (@khsrali maybe we should sit and do it together?). Importantly I would not put on aiida.net any docs of external plugins. Users would end up contacting the core team for any fix. It's better to keep them just linked from the registry, and it's clear then who's maintianing them. It also avoid a lot of maintenance if there are issues etc (and I don't see a real benefit TBH)
• I would keep any aiidalab domain separate - they are two separate "products" with non-identical development teams and different goals (even if of course related).