-
Notifications
You must be signed in to change notification settings - Fork 59
CoLab RNode office hours #988
Comments
I've spoken with @jeremybeal11 about a similar idea. This could become an officially sponsored task, but we are blocked by:
|
just saw this, and im also curious about what the budget is for. just a side note, can we refrain from using "Noob" and substitute it with "beginning learners" or something like that lol |
I argued against "noob" long ago too. @jimscarver agreed to some extent, but he keeps using the term. |
Regarding [weekly], indefinite durations are awkward, so it's important to give plenty of justification. See, for example, the "How will we measure completion?" section of #208. |
Regarding rewards for meetings, advice I have received that seems wise is: reward for the results of the meetings, not just for holding meetings. So perhaps the goals here is something like: present the rholang tutorial to 15+ developers in the next month or two or three. Or: develop rholang proficiency in 15+ developers (as demonstrated by the ability to answer the quiz questions in the tutorial). And for rnode office hours: assist 10+ members in bringing up nodes, or resolve 20+ support issues raised by rnode operators, or some such. |
Yeah, actually, these sessions might be a great chance for a working group to go through the tutorial and solve the exercises and point out where I've made mistakes writing them. Thoughts about merging this in with #919 ? |
Maybe use #919 for rholang stuff and re-scope this one to rnode stuff? |
Here's my proposal. @jimscarver Does this sound reasonable? It is valuable to offer peer learning sessions at various times and at various skill levels. I want to close this issue and open two new issues. One for colab rholang sessions (offered once per week) and one for colab rnode sessions (offered once per week). The offered budget would be $100 per session. Can't justify more than that because that's more than my own rholang office hour costs the coop. For each session someone from colab would need to post this template in the bounty issue (not a google doc or an email or a different bounty or a post-it-note) but directly in the corresponding bounty. Date: In order for the bounty to be paid, at least four people need participate (as in talk, code etc, not just sit quietly) as verified in the video. I'll leave it to someone else to create the individual issues and add the developer education label. If that happens I will fund it. |
@JoshOrndorff what about I change the name of this issue to just rholang office hours and then create a new issue for rnode office hours instead of opening two new issues? |
Actually, @David405, Let's do it the other way around. You start a new issue for rholang office hours according to the details I DMed you on discord. |
Let's team up with @ddayan to have this cover his Tuesday morning sessions as well. |
I wouldn't say there was much "organized" work done here in October. |
The Cooperation Laboratory starting in September hosts classes and workstudy for rholang on tuesdays and then node setup and testing on thursdays. The venue for the office hours is https://zoom.us/j/6853551826, time is 4pm NY time, 8pm GMT
Benefit to RChain
Create an environment for noobs and developers seeking to learn the rholang programming language.
Provide workstudy for rholang codes, contracts to be evaluated, debugged.
Guide people through setting up rnode
Create our own private RChain network
_Estimated Budget of Task: $2000
Estimated Timeline Required to Complete the Task: [weekly]
How will we measure completion? [log note]
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.
The text was updated successfully, but these errors were encountered: