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

Process Changes #30

Open
mgoelzer opened this issue Apr 2, 2019 · 0 comments

Comments

@mgoelzer
Copy link
Contributor

commented Apr 2, 2019

Suggested by @jacobheun:

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 #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, #16 (comment), for example. We do this in the js ipfs core meetings 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.