Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:53271 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 40761 invoked from network); 13 Jun 2011 16:55:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Jun 2011 16:55:49 -0000 Authentication-Results: pb1.pair.com header.from=justin@justincarmony.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=justin@justincarmony.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain justincarmony.com from 74.125.83.170 cause and error) X-PHP-List-Original-Sender: justin@justincarmony.com X-Host-Fingerprint: 74.125.83.170 mail-pv0-f170.google.com Received: from [74.125.83.170] ([74.125.83.170:45714] helo=mail-pv0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 14/B1-14457-21146FD4 for ; Mon, 13 Jun 2011 12:55:47 -0400 Received: by pvh10 with SMTP id 10so2352336pvh.29 for ; Mon, 13 Jun 2011 09:55:43 -0700 (PDT) Received: by 10.68.39.72 with SMTP id n8mr2577194pbk.93.1307984143796; Mon, 13 Jun 2011 09:55:43 -0700 (PDT) Received: from [192.168.1.104] (c-24-10-180-216.hsd1.ut.comcast.net [24.10.180.216]) by mx.google.com with ESMTPS id p5sm581180pbk.20.2011.06.13.09.55.41 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 13 Jun 2011 09:55:42 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii In-Reply-To: Date: Mon, 13 Jun 2011 10:55:36 -0600 Cc: David Coallier , Pierre Joye Content-Transfer-Encoding: quoted-printable Message-ID: <220C7657-1A18-4C7A-8333-84F67755E441@justincarmony.com> References: To: internals X-Mailer: Apple Mail (2.1084) Subject: Re: [PHP-DEV] [IDEA/PRE-RFC] PHP Core Mentorship Program From: justin@justincarmony.com (Justin Carmony) I like the idea for the mentorship program. I also agree with Pierre = with the things we'll want to avoid while doing it. Pierre brought up a good point about how ideally a mentorship program = wouldn't be necessary, but the website, wiki, etc would have all the = resources and information for people to jump in and contribute. The = problem is, the current system of doing that isn't perfect, so I think = the mentorship system can accomplish two things: First, add the human element to helping bring in new comers into a = complex system. I know people can already hop in, but it is a daunting = task. Having a mentor who you could have more than email conversation = (irc, im, phone, etc) can help get people up to speed quicker. I would = feel less dumb asking my dozens of dumb questions (questions that do = have answers somewhere online, but either I couldn't find them or didn't = understand them) to a mentor, rather than spam the internals list with = them. The mentorship helps new volunteers get in an imperfect system = quicker. Second, and just as important, that the mentors and mentees *Document* = and try to *Fix* the hurdles they discover during the mentorship. This = will help improve the overall barrier of entry for other new volunteers. = I think this could be the greatest ROI of the program, making it easier = for the next new volunteers. I'm willing to be a mentee and help start this program. I have some = ideas for the program, but don't want to spam everyone with a wall of = text about them. Justin Carmony On Jun 13, 2011, at 9:12 AM, Rafael Dohms wrote: > On Mon, Jun 13, 2011 at 10:16 AM, David Coallier = wrote: >> See response inline. >> ... >> See Pierre, that's where I believe we are doing things wrong. We >> already have all our infrastructure to report bugs, create wiki = pages, >> send emails. The goal of the program is to create something more >> personal, something more interactive than just sending everyone to >> read the manual. >> ... >> -- >> David Coallier >>=20 >=20 > I agree here with David, i think the mentorship would bring a "human" > interface for newcomers. > Yes we already get newcomers, but we could get much more if we had a > human interface instead of hitting everyone with a TL;DR documentation > page. Let their first interaction be with a human who can then direct > to the page at given points. >=20 > Mentorship has grown some awesome developers in the community, i think > it can do the same in internals. >=20 > And yes, we still need all of those pages described, this is an extra > layer on top of everything being done. If we can get mentors who like > to help the i say we go for it. >=20 >=20 > --=20 > Rafael Dohms > PHP Evangelist and Community Leader > http://www.rafaeldohms.com.br > http://www.phpsp.org.br >=20 > --=20 > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php >=20