Announcing the 'FreeBSD Community Process'

Matthew Seaman matthew at
Tue Jun 20 10:28:31 UTC 2017

On 2017/06/20 10:55, Roger Pau Monné wrote:
> On Wed, Jun 14, 2017 at 07:53:47AM +0100, FreeBSD Core Secretary wrote:
> [...]
>> 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 at mailing list
>> placing fcp-0000 into 'feedback' status.  Your contributions are
>> welcome, by email to the fcp at mailing list, or by submitting
>> issues or pull requests, or by annotating the document text
>> through GitHub.
> Why is the master repository hosted on github?
> I think it's fine to have mirrors on github, but I don't fancy at all
> having the master repository hosted there. FreeBSD has AFAIK always
> hosted it's repositories on self managed infrastructure, and IMHO we
> should continue to do so.

Part of the reasons for starting out on GitHub is that it makes it very
easy for anyone get involved by creating Pull Requests (can be done
entirely through the GitHub web interface) and also to present the FCP
documents attractively rendered with very little up-front work.  That
doesn't mean that GitHub has to be the final answer.

Certainly we should have a mirror of this repo on Project controlled
hardware, in case GitHub disappears overnight.

However GitHub versus not-GitHub is precisely the sort of argument that
inspired the whole FCP process -- likely to descend into futile
dead-horse-flogging and bikeshed-painting.  Core would be delighted to
see one or more properly thought out proposals put up for discussion in
the form of FCPs for alternative ways of hosting the FCP process.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 972 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the freebsd-fcp mailing list