search

go-study-group / agendas

Agendas for the Go Study Group Meetings
MIT License
29 stars 0 forks source link

Meeting Notes Publication Discussion #9

Open ankur-anand opened 5 years ago

ankur-anand commented 5 years ago

This issue is to invites views & suggestions regarding the way to publish meeting notes for go-study-group.

Since every single person has a vision of what would be an ideal way to publish notes for the larger community, we can use this thread to reach a consent.

Please comment with your suggestions and idea, and also please upvote if you agree with existing ideas and suggestions posted in comments.

Also, highlight your concerns in the comments below if any for any Idea and suggestions, that has already been posted in comments. We will use this to fine-tune these ideas and suggestions to find our ideal way to publish, the meeting Notes after each session.

carolynvs commented 5 years ago

I kind of like having comments, because we can have many notetakers, and later I can lookup a milestone, view the issues, and read the comments on the issues.

React to this comment with a 👍 👎 if you want to use comments on the issue or not.

michaeldebarros commented 5 years ago

My initial response would be to have some kind of notes.md considering it would be more clear for those like me that looks at the backlog of videos. Every one could take notes and submit a PR. The problem is that it brings a burden on the maintainer of the repo to review the PRs. In the other hand, if everything is kept on the issues, we have a more organic note taking, and more opportunity for discussion. My vote would be to start with working inside every issue. If it ends up being to "messy" then we figure out another approach.

embano1 commented 5 years ago

I like the ideas already shared here as they all have advantages. The question is: what is the reality? Are people really going to use comments in issues to take notes/discuss or will discussion happen mostly outside of Github, e.g. on Slack? What about the people watching an episode later (i.e. not live) and wanting to discuss? Should they also do it on Github or Slack? Do we reach everyone on Github or is Slack better?

The point I'm trying to make: is it really practical to do notes in Github issues (per episode) or would one central place (file), like in the Kubernetes SIGs, be the better approach (from a consumer's perspective - understand the tradeoffs for maintainers).

Now, regarding how to handle the number of PRs/ keep them small. How about:

1) adding contributors to this repo (Aaron + 2) which can approve PRs 2) designate a note taker in each episode so we have one PR per episode (notetaker would have to do some work to link to the issues, contributor with merge rights would have to also close issues, e.g. in the PR with a "close" comment)

ankur-anand commented 5 years ago

Extending @embano1 points, I do feel putting the notes on the issue itself can loose it's meaning too if the issue has to many comments whether for discussion or any other relevant information.