---
# System prepended metadata

title: Solid Team Meeting

---

# Solid Team Meeting
November 11th, 2020

Meeting URL: https://us02web.zoom.us/j/82810582560?pwd=bG0vbGNuMHBUSTJKOEUxbzh2WXludz09

# Present

- Jeff Z
- Timbl
- Dmitri Z
- Nicolas AS
- Marrelle B
- Jackson M
- Sarven
- Vincent (partly)

# Agenda

- Editor / Panel Updates

- Solidproject.org 
    - Recap of recent work updates
    - What's next / work to be done

- Solidcommunity.net
    - Recap of what's been done since the migration

- SolidOS operating system
    - Recent updates and current work
        - https://github.com/solid/contacts-pane/issues/18
- any other things

# Action Items

- Setup Gitter chat for Solid Team
- URI Persistence policy for solidproject.org for spec documents.
    - Sarven proposes to make a draft PR to get the discussion started.
- Integrate solidproject.org to netlify -> an account already exists for other solid org repos
- PR for https://github.com/solid/solidproject.org/issues/247 - Sarven
- Map task breakdown to GH issues to update the solidproject.org website.


# Editor/Panel update

## Technical discussion around the spec document

- Sarven: **Ecosystem spec** brought to shape, by removing things that are unclear, or too far off in the future to be part of the current spec. The spec includes:
    - A protocol (client/server)
- The spec should be hosted under `solidproject.org`
    - The identifiers of the spec documents, as well as panel discussions, should be commited to for persistence.
        - IRI templates ?
    - This would require a "Persistence policy" - https://github.com/solid/solidproject.org/issues/247
- Pipeline to produce the actual spec document:
    - Travis 
    - bikeshed
    - respec
    - Travis is quite slow, maybe should be replaced using GH actions
    - Netlify could be use for previews
    - Justin: Should the source text be directly in HTML, or is MD easier to edit/discuss ?
    - Dmitri - personal experience.. changed from bikeshed to plain ol HTML authoring
- The `solidproject.org` website should be hosted on a Solid server.
    - The GH repo could host "plain" HTML, and it should be pushed from there to the Solid server hosting `solidproject.org`. 
    - That would be a strong message to the outside world that the Solid spec can be used in the "real" world. 
    - Each document would be directly editable, access right could be managed at fine granularity...

## Solid-OIDC

- The spec draft has matured, there are just some discussions around the access token.

## Auth panel

- Proposition of the ACP mechanism by Emmet T. (Inrupt)

## Interop panel

- App interoperability draft iterated on
    - Shape tree spec and primer, work with Ghent university to have PoC/implementation.


# solidproject.org update

- The update was focused on 
    - making it clear to a new visitor what Solid is at a first glance
    - Updating the tutorials
- A second round of updates is going to be required for secondary content
    - interop, data model, security model, additional tutorials, user section, app listing, newsletter...
-  Clarifying the Solid roadmap
    -  Published on solidproject.org, but documented in RDF and being a standalone project.
- App listing update
    - Many apps no longer work, so we should reach out to the authors.
    - The utilities from the library list should move to the app listing

# solidcommunity.net

- Creation of a role in the process, "System operator", to manage the solidcommunity.net server. This allows to set expectations, and to have active maintenance of the server.
    - Eric P.
    - Michiel D.
    - Alain B.
- Creation of the "Acceptable use policy" for the service - Published at https://github.com/solid/solidcommunity.net#solidcommunitynet-acceptable-use-policy and https://solidcommunity.net
- Sarver: Should we document the "intent" of Solid, and reference it ? In order to say basically we want to avoid sharing misinformation, harmful things...

# SolidOS

- Group maintaining the Data browser and Mashlib
- Maintain NSS
- Test suite development
- Nextcloud/Solid interoperability project

see also PHP server: ( was the reference to https://github.com/linkeddata/ldphp in the call? I don't know another PHP-based pre-Solid RWW server - Sarven)

https://github.com/pdsinterop/php-solid-pubsub-server

another product of https://pdsinterop.org/
which is a project to bring together NexxtCloud and Solid. Everyine on NextCloud will be able to have a solid pod.
