From owner-freebsd-chat Mon Nov 17 09:14:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA24738 for chat-outgoing; Mon, 17 Nov 1997 09:14:41 -0800 (PST) (envelope-from owner-freebsd-chat) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA24731 for ; Mon, 17 Nov 1997 09:14:32 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id RAA05420 for ; Mon, 17 Nov 1997 17:14:26 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id SAA07538; Mon, 17 Nov 1997 18:14:25 +0100 (MET) Date: Mon, 17 Nov 1997 18:14:25 +0100 (MET) Message-Id: <199711171714.SAA07538@bitbox.follo.net> From: Eivind Eklund To: chat@freebsd.org Subject: Example of mentor page Sender: owner-freebsd-chat@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Regarding the mentoring possibility I just sent a message about - here is a suggestion for a web-page to better describe what I was talking about: %includes; ]> &header;

The intention behind The FreeBSD mentor project is to give outside parties developing from FreeBSD a channel into the formal FreeBSD development process. This is not intended to be a replacement for the normal mailing lists, but a way for outside developers to get certain way of getting timely feedback and integration.

The workings are very simple - to get a mentor, send a mail to hackers@freebsd.org with a subject of "Call for Mentor" or similar, with the body of the mail containing a small description of your interests and what kind of project you are doing or are interested in doing with FreeBSD.

The mentor will have the following responsibilites:

  1. Providing timely integration or rejection of changes.

  2. Giving information on the FreeBSD project structure where that is unclear to the mentoree.

  3. Answer questions relating to the mentorees FreeBSD devlopment project to the best of his/her ability (in the cases where it isn't obvious that this should go to a larger audience).

  4. Set the mentoree in contact with other FreeBSD developers in the cases where it is obvious that this is something that should be done in collaboration with another developer.

Aquiring a mentor will of course not free the mentoree from their normal responsibility of attempting to gain knowledge from documentation and source before contacting using other people's time. A mentor can reject a mentoree at any point (how could we stop this?), but should not do this without a good reason. Examples of reasons include abuse of the mentors time by the mentoree, and the mentor just plain running out of time

&footer