From owner-freebsd-fcp@freebsd.org Thu Aug 29 15:52:46 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 D660DDA484 for ; Thu, 29 Aug 2019 15:52:46 +0000 (UTC) (envelope-from lwhsu.freebsd@gmail.com) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46K6ZQ4hQyz3N0M for ; Thu, 29 Aug 2019 15:52:46 +0000 (UTC) (envelope-from lwhsu.freebsd@gmail.com) Received: by mailman.nyi.freebsd.org (Postfix) id A0E42DA482; Thu, 29 Aug 2019 15:52:46 +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 A090BDA481; Thu, 29 Aug 2019 15:52:46 +0000 (UTC) (envelope-from lwhsu.freebsd@gmail.com) Received: from mail-yw1-f48.google.com (mail-yw1-f48.google.com [209.85.161.48]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46K6ZP5rFhz3N0J; Thu, 29 Aug 2019 15:52:45 +0000 (UTC) (envelope-from lwhsu.freebsd@gmail.com) Received: by mail-yw1-f48.google.com with SMTP id i207so1296530ywc.9; Thu, 29 Aug 2019 08:52:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=wY3QqHOPLSUlCOb4QmA9woMOMytMceJZ9WNhi9JsvlM=; b=CYWnJ8vNpdiBVrHFHRT05p1bEF2BUGCKrxwembIDbWQtYG4SjLr/cYSHStplFMSU9c ySjsDcJpvm1Ev9lK8ROgBOwvoD8opCnLq+y3IfYIy0mqhdcWDmm0cY2zM+1TVFBE3Arl 4IgfBWCIv13a/NMLFK8TNwF3L4OJGhzLEYF60Qwk4sdT7oI3GT9SAmf1MCpiJO8w+vih a3E18wLVVx9ux2XAz0RMWIlApTLgLBvZlXmsFo+R9NIpsgsLJPXPU8mcuvcTWtr4GVhm lvDLFRSd/nt7D+7YKl8maTtsQbPMMPUU7kat2UDuwRjvaVEfg1r5jA4NnWmQCzCEpS+c 9c2A== X-Gm-Message-State: APjAAAUE9JMFS0i/ncc/76YqR4tgkmV3LDibGm51zzVDvPphKlMqU+j+ 4mFdzKJ7V4TUxHDuQV5fMlTbY3b9sz918vh75UN1FeV9 X-Google-Smtp-Source: APXvYqwSf91pWiPN9dYEGQSlr8I/x8+1FRo41YZhZ6mp+Ir88nYMezpj5tvO48mwXFlTygEOH5/EFE6wnhk3eQUzpmk= X-Received: by 2002:a0d:ca02:: with SMTP id m2mr7784840ywd.400.1567093964422; Thu, 29 Aug 2019 08:52:44 -0700 (PDT) MIME-Version: 1.0 References: <20190829114057.GZ71821@kib.kiev.ua> <412537DD-D98F-4B92-85F5-CB93CF33F281@FreeBSD.org> <20190829144228.GA71821@kib.kiev.ua> <20190829153712.GB71821@kib.kiev.ua> In-Reply-To: <20190829153712.GB71821@kib.kiev.ua> From: Li-Wen Hsu Date: Thu, 29 Aug 2019 23:52:29 +0800 Message-ID: Subject: Re: FCP 20190401-ci_policy: CI policy To: FreeBSD Hackers , fcp@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 46K6ZP5rFhz3N0J X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of lwhsufreebsd@gmail.com designates 209.85.161.48 as permitted sender) smtp.mailfrom=lwhsufreebsd@gmail.com X-Spamd-Result: default: False [-5.93 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; TAGGED_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_TLS_ALL(0.00)[]; IP_SCORE(-2.93)[ip: (-8.95), ipnet: 209.85.128.0/17(-3.34), asn: 15169(-2.32), country: US(-0.05)]; NEURAL_HAM_SHORT(-0.99)[-0.994,0]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[48.161.85.209.list.dnswl.org : 127.0.5.0]; FORGED_SENDER(0.30)[lwhsu@freebsd.org,lwhsufreebsd@gmail.com]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[lwhsu@freebsd.org,lwhsufreebsd@gmail.com]; 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: Thu, 29 Aug 2019 15:52:46 -0000 I was really hesitated to send out the previous mail because I understand this is a sensitive topic and some words might look scary. My apologies if the proposal makes people uncomfortable. Please calm down, this is just an idea, not call for vote or say it will proceed as-is. We want to point out there is a thing may worth to be discussed, and hope to collect the comments and suggestions, we know the proposed way is not perfect, and that's why we need better idea from more people. I am really bad at writing, but some items I hope people can check: - Yes we're doing good now, and we should keep it and let's try to do better. - Please check the weekly CI report to see the build (and test) statistics, we still have some rooms to be improved. Let's try to get bugs fixed before users asking on -current or -stable. Of course we cannot cover all parts of the system, but that means we can always do more contributions. - We have been running CI for few years, perhaps it's still too early, but let's try to pay more attention to it. If there are things imperfect, let's fix it. I cannot watch the results, do preliminary analysis and call people to check, just by myself along, at least not forever. I hope we can have a more automatic and scalable way. - There is no one want to "control" the contribution, instead, we hope this could make collaboration more smoothly. As there are more and more contributors, we should have a way to keep head and stable branches buildable and have less regressions as we can as possible, then everyone can work together with more confidence. - The "revert" part and the timeline looks scary, please think this is the last and unwanted solution. The description is try to limit its scope and encourage people do analysis, communication and fix first. The words here absolutely should be improved. Updating the committer guide is really a good idea, and we probably should define what means "unresponsive", like in ports we have maintainer timeout and even maintainer reset. Thanks the feedback from all of you. I think encouraging people to discuss and keep the discussion record is one of the purposes to have FCP process. Best, Li-Wen