From owner-freebsd-fcp@freebsd.org Wed Jun 14 20:38:17 2017 Return-Path: Delivered-To: freebsd-fcp@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 6096BBF380F for ; Wed, 14 Jun 2017 20:38:17 +0000 (UTC) (envelope-from rpaulo@me.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4190377EB1 for ; Wed, 14 Jun 2017 20:38:17 +0000 (UTC) (envelope-from rpaulo@me.com) Received: by mailman.ysv.freebsd.org (Postfix) id 3E238BF380E; Wed, 14 Jun 2017 20:38:17 +0000 (UTC) Delivered-To: fcp@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 3DB63BF380D for ; Wed, 14 Jun 2017 20:38:17 +0000 (UTC) (envelope-from rpaulo@me.com) Received: from st13p97im-ztdg18301101.me.com (st13p97im-ztdg18301101.me.com [17.41.193.160]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 157B677EB0; Wed, 14 Jun 2017 20:38:17 +0000 (UTC) (envelope-from rpaulo@me.com) Received: from process-dkim-sign-daemon.st13p97im-ztdg18301101.me.com by st13p97im-ztdg18301101.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0ORJ00K00YIOBE00@st13p97im-ztdg18301101.me.com>; Wed, 14 Jun 2017 19:38:10 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1497469090; bh=YTWSYN6T0ee7A+0A61y7HAXx/aXMjTufdZk+YmntKZM=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=Zh5wmD7ij9GVyUG0AIqb+AdCvB3G4eAwQ9Fzg32WPe9pjglsc4zn4EOisynx1zSOn vXXJVDnaELfq3t2SY8R1Iwu/SEnRWRuKhp3TRXnGbiU3XOdh0VkBDDHV1UaXE91tz0 ruyvwKLwFHa2RT3tavzSmfr1nDhmyvjOnLFTThj2TH4ABPeOjltrTv6/nqOFUA6cSB Fep0GmXSX/CwkdBpHFkDuTUMTSNTG2eadEC7USHwvNK6XszGOsXflrE01iMF+HeRt+ nPbM0z11btbvr6NdRuXmS0ZFeclLJTWDFipLrNjjgEuxKE4ILS8Fq9mFUPYjCEG92D q1fq3J8/RRtGw== Received: from icloud.com ([127.0.0.1]) by st13p97im-ztdg18301101.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0ORJ00GBJYJK4V30@st13p97im-ztdg18301101.me.com>; Wed, 14 Jun 2017 19:38:10 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-06-14_05:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=1 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1706140328 Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (Mac OS X Mail 11.0 \(3436\)) Subject: Re: Announcing the 'FreeBSD Community Process' From: Rui Paulo In-reply-to: Date: Wed, 14 Jun 2017 12:38:07 -0700 Cc: FreeBSD Developers Content-transfer-encoding: quoted-printable Message-id: References: <539e27d3-4eca-463a-75d4-667d3fec90f6@FreeBSD.org> To: fcp@freebsd.org X-Mailer: Apple Mail (2.3436) X-BeenThere: freebsd-fcp@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD Community Proposals List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jun 2017 20:38:17 -0000 On Jun 13, 2017, at 23:53, FreeBSD Core Secretary = wrote: >=20 >=20 > Dear all, >=20 > Core has just presented their ideas for a new 'FreeBSD Community > Process' at BSDCan. This will provide a more formalized mechanism for > proposing and deciding on important or contentious changes within the > Project. The idea is to avoid discussions degenerating into an > interminable argument on the mailing lists with ultimately no action > being taken. >=20 > The FCP process is modelled on similar ideas in other projects, > particularly the Python Enhancement Process > (https://www.python.org/dev/peps/pep-0001/), the Joyent RFD Process > (https://github.com/joyent/rfd/blob/master/README.md), and even the > venerable IETF RFC Process > (https://www.ietf.org/about/standards-process.html) >=20 > In summary, anyone wanting to make a change that will result in a > non-trivial effect on the FreeBSD User Base, (or retrospectively = anyone > having backed out a change after running into contention over = something > that turned out less trivial than they anticipated), should write down > what they propose to change, describing what problem they are trying = to > solve, how they propose to solve it and what consequential impact this > will have. Contact the fcp-editors@ mailing list for assistance in > getting your proposal into releasable state. The document is then = added > to the FCP index, committed into the FCP repository and published for > discussion. Each FCP proposal is a living document and will be = updated > to reflect any conclusions resulting during the discussion. >=20 > Once consensus has been achieved, or the discussion has gone on for > enough time, Core will vote on accepting the FCP. Core will be voting > according to the mood of the discussion around the proposal. >=20 > The current state of fcp-0000.md -- the document that defines the FCP > process -- can be viewed at >=20 > https://github.com/freebsd/fcp/blob/master/fcp-0000.md >=20 > This is a working document and subject to change. We will be applying > the FCP process as far as possible to fcp-0000 itself: this message > counts as the formal announcement on the fcp@FreeBSD.org mailing list > placing fcp-0000 into 'feedback' status. Your contributions are > welcome, by email to the fcp@FreeBSD.org mailing list, or by = submitting > issues or pull requests, or by annotating the fcp-0000.md document = text > through GitHub. >=20 > For help with generating a new FCP document and discussion around the > FCP process please join the fcp-editors@FreeBSD.org mailing list. I think the FCP idea is good, but I don=E2=80=99t like the fact that = only core@ can vote. Core has been an entity that doesn=E2=80=99t get = to decide much on the direction of the project and I was under the = impression that most people were okay with this because the developers = were the ones deciding the direction of the project. Why can=E2=80=99t = committers vote? =E2=80=94 Rui Paulo