-
Notifications
You must be signed in to change notification settings - Fork 4
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
App Clean-Up June 2022 #28
Comments
The following is the current standings for the App Update. I will leave this up for two weeks for comment, then make a pull request to update the document: Super Feature: Feature: Keep:
Self-Install Category Remove
|
The new apps were merged in with #727 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi All,
As discussed in the last Solid team meeting, I'm cleaning up the Solid App (https://solidproject.org/apps) page.
I've created notes for each app listed here (https://docs.google.com/spreadsheets/d/1p0opUBL0vRpEdNzDuB8mVy5XTrAbhSdMIzytqn-ef-M/edit?usp=sharing), and I've reached out to each of the developers to alert them of their app's status.
Apps were evaluated based on the criteria listed at the bottom of the apps page (https://solidproject.org/apps). The criteria for an app to be Solid-compatible are:
Based on this, I sorted the apps into 4 categories:
Super Feature
Super Featured apps will be listed at the top of the "Featured" category. Each of these apps is compatible with both the Old authentication standard, the new authentication standard, and the new-new (2022) authentication standard. Developers of super featured apps received the following in their email:
Feature
Featured apps were compatible with at least one authentication standard but not all, and they had a usable UI that would give a decent first-impression for people exploring Solid for the first time. Developers of featured apps received the following in their email:
Keep
Apps labeled keep were compatible with at least one authentication standard but not all. Developers of "keep" apps received the following in their email:
Remove
Apps marked as "Remove" either failed to meet the criteria listed on the apps site in some way or the criteria was un-testable. There were a few standard reasons for this, and I was sure to stress that the decision could be disputed before the page was updated.
Some apps didn't have an option to log in with other Solid servers and forced users into a specific server, thus violating rule 1. Developers received this message in their email:
Some apps encountered errors when testing that prevented me from testing rules 2-4. Developers received this message in their email:
Some apps were not Solid-Specific apps. They may have been linked-data related but lacked the ability to work with a Solid Pod. Alternatively, a few were simply landing pages for an organization and not apps. Developers received this message in their email:
Some apps were not able to authenticate with any Solid server. Developers received this message in their email:
Some apps linked to sites that did not load. Developers received this in their email:
Some apps did not have a deployed instance and required a user to clone a git repository and host the app locally. This prevented the app from being tested. Though, this criteria was appealed and instead of removing these apps, I'll now add them to a new section called "Self-Installed." Developers received this in their email:
The text was updated successfully, but these errors were encountered: