On Sun, Mar 04, 2018 at 11:24:34PM -0500, Andras Farkas wrote:
> What do you have to hide from FreeBSD users? Why should users trust
> people who hide things from them?
When I posted email to an internal list, I was under the impression
that it would remain confidential.
Someone, I don't know
I knew this would be end result of that coc(k) being whipped out.
Also, I'm sure that it's not feminism you hate, it's that some idiots hide
under that blanket and imagine they can't be attacked anymore.
Why did that need for a new set of weird rules come out anyway? Right now
it feels like
On 3/4/2018 10:40 PM, Franco Fichtner wrote:
> Hi there,
>
>> On 4. Mar 2018, at 10:02 PM, Jeff Roberson wrote:
>>
>> First of all this is really not an appropriate forum for this discussion.
> Nobody discusses it elsewhere. "Decisions" are made between closed doors.
>
On 3/4/2018 5:13 PM, Julian H. Stacey wrote:
> d...@freebsdfoundation.org wrote:
>> Hi David,
>>
>> This is Deb Goodkin, Executive Director for the FreeBSD Foundation. The
>> Foundation isn't responsible for the CoC, that would be the FreeBSD
>> Project's core team. Please don't spread
On 3/5/2018 11:09 AM, Julian H. Stacey wrote:
> Bryan Drewery wrote:
>> This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
>> --oex5zYNtdOsHH7CGnZTm2mPFhuBKYldVo
>> Content-Type: multipart/mixed; boundary="YJ0tBWvLQToy5jfzJdV74lsXFyKkOJvV1";
>> protected-headers="v1"
>> From: Bryan
On 2018-03-05 12:51, Bryan Drewery wrote:
> On 3/4/2018 5:13 PM, Julian H. Stacey wrote:
>> d...@freebsdfoundation.org wrote:
>>> Hi David,
>>>
>>> This is Deb Goodkin, Executive Director for the FreeBSD Foundation. The
>>> Foundation isn't responsible for the CoC, that would be the FreeBSD
>>>
Bryan Drewery wrote:
> This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
> --oex5zYNtdOsHH7CGnZTm2mPFhuBKYldVo
> Content-Type: multipart/mixed; boundary="YJ0tBWvLQToy5jfzJdV74lsXFyKkOJvV1";
> protected-headers="v1"
> From: Bryan Drewery
> To: "Julian H. Stacey"
On 2018-03-05 15:51, Mark Linimon wrote:
> On Mon, Mar 05, 2018 at 02:48:26PM -0500, Stephen Cook wrote:
>> The problem with the Foundation sponsoring a CoC is that a small group
>> of extremists forced their way in to generate and implement their own
>> set of rules, secretly.
>
> This is
On Mon, Mar 05, 2018 at 02:48:26PM -0500, Stephen Cook wrote:
> The problem with the Foundation sponsoring a CoC is that a small group
> of extremists forced their way in to generate and implement their own
> set of rules, secretly.
This is exactly not what happened.
> I suspect from the lack of
Hi, Reference:
> From: Bryan Drewery
> Date: Mon, 5 Mar 2018 11:28:04 -0800
Bryan Drewery wrote:
> This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
> --Dfb89j1723L9zFot341vqJ5ixcKpqkUga
> Content-Type: multipart/mixed;
On Mon, Mar 05, 2018 at 05:17:59PM -0500, Stephen Cook wrote:
> On 2018-03-05 15:51, Mark Linimon wrote:
> > On Mon, Mar 05, 2018 at 02:48:26PM -0500, Stephen Cook wrote:
> >> The problem with the Foundation sponsoring a CoC is that a small group
> >> of extremists forced their way in to generate
On Mon, Mar 05, 2018 at 11:46:59PM +0100, Julian H. Stacey wrote:
> I agree with the other person's thoughts that FreeBSD fixes uncommited
> for years destroys incentive to file more fixes.
I do not know anyone who disagrees with this.
The issue is how to get people involved with this utterly
On Mon, Mar 5, 2018 at 2:46 PM, Julian H. Stacey wrote:
>
> Read https://www.freebsd.org/internal/code-of-conduct.html
> It's a mess of some sense & some ridiculous, force fed to FreeBSD.
> Expect some not to like force feeding, or proponents thereof.
> Expect forceful
13 matches
Mail list logo