solid-contrib
Document conformance criteria
Document the conformance criteria for applications to meet in order to be listed.
To date we've listed all apps that want to be listed.
At some point the list will grow large, and we'll have to think again. But it will primarily be driven on those that wish to help out.
If someone would like to step up we could explore further. Any offers?
PS also pointed this domain here for convenience :
http://solidapps.org
At the moment all apps get listed here, perhaps join the Happy Solid W3C Solid Community Group call to talk about what constitutes a beneficent Solid application.
The whole point of this issue is to... literally document. What does a call bring to the table over and above this issue? Sure we can talk.. but still at the end - as an actionable item - there is going to be documentation on the repo (eg. "before making a PR, check if your app fulfills the following criteria..").
I don't understand the rationale behind closing this issue - unless of course you feel that people with access controls on this repo will decide as per the vision or being on 'team' ... without documentation.
The conformance criteria for the most part coupled with the relevant specs in the ecosystem. There may be things not explicitly in the specs (cutting edge stuff) as long as it doesn't conflict with the core stuff. Interop is key.
Reminder https://github.com/solid/information/issues/7 .. before closing issues.
I'm not sure this belongs in the test-suite though, since this is not the verification of properties of apps, but the properties of Solid servers in relation to the Solid specifications.
