SolidOS Team Meeting

# SolidOS Team Meeting * Date: 2022-30-11T16:30:00Z (UTC) * Call: [https://meet.jit.si/solid-operating-system](https://meet.jit.si/solid-operating-system) * [Previous meeting link]() * [Next meeting link]() * Chat: [https://gitter.im/solidos/solidos](https://gitter.im/solidos/solidos) * Repository: [https://github.com/solidos/solidos](https://github.com/solidos/solidos) * Meetings home: [https://solidos.solidcommunity.net/public/SolidOS%20team%20meetings/](https://solidos.solidcommunity.net/public/SolidOS%20team%20meetings/) ---- ## Present attendees * Alain, Angelo, Noel, Timea, Matthias, Jon, Tim, Rahul, Tiger, Sharon ### Scribes * Jon, Timea --- ## Topics ### Round Table #### Alain * Worked on mashlib, repo added to SolidOS to be used for tests; added documentation, still need to add docs to use CSS in solidOS repo. * Worked on rdflib, asked to use more recent dependency for json-ld, there was a ts error showing up, resolved that (there was an await missing); the PR was approved, not merged yet. * Asked Angelo to validate Tim's work on something(?) * Worked on solid-pane(?) also, along with Tim * Tim: I took your version and changed it because I had some problem. It is more accepting of different inputs. * Solid Lab Flanders is making something that will create a lot of accounts on solidcommunity.net, in the hundreds. They're asking ppl to put results of readings into pods (a research project at a University). Beginning today or yesterday. #### Angelo - Continued to work on PodOS. - do we have anything extracting metadata into RDF? - Tim: the Sem Web community used ot have some stuff. Not sure about PDF. - Noel: they do that types of thing in TrinPod, but I don't think it's open source #### Noel * Work on preparing libraries, they don't work in some env's (for example Vite). Issues with N3 library, they work fine with Webpack but not something else. The solution I've found is to just bundle the problematic dependencies with webpack and include them in my library. Not the best solution, but it works. * Learn more about this in the repo: https://github.com/NoelDeMartin/solid-utils/tree/next/external #### Timea - Had a mtg on webid spec, collected some tasks related to that. #### Matthias - Did not implement anything, update about servers, solidweb.org 2.6 K pods, solidweb.me 140 pods. - I have a technical topic later. #### Jon - Chase prepared a presentation for our meetup. But we got 8inches of snow in Minneapolis, so nobody showed up. However Chase and I used the opportunity to meet on zoon and practice sharing presentation on Zoom. - We will reschedule the meetup maybe mid december. #### Tim - I wanted to do tests in contacts-pane. i copield teh tests from profile-pane but it crashed in the middle: "I get node_modules/jose/dist/browser/index.js:1 export { compactDecrypt } from './jwe/compact/decrypt.js’ SyntaxError: Unexpected token 'export" -> I am stuck. - A week or so ago went to Korea, received a Peace prize, related to data sovereignty. We should all feel good about this, as it relates to the work we're doing, and how it benefits civilization. #### Rahul - Here to learn about SolidOS #### Tiger * I want to see how to integrate Soldi into CasaOS - as a client -> how can we make our user from CasaOS able to access a Solid Pod. I followed a tutorial and am able to write to a Pod. * The second is how to use CasaOS to host a SolidPod. Using Docker should eb fine but we are looking functionality how to use Soldi Pod subhosted along with CasaOS. * both points at early stage, questions will follow in the chat. * Tim: is this on mobile? * Tiger: in a browser. Backgrouns on Linux but interface is in browser. #### Sharon * ### Technical topics #### concerning webid-profile on solidweb.me (Matthias) * Pros and cons regarding deploying the thing below(?). We have to extract from specific instances. Alain has found the possibility of making it work with NSS through templates(?). Gathered pros and cons, and wants to discuss whether to deploy this. * Want to know if I should deploy the chnages or not? * Alain: it would be easier for people creating new pods to have some directories in it. If one does not have mashlib it is difficult (mashlib creates them). I personally did that for the tests of mashlib. It will make teh comparison easier. * Noel: one of the cons means - it breaks current behaviour- which exactly? * Matthias: teh old pods will not have it. I was thinking to make a bash script to chnage it - but this would not be a good idea. * Noel: personally I do not think the difference is a problem. They are anyway different than other pod providers. As long as they apply to teh solid protocol, they can be different. One of the things you were saying is that is has teh same structure as css - but if it is not according to spec is an extra. It is not an issue if it is not as long as it is not in teh spec. * Rahul: what is your upgrade patterns in CSS and NSS. We are workign on a Solid notification protocol - when that comes in: are oyu going to update NSS and CSS or just one. * Alain: since I am the only maintainer, I am not sure I will be able to make the changes. I need some help. * Rahul: how do you progress when you have discrepancies in standards. If Matthias makes a breaking change - if you have multiple levels at which you have differences --- I want to know how changes are handeled? * Tim: the notification protocol is very important. Most things we talk about here would be about to look at the version used on the server. When it comes to the user pods, well the app should update what is missing. IN general we have to be as forgiving as possible and conservative in what we do and liberal in what we expect. With contacts- pane we had that same example and we decided to change the data. * Alain: in NSS we already implemneted the change in protocol and made a batch to update all existing servers. * Rahul: I expect this chnage to come in the next few weeks, please consider. * Noel: if tehre is any change in the spec, it is important to open an issue to keep track. If you see something not spec compliant open an issue. * Timea: this is a very important point Rahul raised; I will raise this point to the Solid Admin (?) team to discuss how at the organztion level we can be more transparent when changes occur. We can't force ppl to update code (its a volunteer org), but we can let ppl know we have updates on the website, and ask for help. The Forum will discuss and decide. * Noel: There are tests for determining which servers are implementing the specs * Tim: You can even point it at a pod you're using, if you wonder why things aren't working. * Matthias: I think we should deploy it to make it easier to discover the profiles and the type indexes. * Noel: OK. I think we're done with this topic. * we have https://github.com/SolidOS/css-mashlib/tree/main/templates/pod * the question is whether to deploy this or not on CSS instance solidweb.me * let's do a brainstorm or gather some pros and cons * pro - compatibility with NSS behaviour - experiences to prepare for sc.net migration - simplification of exploration of documents when a client asks for profile - (publicTypeIndex, privateTypeIndex, settings) - ... * con - breaking of current behaviour (continuity) - maybe to consider Capital 's' of <settings> or not - ... * opinions (to be documented) ... possibly vote ? action items ? #### Live debugging session getting Tim unstuck - Tim is having issues having tests run, it seems to be related with the jest config. The code can be found on https://github.com/SolidOS/contacts-pane/tree/dataModel2 - The problem seems to be related with the version of the `jose` dependency that is used during jest execution, it's taking the browser bundle where it should use the node version. ---- 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)