From owner-freebsd-questions@FreeBSD.ORG Mon Aug 18 12:14:22 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B489337B405 for ; Mon, 18 Aug 2003 12:14:19 -0700 (PDT) Received: from viefep16-int.chello.at (viefep16-int.chello.at [213.46.255.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE71F43F85 for ; Mon, 18 Aug 2003 12:14:17 -0700 (PDT) (envelope-from martin@tradex.sk) Received: from tradex.sk ([217.23.250.194]) by viefep16-int.chello.at (InterMail vM.5.01.05.17 201-253-122-126-117-20021021) with ESMTP id <20030818191416.EEXI14479.viefep16-int.chello.at@tradex.sk> for ; Mon, 18 Aug 2003 21:14:16 +0200 Message-ID: <3F412867.6000403@tradex.sk> Date: Mon, 18 Aug 2003 21:26:31 +0200 From: Martin Matuska User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@FreeBSD.org X-Enigmail-Version: 0.76.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Accepting new commiters X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2003 19:14:22 -0000 Hello, I am writing a master thesis about open source development processes and one of my analysis objects are processes of the FreeBSD project. The FreeBSD documentation (handbook, articles) is a great source of information, but there are some points missing in the documentation I consider important. I would like know more on the following items: 1. Who makes the decision, who is authorized and who is responsible for accepting (adding) new commiters? 2. Who makes the decision, who is authorized and who is responsible for releasing (deleting) existing commiters (whatever reason)? A great help would be a link to a document describing this issue (but a simple answer helps, too). Thank you very much.