Weekly mob can work if Llewellyn is absent

[MichaelRWolf]

Problem

Currently, @isidore is a single-point-of-failure by his absence for ALL of these development steps.

• Teleconference :: Zoom
• CDE :: Amazon Streams (formerly TeamViewer)
• Repository :: github
  One weekend at a time, work is orphaned in a place that is not the repo, leading to the early-July through late-October non-push.

Proposals

A mix of ChatGPT answers and @MichaelRWolf ideas...

Zoom

Sign in to your Zoom account at zoom.us and go to the Settings page.

Navigate to the "In Meeting (Advanced)" section under the settings.

Enable "Allow participants to join before host":

Look for the option labeled "Allow participants to join before host" and enable it.
This option lets participants join the meeting without the host needing to be present.
Optional - Select the Join Time Limit:

You can also specify a time limit (e.g., 5, 10, or 15 minutes) to control how long before the scheduled time participants can join. This option appears right after enabling the setting.

CDE - AmazonStrems

No known solution to AmazonStream.

On 2024-11-03, we adopted single-typer on someone's personal MacBook. Another option would have been to use gitpod. This only worked because we were starting fresh work. Had we been building on previous work, we'd be blocked by stranded changes.

Repository

Rely on the wisdom of the group (as humans and as distilled in GH Actions) to prevent BadThings(r) from happening.

To allow a specific group of users to push to a GitHub repository, you'll adjust access settings to grant them the necessary permissions. This involves inviting users or teams to the repository, then assigning the appropriate role (e.g., Write or Maintain) to enable push access. If the repository is part of an organization, you can also create a team for easier management.

Steps:

1. Access Repository Settings: Go to Settings on your GitHub repository.

2. Manage Access: Click on Manage access and invite users or teams.

3. Assign Permissions: Set the Write role to allow push access or Maintain for broader control.

4. Confirm: Save changes to grant the permissions.