Open jeremybeal11 opened 6 years ago
This is my first bounty, not even sure if i did this right.
DevEd will sponsor this. Congrats on your first bounty post @jeremybeal11!
Let's get started by choosing a time. Probably the existing colab time, right @David405 And post about it on the pub-RChain discord inviting anyone who wants to come and telling the time and zoom room. Maybe a teaser like "this week we'll talk about sending and receiving messages, and answer your questions".
Extra credit for whoever makes a pull request to https://github.com/JoshOrndorff/LearnRholangByExample/blob/master/README.md adding the second session info next to the existing info.
@Eknir (If that's wrong, can someone please tag Rinke here?) I'd also sponsor another session for intermediate-advanced lessons. Do you want to lead that up?
I think we should 1) get the intial count of who wants to participate. 2)evaluate their time zones so we can build a good schedule in respects to their time zones. 3) agree in what topics everyone feels comfortable teaching.
Good call Jeremy. In the spirit of self starting and having a hard time polling the audience, let's do this.
wow good approach Joshy, So let's do exactly that. i figured we can just start with the basics and work our way up.
Date: 2018-10-23
Attendees: 11
Topics covered: basic sends, receives, comm event, system powerbox
Video: https://youtu.be/zD7ptzx5DTw
Just thinking out loud, since this office hours actually started unofficially about a month ago, would it be okay to also paste in the report from earlier sessions?
@David405 You may paste in the ones from the month of October following the same format you did just now.
@Eknir Good work promoting this session. Getting people involved makes all the difference. If we regularly attract over 10 people to this section and my Thursday morning section, then I vote we spin off a third section.
So far only one office hour session has been reported here. Is that all that's to be paid? @David405 @Eknir @jeremybeal11
@JoshOrndorff I'm still on SOW so i don't think posting it applies to me.
@JoshOrndorff For the month of October, there were five rholang office hours/workstudy on Tuesdays.
Like @jeremybeal11 said, he is on SoW and so doesn't have to post his office hours here.
Report from the other office hour sessions below
Date: 2018-10-02
Attendees: 12
Topics covered: Pattern matching, Matching on a map, Show-me contract
Video: https://www.youtube.com/watch?v=SQcCui2vGhk ```
Date: 2018-10-09
Attendees: 6
Topic(s) covered: Simple Map contract debugging
video: https://youtu.be/qVML_3qImAs?t=4628```
Date: 2018:10:16
Attendees: 7
Topic(s) covered: Rhloang bundles, Relational store contract
video: https://youtu.be/rdLdzpk0YVg?t=502```
Date: 2018-10-30
Attendees: 5
Topics covered: Persistent sends, recieves
Video: https://www.youtube.com/watch?v=SQcCui2vGhk ```
The objective is to start engaging with the community whether they are members of RChain or devs passing by holding office hours that will allow others to collaborate and learn Rholang regardless of skill level. Each week, the office hours will follow by a general weekly schedule (ex: week one - go over sending and receiving messages, week two - go over smart contracts, etc) for the first half, and open questions, sharing code, and general discussion for the second half.
For each session someone from CoLab will post this template in the bounty issue directly in the corresponding bounty. The template must contain:
In order for the bounty to be paid, at least four people need to participate (as in talk, code etc, not just sit quietly) as verified in the video, and the developer education label to the issue.
Benefit to RChain
Budget and Objective
Please make the issue SMART: Specific, Measurable, Achievable, Realistic, Timely.
Estimated Budget of Task: $[100] per class, 1 class a week Estimated Timeline Required to Complete the Task: [weekly] How will we measure completion? [Date, Attendees, Topics Covered, Recording of the session]
See CONTRIBUTING.md for details on budget and reward process.
Legal
Task Submitter shall not submit Tasks that will involve RHOC being transacted in any manner that (i) jeopardizes RHOC’s status as a software access token or other relevant and applicable description of the RHOC as an “asset”—not a security— or (2) violates, in any manner, applicable U.S. Securities laws.