From owner-freebsd-fcp@freebsd.org Fri Aug 30 16:19:55 2019 Return-Path: Delivered-To: freebsd-fcp@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D8111D243F for ; Fri, 30 Aug 2019 16:19:55 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46Kl7H447yz4GVB for ; Fri, 30 Aug 2019 16:19:55 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: by mailman.nyi.freebsd.org (Postfix) id 89E7AD243C; Fri, 30 Aug 2019 16:19:55 +0000 (UTC) Delivered-To: fcp@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 89942D243B; Fri, 30 Aug 2019 16:19:55 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 46Kl7G1Hmrz4GV8; Fri, 30 Aug 2019 16:19:53 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x7UGJnOn095329; Fri, 30 Aug 2019 09:19:49 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x7UGJnUt095328; Fri, 30 Aug 2019 09:19:49 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201908301619.x7UGJnUt095328@gndrsh.dnsmgr.net> Subject: Re: FCP 20190401-ci_policy: CI policy In-Reply-To: <20190830015805.GA16894@troutmask.apl.washington.edu> To: sgk@troutmask.apl.washington.edu Date: Fri, 30 Aug 2019 09:19:49 -0700 (PDT) CC: Cy Schubert , Ian Lepore , FreeBSD Hackers , araujo@freebsd.org, fcp@freebsd.org, Konstantin Belousov , Li-Wen Hsu , Kristof Provost X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 46Kl7G1Hmrz4GV8 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd-rwg@gndrsh.dnsmgr.net has no SPF policy when checking 69.59.192.140) smtp.mailfrom=freebsd-rwg@gndrsh.dnsmgr.net X-Spamd-Result: default: False [2.43 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.49)[0.485,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.77)[0.767,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.23)[0.233,0]; RCPT_COUNT_SEVEN(0.00)[9]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.04)[ip: (0.15), ipnet: 69.59.192.0/19(0.07), asn: 13868(0.05), country: US(-0.05)]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-fcp@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FreeBSD Community Proposals List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2019 16:19:55 -0000 > On Thu, Aug 29, 2019 at 06:35:41PM -0700, Cy Schubert wrote: > > > > What about weekends? I notice commits tend to slow down during weekends. I > > suspect people who work on FreeBSD at $COMPANY for a living treat it as a > > job, which it is. However this should be considered. > > > > A committer, who works for a $COMPANY and has no intention of > looking at the mailing lists or CI reports until Monday, should > not commit on Firday. What ever happen to common sense? Perhaps this speaks to another issue then, I know the community is a whole against rules, procedures, requirements, etc all, but I'll again stick my head across the block and say: Should it be added to the committers guide that a committer is expected to be "responsive" to commit especially, and project in general emails for 48 hours following any commit? Would that not solve some of this? I do know from first hand interactions that several project members foo@freebsd.org email is basically /dev/nulled into a mail box that gets cleaned out on some random schedule. That technically goes against the requirement that if your a committer your suppose to be reading commit mail but I can agree that the volume of commit mail has become an overwhelming problem. One I do wish we had a better answer to than just ignore it. Regards, -- Rod Grimes rgrimes@freebsd.org