# Solid Team Meeting
January 13th, 2021

## Present

- Justin B
- Marrelle B
- Kay K
- Jackson M
- Jeff Z
- Vincent T
- Sarven C
- Dmitri Z
- Nicolas AS

## Agenda

* Editor Update (Spec and Panels)
** https://solid.github.io/specification/#work-items
** https://github.com/solid/specification/pull/216
* solidproject.org
** Automated push to TR - https://github.com/solid/specification/pull/216
** Terms of Use ( https://github.com/solid/solidproject.org/pull/489 )
** Access/transparency of [e-mail] ( https://gitter.im/solid/team?at=5ff5c957cd31da3d9a961f41 )
* Social / Community Outreach
** Infographic
** Solid World Update
* Open Discussion (Add or Update)
** hackmd/@solid/ access controls ( https://gitter.im/solid/team?at=5ffece9e9632f63d87144fd2 )

Action Item:

JB: Get Ted looped into team addresses

Action Item: route info@ to [e-mail]

Action Item: Will be the e-mail communication hub for inbounds - will route inbounds to appropriate team members for response to inbounds, and if you respond you must let her know.

Action Item: Marrelle will be putting together a standard response template (will be sure to include link to forum as well per suggestion from Jeff Z)

# Editorial update

## Protocol

* Plan for the CG: commit to a charter

## Interop

* Goals have been set for 2021
* ShapeTree spec draft is 95% complete
** Informed by a JS implementation (being refactored into TS), with the goal of having a Java impl.
* App spec interop spec 85% complete

## AuthZ

* Use cases/requirements for WAC vs ACP
** Collection of implementation intention
* Once these use cases are listed, draft a proposal for an AuthZ mechanism, informed by existing implementations.

## AuthN

* Discussion on how to transfer panel results into the main spec
* The core auth protocol is settling, with pending questions around app authentication.
** What credentials does an app have ?
* Questions around interoperability issues between ESS/CSS/NSS when it pertains to key algorithms
** Test suite and plugfests

# Solidproject.org

## Terms of use / persistence policy

https://github.com/solid/solidproject.org/pull/489

* How to enforce pledged persistence (who, and how from a technical perspective) ?
** We would need Tim to make a final discussion here

## [e-mail]

* Historically, it was its own mailbox. It is now an alias routing to the [Solid Administrators](https://github.com/orgs/solid/teams/administrators).
** What's the current use of this address ? -> it's given as a contact endpoint on solidproject.org. It previously was used as a registration adress on some services, it is also the replyto: of the newsletter. It should be kept this way, unless the automated responses become overwhelming.
** Clarifying the role of this email address is a matter of transparency, so that it can be spelled out in the term of use.

* How to respond to emails by organizations who want to use Solid ?
** We can direct them to the homepage, but we have to craft a response that shows how they can do research, without taking our own bandwidth

* Polite Redirect Email here: https://docs.google.com/document/d/1EeQncGUpYcuf9YOLcnoy-GB_fhxleAbaIcadvIbVTCE/edit?usp=sharing

# Open discussion

## hackmd vs W3C wiki

* More people are comfortable with Markdown than wikitext
* (Point to be raised again next meeting)