Closed Mitzi-Laszlo closed 4 years ago
aims within github.com/solid including: administration of solid properties, standardisation work, and creating and maintaining the website solidproject.org
I see github.com/solid as an open source project. (ducks...)
Just had a chat with Mitzi, we agreed that the code repos can stay under github.com/solid, but we'll look for a way to clearly label a list of "code" repos that are still maintained, and we can clean up the ones that nobody is working on anymore.
Yes! We can just give every repo a 'solid' tag and then use an additional tag 'code' for the ones that contain code.
A few questions for you @Mitzi-Laszlo to make sure I'm understanding the proposal correctly:
@justinwb
yes
yes
ok, let's add solid/vocab, solid/web-access-control-spec, solid/solid.mit.edu, solid/webid-oidc-spec to the research tag list.
yes
Following the implementation of the suggestions above here's an update of the repository overview of the Solid GitHub
Maybe wait to close issue until we have consensus and PR is merged?
On https://github.com/solid/process/issues/180 there was a conversation about a repo naming system and on https://github.com/solid/process/pull/172 there is a repository overview.
There are 117 repositories in github.com/solid and it is not easy for newcomers nor for people working on the repositories for some time to navigate between these repositories in a way that it is crystal clear what is the aim of each of the repositories.
The Process repository was started as an attempt to collectively agree on how to work on specific aims within github.com/solid including: administration of solid properties, standardisation work, and creating and maintaining the website solidproject.org. There are more activities going on in github.com/solid that the three just mentioned.
This is a proposal about how to gain clarity around the aims of the work happening in github.com/solid as well as clarity around who is responsible for what.
There are some repositories that used to fill the functions of the repositories already described here above but are no longer maintained by defined people. The key information needs to be combined with the repositories above and archived to avoid thinning of information and wiki rot.
Solid Research
In the remaining ~50% of the repositories of github.com/solid there are a range of experiments and research on Solid. The aim of governance of the experimental research is not described in the process repository and largely started during the Solid MIT research project and has been picked up by the University of Ghent in more recent years.
Some of the research works on implementing the Solid standard to ensure the proposals are feasible. There is not a defined intention to provide this software as a service to end-users with a defined service provider, although some users do so organically. In particular node solid server is used by many developers as a reference Pod when building Solid applications.
Here are a list of repositories that could be tagged as 'research':
There are various implementations of the Solid specification.
There are various Solid-related libraries mostly being led by Ruben Verborgh.
Folllowing is a list of other Solid research: