Regular event attendees, "Who We Are", and organization membership

[julianpistorius]

Context

• There is a feature on the website that shows people who go to the website who they might run into at different events.
• This feature works by getting members from the GitHub teams which organize the community events.
• "Teams can only be made up of members of your organization, outside collaborators are unable to be on a team" (see About teams - GitHub Docs, and it requires an organization owner to add a member to the organization.
• See adding people to teams requires them to be members of ResBazAZ #32 for history

Questions

1. Do we want 'regular event attendees' to also automatically become members of the organization?
2. What does it mean to be part of the ResBazAZ organization?
   • What are the privileges & responsibilities of membership? (Example: Voting)
   • Note: This also relates to the in-progress "Who We Are" page issue and pull request.
   • See GOVERNANCE.md
3. Is the 'regular event attendee' feature something that we want, and if so, how much?

[julianpistorius]

Some of my thoughts:

1. The 'attendee' and 'member' roles are not necessarily the same, and someone should be able to explicitly opt-in to (and opt-out from) from these roles separately.
2. The value of the 'regular attendee' feature seems like something that organizers of individual events should decide on, based on the feedback of the attendees of their events.
3. The 'regular attendee' feature should still work if organizers of different events have different preferences.

[alex-r-bigelow]

Per discussion at Coffee & Code this morning:

1. Should be trivial to tweak the randomAvatars thing to only show a limited sample in the "who you're likely to see" sections instead of the full list; I'll push a fix with that soon
2. To include people without adding them to the GitHub organization, we could add a custom file a. somewhere, in b. some format, but I'm a little unsure whether GitHub will allow us to scrape profile info about unaffiliated users? I can experiment in a bit...

a. Probably ideal to keep the file in the website repo, adjacent to the auto-generated people.json? If it is possible to pull arbitrary github profiles, we'll probably need it in the repository anyway

b. To make it edit-friendly, JSON, YAML, or CSV seems sensible?

• I think github has a CSV editor*, but I worry about things like nested commas / delimiters for the one-to-many, github-to-profile-to-team mapping. Although JSON / YAML are a bit more esoteric, they seem like they'd be more error-resistant?
• YAML would be fine (especially as people would need to edit front matter with Quarto already), but I worry about parsing YAML as part of a github workflow?
• JSON would be easiest from my (kinda biased) perspective, but might be the least usable? There are some JSON auto-formatting tools* that can make editing JSON a little less painful

There was a concern raised a while ago about people wanting to display different information on our site than their Github profile; a custom file would have the benefit of making it possible to override bio, company, avatar url, etc

* ^{These challenges might not be so bad with resbazaz/website#84 ... sorry my review is a bit delayed there; having some fun trying to get docker running on an ancient laptop in the wake of being very recently funemployed...}