| Feature | Description | Design phase | Implementation |
|---|
| Enhancement of the Team App | Managing a collab's team is a rough experience. This feature is about adding capabilities to the Team App to improve the user experience. | 90% | 70% |
| Accreditation workflows | Accreditations represent levels of trust the community gives to users. | 70% | |
| Registration of new users | Currently, only SGA2 accredited users have access to the Collaboratory. This feature is about giving access to other users. | 50% | |
| Group App | Power users need to manage groups in order to organise permissions in collabs and services. | 90% | |
| Software Catalogue | The Software Catalogue showcases the services, applications and libraries created by the community. It needs to be migrated to the new Collaboratory. | | |
| JupyterHub on Kubernetes | Jupyter notebooks are a key feature of the Collaboratory. Deploying JupyterHub on Kubernetes will bring state-of-the-art notebooks to the community. | | |
| External App integration | The Collaboratory aims at being an extensible platform. Integrating services provided by the community is an important goal. | 50% | 30% |
| Forum | The forum is an important channel of communication with users. It needs to be migrated to the new Collaboratory. | | |
| Analytics | The European Commission requires having statistics on the usage of the community services. This feature aims at providing the common tools for this. | | |
| APIs | Opening the Collaboratory capabilites to developers through APIs: Collab, Team, Group, Drive... | 30% | 20% |
