Skip to content
This repository has been archived by the owner on Feb 8, 2023. It is now read-only.

Clarify & update responsibilities for weekly call #648

Merged
merged 5 commits into from
Jun 19, 2018

Conversation

mishmosh
Copy link
Contributor

This moves the changes proposed in #644 to the documentation. Additionally, it adds documentation for how someone would get all the permissions to host a call.

It does not attempt to solve #636.

@ghost ghost assigned mishmosh Jun 18, 2018
@ghost ghost added the status/in-progress In progress label Jun 18, 2018
@ghost ghost assigned Mr0grog Jun 18, 2018
License: MIT
Signed-off-by: Rob Brackett <rob@robbrackett.com>
@Mr0grog Mr0grog force-pushed the weekly-call-writeup branch from 59705e1 to d6ca871 Compare June 18, 2018 19:12
Copy link
Contributor

@Mr0grog Mr0grog left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made some grammar/formatting tweaks and asked two actual questions on content inline. Otherwise, awesome! 👏


1. Launch a Zoom call and share the URL with [@dignifiedquire](https://github.com/dignifiedquire) or [@kubuxu](https://github.com/Kubuxu).
1. Announce the call in IRC using `sprinthelper: announce`. To do this, manually copy over the name of the call, the number of the issue, the notes URL, the zoom call URL, and the Stream URL (which should be gotten from dig or Kuba). To automate this, close [this issue](https://github.com/ipfs/sprint-helper/issues/17).
1. Be on Zoom promptly at the start time. You don’t need to moderate, but you have all the rights so you must be there to grant them.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we decided the host is the moderator, so we should get rid of the second sentence here, right?

#### Before the Call

1. Make sure agenda is posted beforehand in GitHub using the current format (see #647 for an example). Ideally, this should be a day or more early so people can add items before the meeting. (Also consider proposed changes in #636.)
1. Post a notice just prior to and at the meeting time on IRC (#ipfs & #ipfs-dev), Twitter (@ipfsbot), & relevant channels.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should be specific here so the host knows what to do. 😄 Are there other relevant channels? (I don’t know them if there are.) We should list them or remove “& relevant channels.”

Linkify and reword
@ghost ghost assigned djdv Jun 19, 2018
@djdv
Copy link
Contributor

djdv commented Jun 19, 2018

I added some changes. The issue numbers didn't seem to automatically anchor, and I reworded a section.
The latter may not be necessary, so feel free to override those changes. Other than that, looks good to me!

@mishmosh mishmosh merged commit c960f3f into master Jun 19, 2018
@ghost ghost removed the status/in-progress In progress label Jun 19, 2018
@mishmosh mishmosh deleted the weekly-call-writeup branch June 19, 2018 13:58
@@ -37,4 +37,4 @@ The 1Password “IPFS Calls” vault contains credentials for:
- YouTube to upload recordings
- Twitter to announce meetings

If you are hosting and need access, ping @flyingzumwalt or @mishmosh.
If you are hosting and need access to the vault, ping @flyingzumwalt, @diasdavid, or @mishmosh.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not have admin on the vault. @dignifiedquire does.

Copy link
Contributor Author

@mishmosh mishmosh Jun 19, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@diasdavid you do now 😈

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😂

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants