Meetings/2021-03-10 solid-team

From Solid Community Group

Solid Team Meeting

March 10th, 2021 on Jitsi

Present

  • Dmitri Z
  • Jackson M
  • Jeff Z
  • Marrelle B
  • Nicolas S
  • Olivia L
  • Oz O
  • Ruben V
  • Sarven C
  • Tim BL

Agenda

  • Announcements
  • Issues:
  • Pull Requests:
    • https://github.com/solid/solidproject.org/pull/489 -- SC discussed with Tim (verbally approved) but still would like him to tick Approve. SC can do a quick Q&A on this..
      • We list are going to persist, special pledge on some URIs. Reminder this will not be done with ALL aspects of the web. All approved move forward with the PR.
      • Action Item: For Tim to approve and Nicolas will hit merge
    • https://github.com/solid/process/pull/253 -- SC asked Davi to provide this security advisory reporting PR (to have a process for stuff along the line of https://github.com/solid/identity-token-verifier/security/advisories/GHSA-xmh9-rg6f-j3mr )
      • Open question: are the security advisories we publish only limited to projects under the Solid GH org ?
        • The scope of the advisory, the entity that initially reported the bug and the impacted could be sensitive information, that should be carefully curated, and attached to a suggested fix when broadcasted.
      • Open question: On what channels are security advisories shared ?
        • website, gitter, forum, mailing list...
        • This should be framed by a dedicated process.
        • who will review the raised advisories?
      • Action item: Look up how this is done on different/similar web servers we can build on top of
    • Are we okay to rename solid/process "master" branch to main? Any reason not to? ( part of https://github.com/solid/process/issue/249 ) - JB+1 – This was approved by all.
  • Topic Items
    • Test Suite (Save for next time)
      • Introduction / Update
    • Social / Community Outreach Update (Marrelle)
      • Solid Slide Deck
      • Diversity and Inclusivity Committee
      • Community Spotlight
        • Nomination timeframes
        • How often can someone be a spotlight?
        • Are we highlighting people and/or projects?
    • Solidproject.org Update
      • Progress update from site team
      • Security Page
      • Preserve the Solid Bluesky response
        • Action Item: Add bluesky to the site -- Sarven can do this but need agreement on URI
    • Administration
      • Solid Forum Migration to Discourse.org
        • Action Item: Justin to move forward.
    • Specification / Panel Update
    • SC: The Solid Process needs a major rewrite.
      • JB: Can we start with a list of issues?
        • SC: Text/links are outdated or not at all practiced. Access controls are a mess, repos are spiralled out of control.. Accountability is generally missing. We could create general todo items (like above) but breaking it down to individual items would be too much admin overhead. Needs a PR rewrite capturing the current state of things while staying in the spirit of what's currently in place. I can give it a shot but would like group agreement.
      • Action item: Sarven create a checklist together. Short list is need to deliver properly.

Minutes

Community Spotlight

JB: +1 for highlighting contributions (citing people involved) vs. highlighting people/orgs directly

Solidproject.org Update

JB: Worked with Kay, Ruben, Vincent, and Jeff to get some good edits to the main homepage copy merged - https://github.com/solid/solidproject.org/pull/525.

JB: Content creators have been meeting regularly on some target items for solidproject.org discussed in the last meeting (see notes here - https://docs.google.com/document/d/1ayzxOGB60jQJGy-JhpuOpaPo2uuuTk15fiIc49bdWEo/edit?usp=sharing). - In progress draft PR on breaking up the about page here - https://github.com/solid/solidproject.org/pull/529

JB: Security page - propose adding https://solidproject.org/security for tracking any notable security advisories in the solid ecosystem.

Solid Forum Migration to Discourse.org

JB: Have received OK from timbl to migrate forum from its current private hosting to discourse.org hosting. Plan to begin that process next week.