From owner-freebsd-ports@freebsd.org Thu May 17 23:36:32 2018 Return-Path: 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 BDA17EE3573 for ; Thu, 17 May 2018 23:36:32 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from mail-ot0-x22c.google.com (mail-ot0-x22c.google.com [IPv6:2607:f8b0:4003:c0f::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2FFD17B8E1 for ; Thu, 17 May 2018 23:36:32 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: by mail-ot0-x22c.google.com with SMTP id t1-v6so7019454ott.13 for ; Thu, 17 May 2018 16:36:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sippysoft-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Mjh3ECjshzxHCZaNBOtBDOcIv3fzOJ07iaJDag+ONcY=; b=F2AuKHNW8WnmO2Mb36DSHV6jw+YvZ4sCrPXghll6xYgnSDZBOJ3iM35319bU++LwCc mamNk1eg1ezGipGvfyTv1457KiTC81ywXP4r6z1BaoaZXYHPhNkOCRbQs/jQKHn189JA q3mqIrs9Td3Fx0DDPn1hSG/j7g2ftyCXZMXJ8KamQU9X4nQt8w/zTXPOvAo6wnqTSDyS KLKGqgTLuHwwLNEzswioFSru+FWmrViFVAO6UpR1gVQm9C2qwLN4tK3m3eEg/x+/8xN4 yCIxvp5t7D6G1AIy6zd9//HReGCheBeCf5fh3R8/1ChAlmEKZfA8nAhezUlEZyCJ3+30 bDYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=Mjh3ECjshzxHCZaNBOtBDOcIv3fzOJ07iaJDag+ONcY=; b=Ymg7BoqZvCCmZXinZPiRmGQqb741FqW/aH4mgjG3AnkG1+TNUJjp1HPWP+QetLSsq7 jlpMktoLfdlHoj5dr65jEIw05RUKR9r5jY/Ik6F2+ykhM/nm5y6GOF1lY0JMyvMCGFcj 1235yvOZULkW2dU/yrXIegDyGhsPCocIWzyjSHTnHh9D5nbCmYit3QYlxfnQe9nUp3di O682ihsnhxZYJvgcZPqbZIb+jeL4/7FgRckHwlsaD2vQRNGwYT8WV1KJBJvtCF1xvGsf oiTH6D8aT666ja/zqkKABSz4Lgf+2YDzlD2iayDiIP6bmUMgUV/RoDiiRlash012S12v nyGw== X-Gm-Message-State: ALKqPwf92Wu8Rv+73sEBo8UIrgrqvf04cz6BUF8R7rwFhhVM5JG2xhSB JC8QA8BsSS6mcpZpWNeZ2OuEIyaRI118BI+4mg0OxA== X-Google-Smtp-Source: AB8JxZrXsxa/2ptpV2dHabJSLgsdY4TGYXn/PH+LeZ9V8u37ZVMKLrkQ4kKVzCjHRkyn+Bi7wvrR6lSWeXd3thuGqSY= X-Received: by 2002:a9d:40ad:: with SMTP id n42-v6mr4700293ote.389.1526600191447; Thu, 17 May 2018 16:36:31 -0700 (PDT) MIME-Version: 1.0 Sender: sobomax@sippysoft.com Received: by 10.201.93.67 with HTTP; Thu, 17 May 2018 16:36:30 -0700 (PDT) In-Reply-To: <732c3f40-1765-6883-dbec-f5c77db8e30c@saltant.com> References: <3cc77471-4200-1f45-e83d-2ae4d636f4fa@saltant.com> <732c3f40-1765-6883-dbec-f5c77db8e30c@saltant.com> From: Maxim Sobolev Date: Thu, 17 May 2018 16:36:30 -0700 X-Google-Sender-Auth: Bay5gEdLcDxdn9EazGPozthQ50I Message-ID: Subject: Re: Practice of "Sponsored by" in commit messages To: "John W. O'Brien" Cc: FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 May 2018 23:36:33 -0000 Well, if your employer feels slighted it's for him to bring it up with you (see my previous rant on the amount and scope of the credit and who parties involved). And then for you to bring it up with me if you feel brave enough. :) I don't see how and why FreeBSD project can help in this highly hypothetical scenario by putting some rules around. Do we have any real-world examples of this happening, bring me at least one out of probably tents of thousands of times people used "Sponsored by" in their commit messages. Just a single one, please! ) -Max On Thu, May 17, 2018 at 4:29 PM, John W. O'Brien wrote: > On 2018/05/17 19:18, Maxim Sobolev wrote: > > John, no, not really, sorry. Work is done, credit is given. The form and > > amount of this credit is between whoever does the work and whoever is > > being credited. I don't see why is there any third-party to be involved > > in governing whether or not this credit is "appropriate", "sufficient" > > or "all encompassing" for the work in question. This is just a credit, > > it does not affect the quality of work, nor the license (which is > > 2-clause BSD) nor the copyright holder. Three things that really matter > > long-time. So "Sponsored by" it's just the message on the t-shirt, > > having only meaning to whoever produces the piece and whoever wears it, > > but nothing in particular to the outside world. IMHO. > > I fear that you and I are still not on the same page. The difference > between a t-shirt and a commit message is that two or three or four > people can all do work on the same commit, but only one person can wear > a t-shirt. > > Taking the analogy further, if you hang a t-shirt with your employer's > logo on a piece of work that you and I collaborated to produce, don't > you think my employer might feel slighted? What if I had done 80% of the > work? > > > On Thu, May 17, 2018 at 3:43 PM, John W. O'Brien > > wrote: > > > > On 2018/05/14 20:14, Maxim Sobolev wrote: > > > What's wrong with a current practice. Why is it of any concern to > you, > > > John? Just curious that is not very clear from your message. It is > like > > > someone trying to moderate what people in general or some group in > > > particular (e.g. freebsd committers) are allowed to put on their > > > t-shirts just because you find it offensive or inappropriate. > > > > I don't find crediting sponsors offensive nor inappropriate. Quite > the > > contrary. What I find problematic is when multiple people do work, > not > > all with sponsorship or the same sponsorship, and only one person's > > sponsor is mentioned in a way that seems to imply that all the work > was > > sponsored. > > > > What I'm proposing is not to end or ban the practice, but to improve > and > > refine it so that sponsors are credited for what they sponsor and not > > for what they don't sponsor. > > > > Is that clearer? > > > > > On Mon, May 14, 2018, 4:40 PM John W. O'Brien > > > >> wrote: > > > > > > Hello FreeBSD Ports, > > > > > > The Committer's Guide section on Commit Log Messages [0], > > doesn't cover > > > the use of the "Sponsored by" key word. As a non-committer > > contributor, > > > it only recently occurred to me to wonder what work that > credit is > > > intended to represent, and whether some light definition would > be > > > helpful to reduce ambiguity. > > > > > > When a committer credits a sponsor of theirs, from which the > > contributor > > > received no sponsorship, the portrayal feels a little awkward. > > Does this > > > strike the list as a problem, and if so, how ought it be > solved? > > > > > > To make this concrete, allow me to illustrate the situation. > > > > > > Alice, working on her own time, prepares and contributes a > > patch. Bob, > > > who works for Acme Corp, reviews and commits the patch on > > company time. > > > The commit message includes "Sponsored by: Acme Corp". Alice > > eagerly > > > awaits her check from Acme Corp. Should the commit message > > have read > > > "Sponsored by: Acme Corp (Bob)"? > > > > > > This could be extensible to multiple sponsorships. If, > > instead, Alice > > > prepares the patch having received a grant to do so from Best > > Sys Dev, > > > the commit message could state "Sponsored by: Acme Corp (Bob), > > Best Sys > > > Dev (Alice)". > > > > > > [0] > > > > > https://www.freebsd.org/doc/en_US.ISO8859-1/articles/ > committers-guide/article.html#commit-log-message > > committers-guide/article.html#commit-log-message> > > > > > > PS: I realize that this issue transcends ports, but it's not > > clear where > > > I should send this instead, and this list seems like it would > > have a > > > reasonably high concentration of people with a stake in the > > discussion. > > > -- > John W. O'Brien > OpenPGP keys: > 0x33C4D64B895DBF3B > >