-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace panels with breakout task forces #324
Comments
Let's focus on As I understand now it should include addressing what I described above. |
Reopening since #323 is practically done |
Context: awaiting confirmation of the idea to obsolete panels, a number of people (possible popping their heads up after summer slumber) were confused when no one turned up in some panel meetings that were still scheduled in the agenda. |
Right. So, this is aligned with the initial suggestion in solid/specification#458 (comment) to transition from panels to task forces. We needed to iron out a bunch of stuff along the way. Here we are. I've updated the status of data-interoperability-panel, test-suite-panel, notifications-panel, webid-profile in the CG calendar to "tentative" for the time being. BTW, webid-profile isn't and wasn't intended to be a panel. It is intended as the first task force (before literally calling it as such). |
PRs references in #324 (comment) are now resolved. @elf-pavlik , everyone: I suggest closing this issue. Solid Process needs to be updated any way. Discussion pertaining to CG task force can carry out in solid/specification. |
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:
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:
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:
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.
The text was updated successfully, but these errors were encountered: