O> Onboarding Skills inventory: Developer? Writer? Redditor? etc.

[dckc]

I suggest we encourage new members to fill out a skills inventory. Perhaps when they join formally, but also as part of "welcome to RChain" messages on telegram etc.

edit: After a couple weeks of discussion, we have:

• RChain Coop Introductions (View / respond)
  • short URL: https://goo.gl/ffWXzD
• Edit
  • Responses spreadsheet (available to members of rchain@googlegroups.com only)

---

earlier:

By way of example:

• i2b2 transmart foundation kick-off survey June 2017

This perhaps overlaps with #15, but that discussion is so long I can't tell quickly. If there is already a skills inventory, I would like a list of those who identified themselves as software developers.

I discussed this briefly with @patrick727 and he suggested I notify @drbloom and @lapin7 .

[lapin7]

I created once this form: https://docs.google.com/forms/d/1FJMSkmscappmuN5HbZz1TlqgOWRcgQsdike4Q6-X8p0/edit

We need a kind of form, because there's no interchange between the official member onboarding and the Activist/Member onboarding.

We need to add a request for becoming a member of rchain@googlegroups.com. How do we do that?

[kitblake]

In terms of onboarding workflow, this form should probably follow CONTRIBUTING.md, as in "Please scan the contributing doc, and IF you wanna contribute, THEN fill in this _form_."

(Btw, if anybody is reading this issue via email the form link doesn't work, but it does via the Github UI.)

[Viraculous]

Nice @kitblake. I think the skills inventory when followed, in collaboration with #208, particularly concerning peer learning and work group would bring about constructive synergy among cooperating peers. It could be an adaptive tool for onboarding members.

[dckc]

@lapin7 Do you have any/many developer responses from that survey?

I'm interested to work toward something simpler.

[BelovedAquila]

I buy this idea, very necessary,it tends to streamline and create effective management of issues. I find it that if every member (new members perse) fills In a form containing it's skills inventory, i.e areas of deep knowledge, expertise and experience, issues would be easily managed. Such that, the management of issues would also be guaranteed to be at trusted hands who can effectively manage, analyze and resolve them . Likewise, when the need of a skill arises in the cooperation, someone can easily be identified to its rescue. Some instances being, the need for transcripts of Rchain Vision into several languages, if skills are being outline in a segment of a form(maybe a skill inventory form), those who are transcribers can easily be spotted and from there the issues can be carried on, such that as transcribers, if they are not able to transcribe a language they might be having links to experts in that language who can. This thereby, would result in effective management and smooth sailing of the cooperation. Basically one who is skilled or an expert in programming tends more to do well in handling issues as regards to programming. To add to it, In respect to the issue on ground, I also suggest, there should be a sort of redirection of issues to each member based on the skills being outlined or presented by that member. for instance; when we are having issues that are needing of editors, marketers, developer's e.t.c, such issues should be sent like a notification or it sort to members who have outlined or notified in the skill inventory form as having such skills in editing and transcribing, vise versal. This really is a great step to development and effective management in the cooperative.

[lapin7]

@dckc My skills-inventory-form never went on line. Great that you want to work toward something simpler. I'm looking forward to the new form and to the integration in the CONTRIBUTING.md.

We could also create a form for a skill endorsement. Something like LinkedIn.

I think it's still to early for management of matching issues and skills. At the moment I'm very happy when somebody takes the initiative of doing something, instead of suggesting or managing others. :-) Anyway it's good to have profiles of our members.

[dckc]

Oh... right... linkedin skills... why reinvent the wheel? For better or for worse, a critical mass of the RChain community uses linkedin. We might as well just collect linkedin profile URLs.

I wish discord supported links to them. (#210)

[lapin7]

If you click on your own name, then you can write a note. For example the url to your linkedin profile. Like this:

[dckc]

That was my first idea too, @lapin7 , but as I pointed out in #210, nobody else can see those notes.

[lapin7]

Oh what a bummer :-(

-- Cheers, HJ

On Wed, Jan 10, 2018 at 5:15 PM, Dan Connolly notifications@github.com wrote:

That was my first idea too, @lapin7 https://github.com/lapin7 , but nobody else can see those notes.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rchain/Members/issues/222#issuecomment-356651892, or mute the thread https://github.com/notifications/unsubscribe-auth/AB0x99do0Uy2kAg3xOCr8TKW37wyLOsCks5tJOI2gaJpZM4RV2Ms .

[dckc]

I drafted something:

• RChain Coop Introductions

[kitblake]

That works. I filled it in. Took two minutes, that's what we want.

[ResonanceXX]

Checking the boxes. There doesn't seem to be a change when it is prompted. I'll try some other way. But keep an eye on that. Cheers and well done.

[lapin7]

Sweet.

Could you add GPS location: latitude, longitude. 2 digits is enough. like 52, 4 for NL

And consider optional sections

The intro could give some links to social media and a sign up for rchain@googlegroups.com like: https://groups.google.com/forum/#!forum/rchain/join

Think also about a confirmation message and what we could put in there.

Once you fill out this form, there has to be an ongoing flow of interaction to trigger new users. Like did you know this and that And how to do this and that

-- Cheers, HJ

On Fri, Jan 12, 2018 at 8:36 AM, Chris Ken notifications@github.com wrote:

Checking the boxes. There doesn't seem to be a change when it is prompted. I'll try some other way. But keep an eye on that. Cheers and well done.

Sent from Yahoo Mail on Android

On Fri, 12 Jan 2018 at 6:42, kitblakenotifications@github.com wrote: That works. I filled it in. Took two minutes, that's what we want.

— You are receiving this because you are subscribed to this thread.

Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rchain/Members/issues/222#issuecomment-357164521, or mute the thread https://github.com/notifications/unsubscribe-auth/AB0x951UtphsjwbzxbwWsKCZ52uEzpCPks5tJwuAgaJpZM4RV2Ms .

[kitblake]

Did trying another way work?

I requested editing rights from @dckc for the form. @ResonanceXX, if you do the same we can work on improving it.

[ResonanceXX]

Of course. I'm strongly inclined to help out. But I wouldn't rush off to make edits. I'd have to know alot more about the subject matter.  

[kitblake]

Hey, why don't we work together on this @ResonanceXX? Instead of editing @dckc's form (because his forte is actually core code), we'll make a new form and recreate what he did. Then as we craft the content we'll learn about Google forms and we can fine tune the user experience.

Here's a start: https://docs.google.com/forms/d/171oKtb6Y7h3ICeoVkUoWQeSTc8vD2bU8YHns9tRd3os/edit?usp=sharing You should be able to edit, if not lemme know.

[dckc]

I don't know my lat/long. I like to use "nearby airport" for rough geographic location. I'll try that.

More on the rest later...

On Fri, Jan 12, 2018 at 4:31 AM, HJ Hilbolling notifications@github.com wrote:

Sweet.

Could you add GPS location: latitude, longitude. 2 digits is enough. like 52, 4 for NL

-- Dan Connolly http://www.madmode.com/

[dckc]

I marked mine OBSOLETE in favor of the copy by @kitblake and made some edits there.

• added a "get involved in the bounty system" blurb above the list of skills
• added location / airport
• in confirmation message, added mention of youtube and twitter and link to FAQ

I'd rather not do sections. I'd like to keep this to "front side of one page". I don't want anybody to go "ugh. too long. Screw it."

[BelovedAquila]

@kitblake would love contributing to the recreation, I added some things I found vital to it since it's a skill inventory form ,such as; -A brief Rchain introduction, -Edited the theme at the top tabular, -Added telegram to the medias, -Created a fit in for activities/interest, -Added to the list skills/experiences to broaden the scope(technical support,computer activities,legal practitioner), -Added skill proficiency, -Suggestions and Inquiries. And am still on it though,still put to making it more outstanding and simple. https://docs.google.com/forms/d/171oKtb6Y7h3ICeoVkUoWQeSTc8vD2bU8YHns9tRd3os/edit what do you think?

[lapin7]

Maybe it's nice to integrate these forms: https://docs.google.com/forms/d/e/1FAIpQLSc7PSiN8D0Af60Wbaz-sMnt0jMcFjO5EZMxjHYuGFiU7y1DDQ/viewform

https://docs.google.com/forms/d/171oKtb6Y7h3ICeoVkUoWQeSTc8vD2bU8YHns9tRd3os/edit

I like sections and before a section begins you can add a way out to submit. When you get bored of the form you can submit at any moment.

[kitblake]

Thanks for the improvements @dckc and nice work @BelovedAquila. Looks much better! Especially now that the default google style is gone.

Somehow the submit button is gone too. I tried to fill in the form. Probably a result of the burst of editing.

We should do some testing, meaning fill in the form so we have some example data. That will help us determine what fields we want to keep. For this particular form, I'm with @dckc that it should be dead simple. Personally I hate filling in yet-another-profile and I'm the type that would say "Screw it".

Have we an idea for what the ultimate destination of the data will be? Would be good if it comprised a 'Talent Pool'. Then when someone needed, say, a developer or lawyer, they could peruse the data. A google spreadsheet might be sufficient. We can tweak the presentation (column widths, etc) so it'll be readable.

[Keaycee]

Nice work everyone who edited the form @BelovedAquila @dckc . But the form need some adjustment. Especially the skills. I will have to work on the form and grant an access rchain@googlegroups.com for any further edit.

[kitblake]

Go for it @Keaycee. On second look, I'm also missing the: 'added a "get involved in the bounty system" blurb above the list of skills'

This form will be part of the onboarding workflow so mentioning the bounty system provides incentive. It'll be nice to have a definitive signal that so-and-so is onboard and would like to contribute. That bell has been missing so far. (Ideally a real living person will follow up.)

[BelovedAquila]

There you go @Keaycee let's make it outstanding. @kitblake yes, such beep ups would go a long way. Your point made in the bracket happens to be true, one tends to follow up such beeps or signal on impulse. We see to it.

[Keaycee]

@kitblake I made some adjustment on the form.

https://docs.google.com/forms/d/e/1FAIpQLSeopRXm-DfVRxpYmlPTm4tE0xJKYWDNxFVQ3CVNp492qp-GRA/viewform

There is a need to remove edit permission after any future inputs so as to enable members to fill in the form. I had already shared edit permission to rchain@googlegroups.com which is important. I suggest the public edit permission be removed so member can start filling the form.

[dckc]

This has gone in a very different direction from what I had hoped.

• Why not lead with a profile URL, since lots of RChain folks already maintain a profile on linkedin etc. that gives their name, skills, etc.
• Why "RChain is a blockchain platform ..."? This is for people who have already joined the coop, no?
• Why separate first name from last name?
• How are caps and gowns relevant?

Making it more than one screenful gives an "oh no... how long is this thing?" feeling, to me. I didn't look beyond the first page.

[BelovedAquila]

@dckc I have succeeded in -Adjusting the name issue,
-Changing the caps and gown, does the present, work for it?, if No, then I could still figure out another. -Check out the profile URL also, if that's what should be. And as regards to the "Rchain is a blockchain platform", Wish I understood you better, what do you think it should have been?

[dckc]

I am more interested in answers to my "why ...?" questions than adjustments.

Rather than "RChain is a blockchain platform..." I think it should have been as in the form I drafted: "Let's get to know each other so we can work together better." Along with "get involved in the bounty system".

[dckc]

@kitblake wrote:

Have we an idea for what the ultimate destination of the data will be?

Very good question. I lean toward a spreadsheet shared with rchain@googlegroups.com .

Whatever the destination is, we need to be clear about it up front. One person who was considering filling out the form expressed concern about where their contact information was going.

[BelovedAquila]

@dckc It was "Rchain is a blockchain platform" because I felt there was a need to a brief enlightenment on what Rchain is all about. I still made an edit on that, it should be checked out. And yet still, if we are not finding the brief definition necessary, then we could work on something more appropriate. For the other Why's, they have been reworked on, you actually have a sensitive point in those indirect notifications made on them,I observed the inventory was getting seemly overboard with what needs to be filled in,which can get boring, discouraging and it tends to nullify our aim of making the inventory as simple, organized and outstanding as planned(No one enjoys filling a form whose length competites with that of an essay) .
The inventory should still be reviewed though.

[kitblake]

I responded privately to the guy who complained about the form via googlegroups with this:

Hi Tesfaye,

Sorry about that. We are indeed working on a form for new members. We’d like to create 
a Talent Pool. However it was not the intention that people fill it out. The form is not 
even close to ready for prime time. 

One of the people involved shared the form, for editing, with rchain@googlegroups and 
apparently everybody got an email. If we do that again in the future we must include an 
explanatory note with the share action. 

Thanks for the feedback about personal information too. It’s a critical issue.

We have to be careful using that googlegroups list. Any shares need a corresponding message.

[Keaycee]

@kitblake He has got a point there. When creating a form (Draft), it's not necessary to make it open for the entire public member to be able to edit because they can also have access to the response of others on the form. I suggest the form should be created and managed my one or more people. I know we all are cooperative members, we can drop our suggestion about the form here on the thread issue on github. If you're the sole creator of the form, you don't have to make it open for public edit. Some members are not familiar with googles doc, forms and spreadsheet. They can easily mess it up without knowing when. I suggest the public edit permission be closed or this form in circulation be deleted and let someone volunteer to make a new form without a public edit permission.

[kitblake]

I trashed the form. There's a new clean copy of @dckc's form: https://docs.google.com/forms/d/1lpmSUL6P_NhXghF8WNM4V3n4v54zzEnSJIkn2vGhpCY/edit?usp=sharing

1. @Keaycee is right, we should not have shared it with the entire RChain googlegroup.
2. Access is restricted. If you want to edit, please request access via the button. Right now, Dan and @Keaycee have access, and anybody who wants to contribute is welcome.

We went a bit overboard with the enthusiastic editing. :) However I was happy to see people contributing! So chalk it up to learning curve.

The context of this form is it will follow CONTRIBUTING.md, so people are already aware of RChain's reward infrastructure. A simple blurb that Dan can hopefully replace is all we want in the beginning.

The form has to be dead simple, aka KISS.

• Short, fitting on one desktop screen.
• No sections.
• No required fields.
• Profile URL at the top. That's what we really want.
• Entire name in one field. We can split it later.
• Let's limit the number of skills to essentials (crypto is a given).
• Skip the Skills Proficiency, that'll become clear on interaction.
• Skip Participant Type.

Whoever did the styling, it looked really good. Nice to see the RChain red used as an accent. The header image on my screen is stretched and blurry. Perhaps use the header image from the Gov forum form: https://docs.google.com/forms/d/e/1FAIpQLSdnXEzZ8fSK4u486Two8z42OPiN3FBtlF7RyFAxgPWJZtIK8Q/viewform

Currently the responses are stored in the Google form itself. It should be possible to instead have the responses appended to a Google sheet. I don't know how to do that but hopefully someone can figure it out. As that sheet will contain personal information like email addresses, it can't be public or openly shared.

Probably we'll need to pipe the collected data from the sheet to a visual representation in a protected environment. That's TBD.

Thanks everyone!

[Keaycee]

Good job for trashing the form @kitblake . Well, the form should only be viewable to cooperative members. Any contribution and suggestion should be state here at the issue thread. Member who wants to contribute or has a suggestion to make about the form should state it and it will be edited my the moderators of the form. @kitblake I'm glad you understand my point.

[lapin7]

Please insert an optional section before the submit that handles reimbursements.

[lapin7]

And it would be great if another optional section is available for skill inventory. Plus some info about our media channels and collaboration how to's. Something like the pinned message on TG.

[lapin7]

And what about the workflow? Follow up etc.

[Keaycee]

@lapin7 I will add the skill inventory on the reimbursement form (Draft).

[Keaycee]

There is a need to get all this forms orderly and arranged. We've got a lot of forms (Draft) and most of them are not yet filled or seen by members of the cooperative. We've got cooperative members on Telegram, Discord, Github, Reddit etc., But some of them are not aware of this forms. We need to these forms to be filled out by our cooperative members.

[dckc]

@kitblake I tweaked the new draft.

[kitblake]

I tweaked the form a bit and connected a spreadsheet. You should all have an invitation. Please test. https://docs.google.com/forms/d/e/1FAIpQLSdP42ZJ-UQ8HU1QkO_lywWbfAqxTJWYG2TWRgbQon6h5BeuKw/viewform

After this dev test I'd like to ask the 'usual criminals' to do a beta test. Once we're satisfied, we can open the Intro form up to all Members, prob with an announcement in Discord.

As the intention is to keep this Intro form totally simple, I thought maybe we can create a second form for a Talent Pool, and link to it in the response. That form can go into more detail about skills, etc. What do you all think of that?

[dckc]

If the 2nd form is about a talent pool, what would the first form be about?

Look, I want to know when a software developer joins the membership. If we simplify beyond that, we've gone too far.

[kitblake]

I'm suggesting we leave the Intro form just like it is now, really simple.

But there's also a desire to collect more information, about specific skills, etc. and we can't both KISS and collect lots of info. So I wondered.. but let's move forward with just this for now.

If people are reading via email, here's a link to please test the form: https://docs.google.com/forms/d/e/1FAIpQLSdP42ZJ-UQ8HU1QkO_lywWbfAqxTJWYG2TWRgbQon6h5BeuKw/viewform

[Keaycee]

@kitblake I agree with you. Let's keep simple. Like you said, there will be need to get more information but we could start with this. With this, we could put together contributing members on github, discord and other channel with their specialty. We know the RChain community is growing steadily, How do we get the new members to fill in this form? Is there a need to inform members on the RChain telegram groups?

[dckc]

"will only be shared with RChain Members" isn't clear enough; how does somebody new know who the RChain Members are? Do we even have a mechanism to constrain access to coop members? I changed it back to rchain@googlegroups.com .

I was a little surprised by "If you would like to join our Talent Pool, please [contact ops@rchain.coop]. " in the confirmation message, but I suppose it is part of the process detailed in CONTRIBUTING.md. I made the link explicit.

[lapin7]

The form is OK. But it's a missed opportunity to get more info. This is easy possible with "Conditional Sections". If one answers YES then you go on with more questions. If it's NO then you go directly to submit. Make it email obliged. Discord ID doesn't interest me. I want a Github ID. Make a field for comment. And at the end you can send an email to the participant with his results and the option to change the answers later.

-- Cheers, HJ

On Mon, Jan 15, 2018 at 8:33 PM, Dan Connolly notifications@github.com wrote:

"will only be shared with RChain Members" isn't clear enough; how does somebody new know who the RChain Members are? Do we even have a mechanism to constrain access to coop members? I changed it back to rchain@googlegroups.com .

I was a little surprised by "If you would like to join our Talent Pool, please [contact ops@rchain.coop]. " in the confirmation message, but I suppose it is part of the process detailed in CONTRIBUTING.md. I made the link explicit.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rchain/Members/issues/222#issuecomment-357770756, or mute the thread https://github.com/notifications/unsubscribe-auth/AB0x97LaVTUADr_853xlC_h0b9MHAkU1ks5tK6gHgaJpZM4RV2Ms .

[dckc]

Discord ID interests me because when I'm on discord, I want to know who these people are. (See grumbles about discord profile limitations in #210).

Field for comment on what? Don't the three current free-response questions suffice? For comments on the form itself, let's use this issue.

Earlier I looked for a way to do conditional sections but didn't see one. Help?

I thought about turning on the email authentication feature, but email doesn't seem to be a big part of RChain culture. I'm concerned that it will cause people to go "oh screw it." On the other hand, maybe we're concerned about bogus responses and this would help with that some?

[lapin7]

Here is draft with a try out for the use of sections. View Edit

[dckc]

I'm confused... What does this have to do with travel reimbursement?