Meetings/2020-11-04 solid-team
< Meetings
THIS DOCUMENT IS A DRAFT
Solid team meeting
Attendants: - Jeff Z. - Marrelle B. - Pat M. - Sarven C. - Vincent T. - Jackson M. - Justin B. - Tim B.L. - Olivia L. - Nicolas S.
solidproject.org
- The website is ~2y.o. The initial annoucement drew a lot of attention on solid, and there's a chance that the same will happen again on GA announce. In particular, that's going to drive a lot of visitors to the solidproject-org website.
- Overall purpose: visitors of solidproject.org know
- what Solid is
- what the roadmap is
- Olivia used the feedback to update the copy
- Proposition: update the sitemap before GA mostly using what we already have, so mostly moving things around based on feedback. After that, we can iteratively improve the website.
App listing
- Tim: the app listing is lacking screenshots, and overall it should be data-driven
- Overall, there is no curation, no info about which apps work, etc
- Having a couple of apps which we feature might help providing a good first experience
- Sarven: feedback from dokieli: often, users don't know what are the prerequisite of Solid apps, which is getting a WebID and Pod. Getting those should be introduced as a prerequisite at the top of the page. Ideally, each app could list its own prerequisites.
- Marrelle: we should curate the app list, remove apps from the listing if they're not working, and in the meantime reach out to the app developpers to fix their apps.
- An option would be for Inrupt to host a featured app listing, that would be directed to by the solidproject.org website.
- Jackson: This listing should not replace the one on thesolidproject.org, to show that it's driven by the ecosystm, rather than controlled by a company.
- Justin: Solidproject.org could point to multiple app listings
Action item: where should the app listing be hosted ? In any case, inrupt would maintain it for the time being.
- Jackson: The release is of ESS, should we worry about many apps not being compatible with ESS ?
- Tim: The attention will be on Solid as an ecosystem, so as long as ESS is introduced as a Solid server, and points to NSS servers, that should be ok.
- Jackson: The release is of ESS, should we worry about many apps not being compatible with ESS ?
Immediate sitemap
- Main copy change addresses the core feedback that users feel after visiting the home page, they don't know what solid is
- About Solid dives deeper into details
- Olivia: FAQ
- Navigation is hard: all the questions should have a drop-down
- Some questions there should be answered by "About Solid"
- Tim: How to get the message across regarding interoperability issues
- Ecosystem upgrade for auth in the future
- What to do for the interim where both tokens co-exist ?
- Jackson: use a "label" to specify the version of the server to clarify compatibility
- e.g. "solid Legacy" vs "solid 1.0"
Action items: See if using solid-client-authn-browser is still possible for a thin wrapper around solid-auth-client
Status of the team
- Question: are we okay with sharing pictures of the team on the website ?
- Hyperlink to webids
- Sarven: we should be careful about how we introduce the team
- Justin: This team is merely the people with a named title in the solid org
Developer section
- Justin: should the tutorials be updated to use the latest libraries ?
- Make sure to include a section "add you own library"
- Tools page has the same issue as the apps page