From owner-freebsd-ports@freebsd.org  Fri May 18 18:20:05 2018
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2172EB0DF7
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Fri, 18 May 2018 18:20:04 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 740A482D42
 for <freebsd-ports@freebsd.org>; Fri, 18 May 2018 18:20:04 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1fJjz3-0003nC-Kr; Fri, 18 May 2018 20:20:05 +0200
Date: Fri, 18 May 2018 20:20:05 +0200
From: Kurt Jaeger <lists@opsec.eu>
To: Eitan Adler <lists@eitanadler.com>
Cc: "John W. O'Brien" <john@saltant.com>,
 FreeBSD Ports <freebsd-ports@freebsd.org>
Subject: Re: Practice of "Sponsored by" in commit messages
Message-ID: <20180518182005.GG37752@home.opsec.eu>
References: <CAH7qZfs8eNMkkeQ0eyV5AcapOCQFFL1fUiBDR1aM1875-Cy-Lg@mail.gmail.com>
 <3cc77471-4200-1f45-e83d-2ae4d636f4fa@saltant.com>
 <CAH7qZfu6j+c-HpjHnwxyeQTKwX9DavN4iAzSpMO5Kjy9VJ2uHw@mail.gmail.com>
 <732c3f40-1765-6883-dbec-f5c77db8e30c@saltant.com>
 <CAH7qZftNadmygyPNW9HNPWTY9kU6W7j-409CrV0XGk6ZYDQTug@mail.gmail.com>
 <7b14a5c4-7320-8f5e-b8c3-f49809caf9e5@saltant.com>
 <20180518041501.GF37752@home.opsec.eu>
 <CAF6rxgnHeSEAOw_qbMeWEiSEX3dbcu7ASPBVthsCXkaZ+f+BaQ@mail.gmail.com>
 <31190803-e6ba-428b-0954-341dad2f1916@saltant.com>
 <CAF6rxgmNL2pRJwJUz39Cfw=Di5sfhN3PvSCfwTrsupQ86gHcFw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAF6rxgmNL2pRJwJUz39Cfw=Di5sfhN3PvSCfwTrsupQ86gHcFw@mail.gmail.com>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 18 May 2018 18:20:05 -0000

Hi!

> >>>> The FreeBSD project could help by asking committers to qualify
> >>>> "Sponsored by" lines to indicate which participant(s) is(are) sponsored,
> >>>> in way that is equivalent to the way that the actual work itself is
> >>>> customarily attributed.

> >>> This sounds reasonable, so I suggest that you submit a
> >>> patch to the ports handbook that describes it for maintainers
> >>> and committers.

> >> One thing to note: FreeBSD has a custom patch to subversion to detect
> >> "ORGANIZATION_NAME" and automatically append it to the default
> >> template. This is likely why its getting added in unexpected places.

> > How do you think I should handle that in my forthcoming doc patch? Is
> > there a related bug I should file against services?

> Its a client side patch of the subversion binary.  I'm not sure the
> best way to handle it beyond perhaps changing the template a bit?

What change would be needed ? There's already a Sponsored by field ?

The custom patch is here:

https://svnweb.freebsd.org/ports/head/devel/subversion/files/extra-patch-fbsd-template?revision=411397&view=markup

-- 
pi@opsec.eu            +49 171 3101372                    2 years to go !