From owner-freebsd-ports@freebsd.org Wed Aug 5 10:51:59 2015 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 337379B3C62 for ; Wed, 5 Aug 2015 10:51:59 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from slim.berklix.org (slim.berklix.org [94.185.90.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AD019135A; Wed, 5 Aug 2015 10:51:57 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (p5B2272CF.dip0.t-ipconnect.de [91.34.114.207]) (authenticated bits=128) by slim.berklix.org (8.14.5/8.14.5) with ESMTP id t75At4f9027267; Wed, 5 Aug 2015 12:55:04 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id t75ApoE6059441; Wed, 5 Aug 2015 12:51:50 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id t75Apc7X032698; Wed, 5 Aug 2015 12:51:50 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201508051051.t75Apc7X032698@fire.js.berklix.net> To: freebsd-ports@freebsd.org cc: Matthew Seaman Subject: Re: Self committing... allowed or not? From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultants, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Tue, 04 Aug 2015 18:02:36 +0100." <55C0F02C.1020707@FreeBSD.org> Date: Wed, 05 Aug 2015 12:51:38 +0200 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Aug 2015 10:51:59 -0000 Matthew Seaman wrote: > On 04/08/2015 17:28, Loganaden Velvindron wrote: > > I would like to know how hard would it be for our FreeBSD experts to > > hack SVN to allow port maintainers commit to individual ports to speed > > up the process :p ? > > Technically that's probably not too difficult. Debian has a system like > that, using PGP signatures for authentication, which we could probably > steal^Wcopy without too much trouble. > > The real kicker though is about maintaining code quality. This is > pretty much why committers exist: they are people who have shown > competence in dealing with src / ports / docs whatever and have > demonstrated they can maintain standards. One of a committers primary > functions is to either fix or get the submitter to fix problems with > submissions before committing. > > Now, it's almost certainly true that many port maintainers who aren't > already committers would be perfectly competent at updating their own > ports. Chances are though if such a maintainer has been sufficiently > active and has submitted enough to establish their competence then > they'd be a definite prospect as a full-blown committer anyhow. ie. if > you're good enough to commit changes to your own ports, then you're > pretty much good enough to commit changes to any port, so you might as > well have a ports commit bit. Number of commiters ? I vaguely recall about 300 or 400 ? { http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/staff-committers.html Contains one friend who said he'd resigned his commit bit. So maybe list out of date. https://wiki.freebsd.org/BecomingACommitter http://www.freebsd.org/doc/en/articles/committers-guide/committer.types.html A quick skim shows no number } Number of Ports Maintainers: 1567 { cd /pub/FreeBSD/branches/-current/ports find . -type f -name Makefile | xargs grep MAINTAINER > /tmp/ports_named find . -type f -name Makefile | xargs grep -h MAINTAINER > /tmp/ports_unnamed wc -l po* 24295 ports_named 24295 ports_unnamed sort ports_unnamed| uniq | grep @ ... a spot of vi trimming of spaces tabs & ?= & = to reduce variance & allow uniq to strip more ... A few of those addresses will be @freebsd list names, & some people@freebsd } Cheers, Julian -- Julian Stacey, BSD Linux Unix C Sys Eng Consultant Munich http://berklix.com Reply after previous text, like a play - Not before, which looses context. Indent previous text with "> " Insert new lines before 80 chars. Send plain text, Not quoted-printable, Not HTML, Not ms.doc, Not base64. Subsidise contraception V. Global warming, pollution, famine, migration.