---
# System prepended metadata

title: SolidOS Team Meeting

---

# SolidOS Team Meeting

* Date: 05.24.2023 17:00 (UTC+1)
* 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

* Chase, Jon, Jeff, Alain, Noel, Matthias, Rahul

### Scribes

* 

---

## Topics

### Round Table

#### Chase

- Still tinkering with Solid panes.

#### Jeff

- Organizing Solid Practicioners group and tomorrow's meeting.

#### Alain

- Published new rdflib version 2.2.33 with n3-patch.
- Migrated CSS solidcommunity.net tests servers on port 3000 and 3001 from CSS v5 to v7.0.2 that solved a bug about subdomain version.
- NSS resolved Append for non existing files using PATCH in NSS. Need to add test in NSS
- signed Chat : shall publish a new version of SolidOS but will have to revert inrupt authentication library version to 1.16 because more recent do not build with SolidOS.

#### Jon

- Working on Solid Onboarding group.
    - Updated code of conduct following Sarven's feedback.
- Making a form to submit resources.
    - Creating a vocabulary for these new resources. One of the issues with these is that many are outdated, so will add a property to indicate when a resource was last updated.
        - Jeff: Before creating a new vocabulary, you should check if you can use an existing one. Let's try not to reinvent the wheel.
    - Noel: How will you make sure that something is up to date?
    - Jon: It could work like a wiki, everyone can update it.
- Had some issues joining the Solid Team (problems related with joining the Solid Community Group in relation with employment status).
    - Jeff: You probably can join the group as an individual, it doesn't matter that you're employed; that doesn't mean you're representing the company in the group.

#### Noel
- Updating [Ramen](https://ramen.noeldemartin.com) app, some small details to work on
- is everyone signed up to mailing list, the number of emails and amount of information can be a little overwhelming
    - a forum  can be more easy to filter, but the mailing list cannot be filtered, I get many of them, not a good experience
- Jeff: Which mailing list, the W3C Community Group? They sometimes get sidetracked on topics. I have a similar opinion, but I use an email filter
- Noel: The list is public-solid@w3.org It would be good to see just info about voting
- Jeff: maybe make that request to the group, maybe they could create a summary with info about  upcoming votes 

#### Rahul
- proposing a session called Real Time Solid, to discuss using real time features (CRDTs), in Solid Symposium. Just sent in a proposal
- Noel: I will probably attend, may do a session with someone else if they'd like, but probably not by myself
- Rahul: maybe you could participate in a panel topic

#### Matthias
- no updates, still have 3 servers running
- applying for co-chair (in the group we were discussing earlier?)
    - one proposal re: CSS migration, perhaps solidweb.org(??) could run NSS, to have this still running somewhere
    - Rahul: about the co-chair, it sounds like it will be about moderating, simple work, the more difficult responsibilities will continue to be delegated, i.e. it's not necessary to know Linked Data, but to be able to make people feel welcome

---

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)