Skip to content

Replace panels with breakout task forces #324

Open
@elf-pavlik

Description

@elf-pavlik

Having participated in numerous Solid Panels since 2019 I think it is time for a retrospective and reorganization.

2019 - 2022

Panels were most active, incubating proposals and advancing them into dedicated repositories.
There was a special case of the Editors Team which I understood was an invite-only meeting.

2022 - 2023

Many panels stop their activity:

  • Authentication Panel - practically no activity
  • Authorization Panel - practically no activity
  • Data Interoperability Panel - some irregular activity
  • Notifications - very active in 2022, falling off in 2023

At the same time, there is a varying degree of work happening on the dedicated repositories and implementations!

2023 -

I think we should anticipate that Solid WG will be established and will be organized independently of CG while keeping coordinated. Based on CG charter and conversations around deliverables (protocol + dependencies) solid/solid-wg-charter#37 I would expect it to cover the following areas:

  • Solid Storage
  • Authorization and Authentication
  • Notifications (maybe)

There are still various areas, like discovery (which can depend on AuthZ) and other app interop-related concerns which the CG should continue its work on. I think the following might be one of the simpler and more effective approaches for the CG:

  • Single regular weekly meeting Solid-CG, which we should consider extending to 2 hours and always have open PR or Issue (at least gh Discussion) for each topic on the agenda.
  • If a certain area regularly starts taking up a significant part of that meeting, and we regularly need to push topics to next week, we should call a breakout Task Force which has additional meetings and to process the workload.
  • We don't create a repo for the Task Forces, only specifications have their repositories, and CG with TF work on those spec-focused repositories.
  • Instead of having incubating documents in the panel repo and creating new repo later on, the initial draft gets created in the personal repository of the person who is proposing it, they can always invite collaborators! As soon as the proposal gets accepted as CG draft it gets transferred to @solid github org.

I think we should do some retrospective first and after that discuss what I propose and what others will be interested in proposing. BTW Solid Panels document is pretty outdated, it links to a Zoom call and W3C wiki for minutes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions