CoLab cooperation laboratory peer learning work study achievements

[jimscarver]

Running peer learning sessions and recruiting coaches and students. Consider adopting and adapting tools such as "Meet for good" to enable scheduling of peer learning, work groups and open meetings in the coop. Organize a peer learning program.

Current activities include: rnode runners, rhobots, system administration, rchain tools, translation, marketing and video production. achievement are rewarded on separate issues where they apply. Report here activities not covered elsewhere.

The work study group four three days a week, mondays, tuesdays, thursdays and saturday. See this RChain Community Calendar for details.

Current peer learning activity log is in this document and the RChain CoLab and the CoLab discord server. Join us and earn rhoc while you learn solving rchain issues together. Become a leader.

---

Estimated Timeline Required to Complete the Task: As Education is a core value of cooperatives and the community around this issue has some momentum, we request an unusually long and unusually indeterminate duration.
Estimated Budget of Task: approximately $2000/month
How will we measure completion? Rather than measure completion, we aim to measure continued benefit worth keeping this process going. Approximately two to three meetings per week with reasonable notes and recordings are a sign of valuable education and collaboration. Progress on at least one or two software development projects is another. New participants in rnode testing is also valuable.

[ResonanceXX]

Always ready to learn from the very best on here!

[Viraculous]

Wow! nice idea in line with the principles of cooperative no.5 (ICA 1995). " Education, Training and Information", it is step towards self-sufficiency and advancement. There is need for peer learning, work group and open meetings especially for new cooperators to facilitate easy assimilation of the RChain cooperative environment. The peer learning could include a complex lot of things but should of necessity revolve around the actualization the RChain vision and solving the problems limiting it. The peer learning is a good tool both for new and old members to be educated on the internal and external environment of the platform to foster cooperative autonomy and community's competence in the dynamic world of blockchain systems. Further more i feel the work group should be partitioned to handle issues based on member specialization, interest or technical know-how while leaving room for contributions from concerned cooperators. This link could help https://github.com/rchain/Members/wiki/Learning-RChain

[BelovedAquila]

Yes, goes a long way in cooperative brain storming and information/knowledge free flow. Would also be glad to be part of this, no man is an island of knowledge, not in Rchain and not in the world. Great!.
@lapin7 and @kitblake, this idea @jimscarver made here,is a good rephrase to what I considered in raising my last issue,
#211
It's a great idea towards marketing and education on Rchain and about Rchain community.

[ResonanceXX]

@jimscarver Hello, please when does the actual peer learning take place. Could this be passive, or could a more formal meet be organised. If so you should consider the platforms where this can occur.. Thank you. Cheers.

[jimscarver]

My apologies for not seeing the activity on this thread sooner. Thus far, the work studies have been held in my zoom room https://zoom.us/j/6853551826. We try, and sometimes succeed in recording activity in the log <https://docs.google.com/document/d/1OVUGmxv4q1ywcxDG-V926lrXpkQNDs7n2eO2R5OJdOk/edit#>. rchain noob group regular meeting is Thusdays 2pm EST where we can decide what we want to learn and do together and schedule peer learning groups other times as needed for specific. When possible we get some work done on an issue participants feel energy to investigate after reviewing peoples interests. Learning to run rholang and rosette has been one activity, We build a bot to run rosette code (not running at present). What else of value might be delivered in this area? Learning to participate in node testing may have interest for some. Single signon for our tools and bots along with strong self sovereign pseudo anonymous interoperable identity enabling our social ledger and democratic process in our communities is a cooperation with diglife.com, holochain.org and others. Tuesday's 1 pm EST is cooperation with holochain identity and rholang programming on holochain. Monday and tuesday 2-4pm EST is open topic learning. 4pm is cooperation with DigLife on the social ledger trial. Saturdays at 11am EST is a cross community identity cooperation meeting. I'll try to get all this in the rchain calendar <https://calendar.google.com/calendar/ical/2cj152c9nidh6glpr1d5g4eq28%40group.calendar.google.com/public/basic.ics> soon. Everyone is free to schedule social learning on any topic at any time. Getting Oauth working from a PHP client using mattermost and discord as providers is a prerequisite for many other activities where we need to identify the user is a priority. Using OAuth is a basic skill we all need to be enabled in the bot/agent/api ecosystem. Our aim is to make it simple. We are self organizing here and without a leader we must all lead. Initiate what you want to learn and do. Let's accomplish together what we could not do alone. Social learning is a means to scale is we each learn something from each other (monkey see, monkey do) and pass it on to others. We are entering virgin territory where there are no experts yet and we need to become them. While this is framed as sociocratic social learning work studies are autonomous and can use whatever norms they choose. We like to have social learning group deliverables entered as github issues to do something useful and get paid in rhoc. Education is useful but we want work product that builds our group memory and guides those who follow us. A github issue should be created for each peer learning activity is one does not already exist. To get paid someone should be responsible for commenting on the issue to report activity and participate in the budget setting and allocations sheets. Hope to see you at the noob meeting today.

…

On Thu, Jan 11, 2018 at 1:56 AM, Chris Ken ***@***.***> wrote: @jimscarver <https://github.com/jimscarver> Hello, please when does the actual peer learning take place. Could this passive, or could a more formal meet be organised. If so you should consider the platforms where this can occur.. Thank you. Cheers. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#208 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AC5YETESFOzXuqWO7QJTTSZCvSQjN4gtks5tJbCQgaJpZM4RLwE1> .

[ResonanceXX]

Jim very detailed explanation. "We are self organizing here and without a leader we must all lead" I couldn't agree more. Great stuff.  Thanks for this. Cheers.

[Viraculous]

Interesting @jimscarver. What's going to be the nature of the work group? Based on specialization, interest or technical know-how?

[jimscarver]

It pains me top see this issue closed. and reopen it in the hopes others help lead the effort. Education is one of the goals of the cooperative. We want to create an environment where the work, is the play, is the learning, becoming self-reliant in employing the emerging technologies in service to the coop.

The 12 scheduled work studies and a number of ad hoc work studies had only a handful of participants and mostly due to limited coaching produced little. The notes and not complete. The project doc need a lot of work. Someone besides me need to take some leadership responsibility. I've invested a lot of time in this but not very effectively.

A big problem is getting good coaches. More people show up if a good coach is planned. I have not done well at attracting coaches.

[TrenchFloat]

@jimscarver Apologies for closing the issue without getting in touch with you. Do you have any suggestions on a new leader for the issue?

[Viraculous]

Thanks a lot, @jimscarver for reviving the fire on this issue. Right from my onboarding to the platform, I have been so much concerned about the need for member education in building the RChain platform. I strongly believe that to build a sustainable, a self-sufficient system, adequate education must be valued. @jimscarver am highly impressed by the Idea that was put down at the project doc and I'm interested. I will look into it more closely.

[aviationhacker]

Hey guys, the issue has just been updated from Scheduling more towards the running of and recruiting for peer learning sessions (also occasionally referred to as the noob working group - as most of us are newbies who are learning as we go). I just thought I'd chime in with an update from that front - I've been part of these sessions for a few months now, and if you're new to developing they're highly educational and @jimscarver who runs them has a wealth of knowledge, so the projects are varied and interesting.

However, an issue we commonly run into is needing assistance from others who have experience working with different languages and implementations using certain languages. While Jim has a wealth of knowledge, he doesn't know it all. So any help that can be given would be highly appreciated!

Currently, we are looking for a coach for some GraphQL work, and possibly someone who has experience with connecting GraphQL to MySQL.

[jimscarver]

I am not very familiar with the newer tool including things like node.js, nginx, express, react, etc. I knowledge in other areas is dated. So coaching in almost every area is needed. I have been hesitant to get more students without having more coaching. While we get a good feeling of accomplishment when we make things work, progress can be slow and tedious. Much of what needs to be done is configuration and integration requiring very little actual programming we just need help getting over some of the hurdles.

[dckc]

@JoshOrndorff how many people do you think learned to do rnode testing in these meetings in July? Just a rough guess would be handy.

[JoshOrndorff]

I can think of at least size people who I can confidently say increased their understanding of running and test RNode. Three or four others occasionally attended. @dckc

[jimscarver]

I think about six node runners either succeeded in connecting their node or at least got to the point where they could officially meaningfully participate in the tuesday node testers session. Joshy also introduced some rholang adding value to the sessions getting people started there.

[aviationhacker]

Just an update with what's been happening in the Colab work study this month, we've been spending our time on a few different issues/projects which are detailed below:
-A little more time was spent on learning rnode (approx. 10 hours) with issues reported in Jira, and notes made in the workstudy log.
-Significant time was spent on implementing kycbot/rho-bot, which can be found on discord. The bot basically processes things in rholang and gives an output to the user on discord. We are now working on getting it working on more channels.
-Some time was spent on organising the various "labs" as we call them, assigning channel leaders and forming teams for the different projects to ensure everything runs as it should.

• Finally one of the teams spent more time indexing videos that were made last month, from issue RChain Membership Signup Explainer Video #854.

For more information on specific votes for each person, see this document: https://docs.google.com/spreadsheets/d/1tFcOjePnmyZw6a0FJGQFOP9Fx1m2yXNyjB4DWYSE34g/edit#gid=525253239

Each individual should have commented on what work they have completed this month for each issue, giving some idea of their work product.

[dckc]

Good stuff.

Please consider escalating rho-bot to its own issue for better visibility.

[azazime]

Nice to have been part of the colab, we did a lot of work in the previous month especially with the team formation and channel leaders which will go a long way towards Colab organization

[Valentine-Mario]

For the month of August, I was involved in running rnode and creating a rhobot account for valentine to ssh and create bootstrap nodes, kycbot error fix and setup, ad hoc work study, channel lead organisation and team formation.

[dckc]

developer-education bounty sponsorship

In office hours (#403) this morning, @jimscarver asked about sponsorship for this sort of colab stuff; @David405 wanted to know more too. With @JoshOrndorff , we booted a developer-education label (#692 (comment) ).

Practicing the RChain Genesis ceremony: our own test net

Raw notes are in #node-runners and in a recording of the Zoom session (to appear).

Anybody who is interested to condense this for a larger audience is welcome to open a bounty issue.

I think even a short 3-paragraph "look what we did" article with a pointer to the recording is valuable.

Some slides to use when explaining it (e.g. at a meetup or in another Zoom) would be another level of effort

As to rewarding just what we've done so far, without condensing for a larger audience, I didn't hear Joshy endorse that. But he did give a hearty thanks, so I suppose it's negotiable.

[dckc]

@David405 , @jimscarver for the Tuesday rholang sessions and the Thursday rnode sessions, I recommend new issues of their own. The general colab peer learning principles and such would make good wiki topics.

[JoshOrndorff]

The work we did this morning is directly related to https://rchain.atlassian.net/browse/RHOL-883

A short 3-paragraph article would certainly meet the requirements of the atlassian issue, and thus I would support that. As Dan mentions, slides and a video condensed to between 3 and 10 minutes would also be nice.

I am very grateful for the time you all contributed this morning, but it alone really only benefits us,a nd it would be a tricky grey area to support financially. It would be best and send good signals about the bounty system to have a deliverable before expecting a bounty imho. But I am open to suggestions on that.

[owans]

I wrote a CoLab article,
See https://www.rchain.coop/blog//introduction-to-rchain-colab/

I see a $200 suggested reward in Dynamic Voting Guide, CoLab 2018-09 -- @dckc

[jimscarver]

In September the colab took steps on becoming a testbed for enabling cooperation at scale and becoming aligned with the priorities of the cooperative. We are enabling cooperative work and self-organization. A current state document was developed, Activity of members under this issue, and related issues is summarized in these sheets. The issues worked on may be reviewed in the bounty dashboard we devloped and maintain https://rchain-bounty.rhobot.net/?month=September&label=colab

[dckc]

If there's a summary, go ahead and excerpt it here in this issue. Supplementary documentation elsewhere is fine, but noone should have to look at them to get essential materials.

The measurement of completion for this issue are:

• Approximately two to three meetings per week with reasonable notes and recordings
  • I'd like to see dates and names/titles of the meetings
• Progress on at least one or two software development projects
  • I'd like to see a pointer to the repo for each project and at least one noteable commit for each (with git hash, one line description)
• New participants in rnode testing
  • I'd like to see a handful of names with the dates they started participating.

I took a quick look at the cited documents and it's not easy to find this sort of evidence. But assuming it's in there, I'm supporting the $2000 budget for this work for September (and I'm looking for a couple more trusted voters).

With the current limited pool of trusted voters, handling the many reward votes looks awkward. I'm considering relaxing constraints on reward votes.

[jimscarver]

Yes dan, I suggest certifying some apprentices would not hurt much as they would not have much weight if the masters disagree and they can help with the reward votes.

I agree there should be better organization in the channels. We do have significant notes and videos. It is a challenge getting people to take responsibility to do proper documentation. There has been progress on a number of issues. A significant number have been helped with rnode and rholang in our channels and videos though not all have been recorded. Code repos are generally pinned to the channels doing the work.

Work on the discord rho-bot (kycbot) in and out of scheduled work studies is included in this issue. A separate issue will be added going forward. Last month improvements to log filtering, adding blockquote support for rholang and eval, and reporting stdout replies from the log to the discord channel were significant improvements made in September.

I am still leading much of the colab work but there is good progress toward it becoming autonomous and decentralized. I think this activity should be encouraged and a budget over $2000 be considered. I do not think the $3750 requested in the sheet is excessive. The value produced is significant though it might be guided better. In my experience the cost of equivalent work in real world is likely to be much greater.

[dckc]

The discord bot for running Rholang code is pretty cool.

But I don't see how that goes beyond the "Progress on at least one or two software development projects" included in the $2000 budget.

In the sheet, many rows have nothing in the "Contribution" column. When I add up the others, I get exactly $2000.

And I did relax constraints on reward votes: no need to be trust-metric-certified: #785 (comment)

---

For reference:

kycbot$ git log --since="Sep 1" "--date=format:%Y-%m-%d %I:%M %p" --pretty=tformat:"%ad%x09${repo}%x09%h%x09%s"
2018-09-27 09:02 PM             35ab378 Added ```rholang and ```eval and cature stdout from log and post to discord.
2018-09-25 11:12 AM             9410346 added stdput reply to channel from log tail for eval:
2018-09-20 09:48 PM             18bc4fc Merge branch 'master' of https://github.com/jimscarver/kycbot
2018-09-20 09:45 PM             e1b79f6 fixed deploy and propose, addeed ```rholang

kycbot$ git diff --stat 514403ea558c60107cf63c2115cfdcce609595e5 -- . ':(exclude)package-lock.json'
 README.md    |  47 +++++++++++++++++-
 package.json |   4 +-
 server.js    | 152 ++++++++++++++++++++++++++++++++++++++++++++++++-----------
 3 files changed, 174 insertions(+), 29 deletions(-)