Solid Team Meeting 2021-08-11

Present

Kay K.
Ruben V.
Marrelle B.
Vincent T.
Jackson M.
Jeff Z.
Virginia B.
Kyra A.
Sarven C.
Nicolas A.S.

Agenda

Community Survey Deep Dive (Kyra & Virginia)
- Inclusive ways to engage
  - Videos on vimeo (recordings & explainer videos)
Info@ email management
Solid World Solid Team Update
- A different Solid Team members joins and gives updates about how the community and team are doing
Community Solid Server (Ruben)
Solid Team members
Panel/Team Updates (ex DEI, Spec Panels, etc.)

Notes

Ban from Solid social media

Marrelle: Misbehaviour of a community member that has been happening repeatidly. In order to create a welcoming community, these actions need to be condemned.

Vincent & Jackson: Due to the nature of the individual and his behaviour, the ban should be backed by solid evidence and references to specific rules that have been violated. Ideally the rule would also specify the length of the ban.

Marrelle: Permanent ban may not be the best options, in order to allow people back in the community and allow them to grow.

Ruben: Banning is also not only a message to the perpetrator, but to the rest of the community

Action items: - Marrelle & Vrginia: Provide to Ruben the specific code of conduct violations and message history - Ruben: Issue a polished statement of a 1-month ban on Gitter, the chans where violations happenend and the general channel - Ruben: Block him from the @solid org on GH - Virginia: Start an email thread with conversation history

Vincent: Which channels would they be banned from (Gitter, forum, mailinglist, GH, anything else)?

Vincent: We may want add an appeal procedure to the code of conduct.

Community survey

Ideas generated by the survey

Improvement to beginner onboarding
Buddy system
Community project
Sarven proposal: Intro video/summaries of each team/space/recurring meetings
- Video content: goal of the meeting, prerequesites
Jeff: Calling things meeting generates less engagement than calling them teams (e.g. editors, DEI, panels...)
Jackson: Where would the videos be available ? Marrelle: Vimeo first, and then linked from the website
Kyra: The issue we want to solve is clarity, so we may want to provide written descriptions even before videos.
Nicolas: Some of this information used to live on GH, but that's not the best place for newcomers who aren't familiar with GH
Kyra: The heart of the question is what it means to join the community: where are newcomers coming from, and where do we want them to go ?
Jeff: Ideally this information would live on a Pod and be displayed through whatever way we find best
Kay: The Solid team could give specific guidance on how to get involved for newcomers

Action item: - Nicolas: create a shared document to collect team descriptions

Management of the info@solidproject.org email

Marrelle: Some emails get lost in the inbox or we don't have a way of knowing if people follow through with the redirections we suggest
Sarven: How much email do we get typically ?
Marrelle: TODO @Marrelle I didn't type it when you said it
Sarven: Keeping a record of our replies is also important
Marrelle: I'll CC info@ with the reply

Solid world team update

Marrelle: Someone from the Solid team should make a team update on each Solid World

Community Server update

Ruben: 3 users for the community server (hobby users, Solid developers, Solid contributors).
- How Solid developers (developing Solid apps) use CSS:
  - "throwaway" server, that you can set up and teardown without any cost
  - Two-way access, to both server-side and client-side
  - Question: Do developers really need/want to get offline access ? Depending on this question, we can decide how to give guidance.
- Solid contributors (developping features for the spec):
  - enable easily implementing their proposals
Ruben: Sunsetting NSS or upgrading NSS security ?
- Convert the databrowser to latest security libraries so that it can switch to
Jackson: What's the plan for solidcommunity.net ?
Ruben: Switching is only possible when the ecosystem is mature with latest security practices
Jackson: The databrowser is on its way to be upgraded to the latest security
Jeff: Could there be a live instance of CSS before we transition solidcommunity.net

Action item: - Ruben to see if Inrupt can sponsor such an instance

Solid team members

Marrelle: We need the team to be larger, more diverse, and not as Inrupt-centered. Community members have already expressed concerns about how Inrupt is predominant.
Jeff: Maybe focus on helping people join specific teams (e.g creators, editors, ...), and de facto become member of the Solid team
Jackson: Elf Pavlik, Alain Bourgeois (already in there), maybe someone from Digita or Ontola
Nicolas: Voting may only make sense at the scale of the sub-team (for lack of a better word), i.e. DEI, Creators, editors...
Sarven: We may need to publicly advertize for existing roles, and the fact that they are open.
Kay: writing down what we work on will help people engage and see what they are signing up for

Action item: - Add process to https://github.com/solid/process to reach out to team members