How should this program work?

[jasonrhodes]

Broad title, right? The discussion started here: node-forward/welcome#6

... but we should continue it here in the new repo. Is just the README and gitter.im room enough to support people in a way that counts as "mentorship"? Here are two other related programs:

• Hapi.js Mentorship Program: http://hapijs.com/help
• PHP Mentoring Program: http://phpmentoring.org/

If the idea is to encourage people with questions to create issues here and/or participate in Gitter chat, I think we should give it a certain period of time and then evaluate how it's gone over that time. To do that, I think we only need a few things:

• Restructure the README so it speaks to mentees first, with language about how to ask for help and maybe some examples of how this is different than IRC or Stack Overflow.
• Think about a path for asking for help that isn't as public as the two mentioned above...
• Think about how to deal with issues like language, i18n, etc

Let's get these sorted out by December 1, if possible, and then give it 3 months and see what kind of response this minimalist method generates.

Anything big I'm missing to get started?

cc: node-forward/welcome#7

[hackygolucky]

@jasonrhodes I've really dropped the ball while I've been travelling recently with this. Sorry.

A few things we need to address immediately, hopefully tying in your concerns:

• a Code of Conduct and contributing.md
• the restructure of the README(yay!)
• the path forward that isn't public for mentees/mentors: the discussion I've had with @nvcexploder about the Hapi program is that a form is essential to this. I've got a final draft I'd love you to take a look at, and then in the meantime those willing to help(you, me, friends) will help match good fits. Then I could add that to the READMe.
• language and translations would be super helpful. For health of project, I would also say recruiting people from all over in order to spread the word and get help with that component. This is certainly not a strength of mine.

We should get all of this added to node-forward.org I also owe @mikeal work on the nodeforward CoC and contributing.md but I'm not sure if after the node advisory board stuff I'm supposed to hold off.

[jasonrhodes]

+1 to all of this! I'll take a look at the form later today.

[hackygolucky]

We'll get the CoC and contributing.md here first, as that's smaller scope. CoCs tend to start wildfires these days and introducing one to node-forward overall is not something I have energy for this afternoon.

[mikeal]

Tracy, I added you as an owner of the org so that you can create a CoC repository. The CoC should apply to all of Node Forward so it would be best if it was at the top level. When you’re done please add it to the main website as well :)

On Nov 20, 2014, at 3:35AM, Tracy [email protected] wrote:

We'll get the CoC and contributing.md here first, as that's smaller scope. CoCs tend to start wildfires these days and introducing one to node-forward overall is not something I have energy for this afternoon.

—
Reply to this email directly or view it on GitHub #26 (comment).

[hackygolucky]

@mikeal sounds good to me 👍

[a0viedo]

Anyone had a mentoring experience through this program? Interested in hearing some feedback.

[42thcoder]

@dead-horse 能求个指教么

[dead-horse]

@42thcoder 当然，私聊？