Meetings/2021-09-08 solid-team

From Solid Community Group

Solid Team Meeting 2021-09-08

Present

  • Alain B
  • Dmitri Z
  • Kay K
  • Kyra A
  • Marrelle B
  • Ruben V
  • Virginia B
  • Jackson M
  • Jeff Z
  • Sarven C

Agenda

Notes

inviting timea and alain to the team

Marrelle: Course of action would be to formally add Timea and Alain to the team, get a bio for both, and upload this on the website

Solid GitHub organization Proposal

Ruben: Tim not being here may be an issue to make a decision, but we can discuss it and make a recommandation. The GH org for solid has a lot of repositories, not all of them being kept up-to-date. > 140 repositories This repository has an official vibe to it, people not part of the Solid team have the ability to add repositories which look like they have the endorsement of the Solid team. For instance, we may want experimental repos not to be there. Proposal: have an editorial process in place for new repos, and archive old repos

Everyone: rough consensus

Dmitri: +1, confusion have been brought up multiple times in newcomers

Ruben: Tim is concerned that moving repos around would break links, and cool IRIs don't change.

Dmitri: GH handles 300 redirections for moved repos.

Nicolas: Do we even want an org for experimental code at all ? Making it discoverable in the community seems to be better than hosting everything in one central org

Ruben: +1, we would just need to create a temporary org for legacy repos being moved out of the Solid org in order to keep them available until their owners move them to a different space.

Solid team meeting organization

Marrelle: Would having this meeting biweekly instead of monthly ?

Dmitri: +1

Ruben: Not opposed to the idea, but under the condition that we have a way to track which people are involved in which issues

Nicolas: +1 to track who is involved in what to make sure decisions can be made

Jeff: +1 in particular if we can plan in advance which topics will be discussed on which meetings

Marrelle: We should identify some topics that we want to discuss on a regular basis

Jeff: Onboarding would be a regular topic

Marrelle: The topics can be discussed on Gitter during the week to come

Notification panel

Sarven: We used to create panels "on the go", but it created a proliferation of panels, so now the notification panel is created by writing a charter to clearly state its goal and scope.

Marrelle: Can anyone join ?

Sarven: Anyone who's a member of the W3C community group, for Contributor License Agreement reasons.

Solid World speakers

Marrelle: I want everyone on the team to be able to speak on behalf of the team. How do we do that ?

Sarven: People register in an ordered list, and if the next person isn't available, skip to the next

Kay: It would be best if the solid team update was thematic, and a person related to the theme speaks

Marrelle: Any volunteers ?

Sarven: /rocks, papers, scissors in the wind/

Security guidelines

Ruben: There are some usernames/passwords stored on a GH repo, and we'd want to mention to the repo owners that they shouldn't that. One way to do so would be to have explicit security guidelines that we can point to. This also relates to the GH repo organization point: if the solid org doesn't endorse repos, it's not as bad. Example policy

Data freedom foundation collaboration

Jeff: The Data Freedom Foundation, a full-fledged org, has expressed interest in Solid. How can we brainstorm with them to keep them engaged ? It seems like we are aligned with them on ethical questions/concerns.

Nicolas: How do we want to engage with any organization ? I.e. do we want to engage as "The solid team", or do we want to rdirect them to the website/material ?

Jeff: We should engage as a team

Matomo session recordings

Kyra: Matomo enables recording how people browse a website. We don't use it right now on solidproject.org. It's usually regarded as a privacy-focused alternative to google analytics.

Marrelle: What's the pricing model of Matomo ? Have we considered using Plausible

Sarven: We should make an announcement beforehand, as part of our community won't be thrilled about this.

Marrelle: The purpose being to improve the website and make sure that people get information from the website, so we should acknowledge people who disagree but go forward.

Kyra: We can investigate if there is an opt-out option. Ad blockers/anti-trackers typically disable these.

Archiving process

Sarven: What should we preserve on the long term, from sources such as chats, website, repos, forum... Archiving is not only useful to preserve content, it's also a way of keeping track of behaviours we want to refer to later even if they have been deleted.

Marrelle: +1

Jeff: Screenshoting things before they are deleted is a first easy way to archive content as a point of proof.

Marrelle: Where can we share these screenshots ?

Nicolas: Do we want archives to be public or private ?

Marrelle: Private seems better, it enables individuals to make amends, and avoids inappropriate

Nicolas: We could store these on a Pod

Jeff: We DO have a Solid team Pod already: https://solidproject.solidcommunity.net/

Sarven: back ups vs archiving.

Mike adams ban, and overall ban lift policy

Marrelle: ban ends in three days, how should we handle things ?

Sarven: zero tolerance: if code of conduct is not followed, permanent ban

Dmitri: +1

Marrelle: +1

Nicolas: +1

Action items

  • [ ] Marrelle to get bios from Timea and Alain
  • [ ] Ruben to ask Davi to create a baseline policy we can share
  • [ ] Kyra to look into Matomo and alternatives, collect pricing models, and see about opt-out.
Retrieved from "https://www.w3.org/community/solid/wiki/index.php?title=Meetings/2021-09-08_solid-team&oldid=484"