Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update with new sync call protocol #28

Merged
2 commits merged into from Apr 4, 2019
Merged

Update with new sync call protocol #28

2 commits merged into from Apr 4, 2019

Conversation

ghost
Copy link

@ghost ghost commented Apr 2, 2019

Just updated the call information, how to find call recordings, etc.

@ghost ghost requested a review from bigs April 2, 2019 02:06
@ghost ghost self-assigned this Apr 2, 2019
@ghost ghost added the in progress label Apr 2, 2019
@jacobheun
Copy link
Contributor

Some things I think we should add to make this a bit easier:

  1. Add a template for the notes to this repo. This allows anyone to easily create a Cryptpad for the next meeting.
  2. Add a section to this readme or the notes template (preferable) about expectation of roles. For example, having the notetaker/moderator be responsible for creating the PR of the notes after the call.
    a. Have the moderator create the items for the next meeting as a new comment in Recurring Sync Meeting #16. If we do this after each weeks meeting it should help us make sure we don't run into an issue where non attending members don't have a cryptpad to post in. Although if we have a template, anyone should be able to create the issue :)
  3. After the video has been uploaded I think it's also helpful to add the url to the original issue, Recurring Sync Meeting #16 (comment), for example. We do this in the js ipfs core meetings ⚡️ⒿⓈ Core Dev Team Weekly Sync 🙌🏽  ipfs/team-mgmt#650 (comment) and I think it makes it easy for people to use that as a central reference point for finding everything.

@ghost
Copy link
Author

ghost commented Apr 2, 2019

@jacobheun Thanks for the feedback. These all seem reasonable. @bigs and I are still sorting out who is responsible for what, so give us a little tine.

I'm going to copy/paste what you wrote into an issue in this repo so we can not lose it once this PR gets merged.

@ghost
Copy link
Author

ghost commented Apr 3, 2019

Ping @bigs

I'm going to self merge if you aren't able to review this week. These are simple changes, and I think it's important for people looking at the front page of the repo to see accurate information about when the call is happening as soon as possible.

@bigs
Copy link
Contributor

bigs commented Apr 3, 2019

sorry, lumped notifications for this in with the monday agenda! good by me.

@bigs
Copy link
Contributor

bigs commented Apr 3, 2019

@jacobheun i have such a template in cryptpad and can add it here!

@ghost ghost assigned bigs Apr 4, 2019
@bigs
Copy link
Contributor

bigs commented Apr 4, 2019

Added the template

@ghost ghost merged commit 078034a into master Apr 4, 2019
@ghost ghost removed the in progress label Apr 4, 2019
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants