-
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
Consider panel dependencies and perhaps adjust timing #135
Comments
Case in point: solid/authorization-panel#33 |
I agree that we need overarching focus and coordination, and I think that we can work within the structures that we’ve got now to guide and encourage that work - and achieve the milestones that are most important to Solid (chiefly the v1.0 specification). I believe that part of the responsibility of the editorial team is to be proactive in providing this guidance and coordination, so I'm going to propose a project under the scope of https://github.com/solid/specification, primarily assigned to editors, to undertake this. |
In practice the authentication, interoperability, and authorisation panel are the only active panels. Let's create a one stop shop page on the W3C Wiki with an overview of panel calls to make it easy for everyone to keep track. |
Also, perhaps it's an idea to close inactive panels for now. |
When panels were first introduced there was a wild proliferation of panels. This resulted in some trouble keeping track of what was going on as mentioned in #135 In the process it states that "Panel repositories that are inactive for more than six months may be archived by Solid Administrators." With this pull request, the inactive panels have been removed. This does NOT mean that the topics are unimportant or that they should not be picked up at a later stage. It
No description provided.
The text was updated successfully, but these errors were encountered: