Skip to content
This repository has been archived by the owner on Jun 17, 2020. It is now read-only.

M> Hangout Summaries - Github page #79

Closed
patrick727 opened this issue Aug 9, 2017 · 18 comments
Closed

M> Hangout Summaries - Github page #79

patrick727 opened this issue Aug 9, 2017 · 18 comments
Assignees
Labels
Mattermost Migration zz-Marketing guides: @pmoorman @AyAyRon-P @kitblake

Comments

@patrick727
Copy link
Contributor

patrick727 commented Aug 9, 2017

M> Indicates that this is a project within the "Marketing" category

Goal:

It will be helpful if there is a github page, like the FAQ(even better in markdown) with summaries of the latest hangouts that include links to the timestamps.

Here is a google doc that I used to write notes, we can start with august moving forward if someone is willing to pick this up.

@patrick727 patrick727 created this issue from a note in Marketing (todo) Aug 9, 2017
@entropee
Copy link
Contributor

entropee commented Sep 6, 2017

Anyone interested in working on this I think this should be rolled into a video production project. I have started a channel called #Video Channel Coop in the Diglife DivvyDao Mattermost domain, here: https://chat.divvydao.net/divvydao/channels/video-production-coop. I can provide invites if you need them.

@entropee
Copy link
Contributor

entropee commented Sep 6, 2017

Can this issue serve as the video production one, or should I start a new one?

@patrick727
Copy link
Contributor Author

@entropee i'd start a new one. I was looking for timestamped summaries of the hangouts for peoples reference currently I have had to do all of them manually for the newsletters.

@dckc
Copy link
Contributor

dckc commented Sep 16, 2017

I'm interested to pick this up -- at least to migrate the existing summaries to markdown. Those summaries in the newsletters are a gold-mine.

@dckc
Copy link
Contributor

dckc commented Sep 16, 2017

I converted a big chunk of the links from the newsletter archive to markdown: https://github.com/rchain/Members/wiki/Weekly-Update-Index

@dckc dckc self-assigned this Sep 16, 2017
@dckc
Copy link
Contributor

dckc commented Sep 16, 2017

These things have lots of names: hangouts, community updates... I think I've seem them called zooms? I went with Weekly Update. does that work?

@dckc dckc moved this from todo to in progress in Marketing Sep 16, 2017
@lapin7
Copy link
Contributor

lapin7 commented Sep 17, 2017

@dckc
Does this budget have to be increased?
Are the rewards distributed?
Please use form Budget allocation and - spending

Issue # Link Status Project / Issue Category Votes Last month Left over New Budget $ Sep Budget ⍴ Sep Budget Voters
79 #79 In progress Hangout Summaries - Github page Marketing 3 $ 400.00 $ - $ 400.00 $ 400.00 ⍴ 4,000.00 @kitblake @lapin7 @patrick727
Github Issues URL Description Category Set State ⍴ Budget ⍴ To Pay Activist AVG work Votes Voters
79 #79 Hangout Summaries - Github page Marketing 3 In progress ⍴ 4,000 ⍴ - patrick727 0% 0  
79 #79 Hangout Summaries - Github page Marketing 3 In progress ⍴ 4,000 ⍴ - dckc 0% 0  
79 #79 Hangout Summaries - Github page Marketing 3 In progress ⍴ 4,000 ⍴ - entropee 0% 0  

@patrick727
Copy link
Contributor Author

@dckc again great work on this!

The video description is "RChain Debrief" so we will use that moving forward, zoom is the software to hold the video conferences.

Id like to see this page a bit more detailed then the newsletter verzions moving forward, perhaps @plantether can help with this.

see https://docs.google.com/document/d/1Va_u-I_IWCvpWVgQXNKsFuhpaH-enouhPotJMTGoiRM/edit?usp=sharing

@plantether
Copy link

plantether commented Sep 17, 2017

@patrick727 @entropee @dckc @kitblake What do you think the more detailed format should be? More and more detailed summary lines, more summary lines but shorter, existing summary lines but annotated?

For example, for Sept. 6:
The newsletter summary line is:
- Technical Discussions: Q&A on Namespaces from Discord

Do you prefer:
(A) Breaking it down into more and more detailed links like the following:

Technical Discussions: Q&A on namespaces and channels

OR

(B) More links, but with descriptions that are not as detailed:

Technical Discussions: Q&A on namespaces and channels

OR

(C) The same links used in the newsletter, but with linked (or unlinked) annotations that are longer or shorter, more or fewer?

OR

(D) Something else

I would prefer something like A, but I think more people would prefer something more like B

@dckc
Copy link
Contributor

dckc commented Sep 17, 2017

I very much like the idea of elaborated summaries of the videos, but I wouldn't add them to the same index. The current list of 5 to 7 links per week was just what I, as a new person, needed: it was the difference between

  • yikes! 40 weeks of updates! I'll never find time to watch them all. And how will I keep track of which is which?
    to
  • ah. OK... now I can pick and choose which ones to watch, whether for the first time or coming back again.

This index is most useful if it's all on one page and not one that makes my scrollbar tiny.

The next level of elaboration that's useful is capturing the main points in a way that pretty much substitutes for watching the video. Just like this bit of the doc you cited:

Private sale: Going well, over 4.4M has been closed out and several more coming in, including several large funds coming in.

It's very valuable to attribute such points to who made them. Points like "People really interested to know we can talk about that off line." are pretty much useless without knowing who said it.

Paraphrasing in text carries a real risk of not quite getting it right; i.e. putting words in somebody's mouth that they didn't say. If the text description isn't visible to the participants in near-real time, then it may be important to review them after the fact, which is somewhat labor intensive.

@dckc
Copy link
Contributor

dckc commented Sep 17, 2017

Thanks @patrick727 ; I made an edit to use "RChain Community Debrief" (more) consistently and add serial numbers and renamed it to https://github.com/rchain/Members/wiki/Weekly-Debrief-Index

@patrick727
Copy link
Contributor Author

@plantether I agree with @dckc 's points, so if i had to choose something like B would be my choice but considering the lenghtyiness.

@edeykholt made the same comment in our meeting yesterday In regards to this issue as well as the Wiki issue which go hand in hand. "Less like a complete transcript, and more like a clean primer"

@lapin7
Copy link
Contributor

lapin7 commented Sep 19, 2017

Great @dckc has assigned himself a reward for this issue and a budget was already allocated. It would be nice if @dckc also set's a percentage for the work that @patrick727 , @entropee and @plantether have done.
In the form Budget allocation and - spending he could fill out for example:
@patrick727#10
@dckc#30
@entropee#20
@plantether#25
This sums up to 85% of the work completed. So next month still 15% of the work could be done.

He also needs 2 more collaborators to vote as well on the rewards.

And @dckc could still assign a budget to this issue, according to his opinion. This however not needed, because there are already 3 persons who have set a budget already.

Budget allocation

URL Status Project / Issue Category Votes Last month Left over New Budget Voters  
#79 In progress Hangout Summaries - Github page Marketing 3 $ - $ - $ 400.00 @kitblake @lapin7 @patrick727  

Budget spending

URL Description Category Set Set ⍴ To Pay Activist AVG work Votes Voters
#79 Hangout Summaries - Github page Marketing 3 In progress ⍴ - @patrick727 0% 0  
#79 Hangout Summaries - Github page Marketing 3 In progress ⍴ 1,200 @dckc 30% 1 @dckc 0.3
#79 Hangout Summaries - Github page Marketing 3 In progress ⍴ - @entropee 0% 0  
#79 Hangout Summaries - Github page Marketing 3 In progress ⍴ - @plantether 0% 0  

@patrick727
Copy link
Contributor Author

went ahead and updated @dckc 's debrief resource page
https://github.com/rchain/Members/wiki/Weekly-Debrief-Index

@dckc
Copy link
Contributor

dckc commented Oct 6, 2017

Thanks, @patrick727 !!

@patrick727
Copy link
Contributor Author

the index is up to date again guys! added the past two hangouts

@patrick727
Copy link
Contributor Author

@drbloom will you please add this summary index to the /reference page. I believe it belongs there and the FAQ. I did a pull request for the FAQ but couldn't figure it out for the /reference page.

https://github.com/rchain/Members/wiki/Weekly-Debrief-Index

@ian-bloom
Copy link
Contributor

@patrick727 - I don't think it belongs there because the rchain/reference README currently makes no mention of Co-op membership, newsletters, hangouts, projects, etc.

Co-op

What do you think about adding the item Membership to the above, linking to the README for rchain/Members? A link to the summary index Weekly-Debrief-Index is already included there.

rchain/reference > Membership > Weekly-Debrief-Index

@patrick727 patrick727 removed this from in progress in Marketing Dec 8, 2017
@patrick727 patrick727 changed the title Hangout Summaries - Github page M> Hangout Summaries - Github page Dec 11, 2017
@patrick727 patrick727 added this to in progress in M> Content Creation Dec 11, 2017
@patrick727 patrick727 moved this from in progress to complete in M> Content Creation Dec 11, 2017
@patrick727 patrick727 added the zz-Marketing guides: @pmoorman @AyAyRon-P @kitblake label Jan 5, 2018
@lapin7 lapin7 closed this as completed Jan 12, 2018
@TrenchFloat TrenchFloat reopened this Jan 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Mattermost Migration zz-Marketing guides: @pmoorman @AyAyRon-P @kitblake
Projects
No open projects
Development

No branches or pull requests

7 participants