SolidOS Team Meeting

# migration from NSS to CSS * Date: 10.24.2023 15:00 (UTC+2) * Call: [https://meet.jit.si/solidcommunity-net-nss-to-css ](https://meet.jit.si/solidcommunity-net-nss-to-css ) * [Previous meeting link]() * [Next meeting link]() * Chat: [https://gitter.im/solid/solidcommunity.net](https://gitter.im/solid/community.net) * Repository: [https://github.com/solid/solidcommunity.net](https://github.com/solid/solidcommunity.net) * Meetings home: ---- ## Present attendees * Alain Bourgeois * Michiel de Jong * Mahdi * Timea Turdean ### Scribes * Timea --- ## Topics ### Introduction of people in the meeting * Timea introduced herself and gave an overview about SolidOS and solidcommunity.net * Alain is introducing himself. Talking about the challenging of his responsabilities from rdflib to NSS, across SolidOS. He is trying to find as much as possible a transition to not break anything. It has become too much of a responsability. * Michiel in agreement on wanting to develop the Solid team and SolidOS projects. He met Mahdi and introduced him to Solid community. He is ready to free up some of Mahdi's time. Raised the topic that the code run on solidcommunity.net should be open source, easy to contribute to. Now we have a migration script from Ruben: https://github.com/RubenVerborgh/NSS2CSS * Alain: "I personally suggest we apply for the 10k to support any activity on solidcommunity.net" * Mahdi is introducing himself, learning to become a DevOps engineer, working with Michiel (contractor NLnet grant based). Got to know Solid 4 months ago. ### expectation management * Michiel: which code will run on solidcommunity.net * Timea: will Mahdi work just on migration or admin in general with or without migration * Alain: can we add Mahndi as admin? ** expect for Mahdi to be introduced official as adminin the Solid Team. ** I want to make sure we all agree about the risk of adding new people. ** Explanation on his expectation to vote Mahdi in as admin: he wants to have an official Solid Team meeting and discussi it there. * Mahdi: I would like to know what is expected from me (admin and migration) also looking forward to meet the team & solid process. * Michiel: if Mahdi is approved by the team and wants to do all the tasks, Ponder Source will help finance him during work hours. Mahdi would you like to admin the server? * Mahdi: I would like to know more. * Timea: sharing her experience of admining inrupt.net ### solidcommunity.net system administration #### context - Digital Ocean resources management (Alain and Jackson got recently access - but not to billing) seems that Justin and Oolivo have access to OnePassword descibed nowhere in the solid ecosystem - solidcommunity.net server access (droplet in Digital Ocean wording) : SSH key admin are listed in the solid system administrators admin should be approved in a solid team meeting should be better documented howto add/remove an administrator - servers are running under PM2 management : everything is documented in the wiki #### discussion * Alain is screen scharing Digital Ocean login - we just confirmed that there are weekly backups done for every week, and we have acces to them. * Michiel would like to discuss Alain's question: https://matrix.to/#/!VAJLTawStGAyYwzTTY:gitter.im/$8dbwvoo6M--8Q4vK-MckIVm1WIYr_HBxeH3Ye1r8N5w > there need to be some clarification on CSS maintenance and community involvement, compliance tests... > Have you participated in coding / planning / specification of CSS ? > In such situation what is the meaning of community involvment ? * Alain: I am not at all happy with how CSS was pushing to replace NSS. Most of the reason I have is because, both are University projects, that is not what I am against, it is hard to bring them into production. Mainainting and upgrading NSS was already a tremendeous amount of work and not a lot of peopel wanted to support the project. Nobody is supoorting NSS anymore. Than I discovered that CSS is a new version, created also at a university. They have created something that is, in my opinion, a strange Solid representation. It is open but when you want to use it you have to create a lot of parameters, you cannot use it as itself. * Michiel: to use it you need teh code and configuration. This is how it works and it does work right? * Alain: yes it does owrk. But how do you manage it in teh future? * Michiel: are you afraid that the code is imposible to maintain? * Alain: yes and more than that. I need expertise on the configuration. I do not understand why it was made so complicated. In some way you cannot create something that is full open, but than take it under an organisation. * Michiel: we could install CSS7 and it would be better than NSS or? * Alain: why? * Michiel: the code is cleaner and I have the impression is that is is better and improved. So are you maininly considered that you cannot contrinbute or that noone can? * Alain: the problm is not me. I have not seen anyone contriibute into the group. * Michiel: we were not contributing because we are not using it. But if we will use it we will contribute. At the moment, I do not think we have many alternatives. It was the plan to move since years and we should not postpone it another year. So you are saying you are unhappy with the architecture of CSS, I understand. Do you propose an alternative? Or is the alternative to keep NSS? * Alain: the alternative is terrible, is there any else? * Michiel: new CSS, stay on NSS; or PHP server or... some other server. Picking another server at this point is a huge thing and it doe snot feel productive. It is a bit late in the game and nothing is perfect. CSS code base is hard but at least it is in typescript. Emelia suggested to chnage the package structure, and use package.json and maybe it is easier to maintain.... If we deprecate NSS and put more effort on CSS there hopefully will be more. ## Not discussed topics: ### NSS to CSS migration #### context - proposal of a migration experiment on the test server : solidcommunity.net:8443 - CSS V7 has a full new identity provider structure - need to be tested. V7.01 is already out - the bad one is that CSS is an email/password driven authentification - The good news there seem to be multiple email/password - we need to question some issues - reset password - delete pod - ... - target CSS-mashlib version (it has to be redone for each new major version) CSS is a like a progiciel it need some parameters to make it NSS compatible. - the best is to use the config generator to select the needed functions - default pod structure at pod creation - update to latest mashlib version - NSS2CSS migration script for filesystem - The good thing is that password encoding is the same in NSS and CSS. This is a tremendous simplification - CSS has a batch pod creation mode Basically this allow a rather simple pod creation system for any version of CSS (not only CSS v7) #### discussion ### community involment in CSS #### context - CCS-mashlib version : npm publish ? - CSS ? - CI test-suite integration ? - SolidOS stack management with CSS : howto use Watch with CSS ? #### discussion ### NSS long term support ? ## actions --- This template is based on the [W3C meeting template](https://github.com/solid/specification/blob/main/meetings/template.md) [Code of conduct](https://github.com/solid/process/blob/main/code-of-conduct.md)