All of lore.kernel.org
 help / color / mirror / Atom feed
From: "\\0xDynamite" <dreamingforward@gmail.com>
To: Bernd Petrovitsch <bernd@petrovitsch.priv.at>
Cc: "jonsmirl@gmail.com" <jonsmirl@gmail.com>,
	Theodore Tso <tytso@mit.edu>,
	fche@redhat.com, riel@surriel.com, ec429@cantab.net,
	Olof Johansson <olof@lixom.net>, Jonathan Corbet <corbet@lwn.net>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Code of Conduct: Let's revamp it.
Date: Wed, 26 Sep 2018 14:34:07 -0500	[thread overview]
Message-ID: <CAMjeLr_cx5+96NGedcYB-MjugA53_j+tksP0Na8W9GY-PAhoZA@mail.gmail.com> (raw)
In-Reply-To: <9be16b08-7aa9-d42e-24c0-f054af39b78a@petrovitsch.priv.at>

>>>> So, is code a *published* item?  Most of the public can't read it.
>>>
>>> I cannot read (or understand) neither Russian nor Chinese nor almost any
>>> natural (let alone dead) languages of the world. I'm pretty sure that
>>> I'm not the only one;-)
>>> Does that make Russian literature non-public? I don't think so ...
>>
>> You confuse the issue.  My definition included "intended for the
>> public".  But it isn't clear that open source code is intended for the
>> public -- it is intended for those who code or wish to.

> Well, then I have to repeat myself: Signed-off source code (in form of
> patches) in a well-known programming language for a (nowadays)
> well-known GPLv2 licensed project mailed on "everyone can subscribe"
> mailinglists, (thus) to be found in several $SEARCH_ENGINE-indexed
> mailinglist archives, if accepted to be found in lots of publicly
> accessible git repos can be not intended to be published?

You did it again.  You changed words.  I said intended for the public,
and you ended your sentence with "intended to be published".

Like it or not, both the law and English grammar have ambiguities.
People put up with them because they share a common intuition (in a
lot of cases) of what each other means.

If you share a birthday card with your personal love note inscribed
and the birthday girl sends it around to everyone at the party, have
you been violated?  She might argue:  how did you expect it to remain
private if you knew there were several people invited to the birthday
party?

> I wonder what else must happen.

Wonder no more.

Mark

  reply	other threads:[~2018-09-26 19:45 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19  6:00 Code of Conduct: Let's revamp it Edward Cree
2018-09-19 14:18 ` Jonathan Corbet
2018-09-19 23:35   ` Edward Cree
2018-09-20  1:16     ` Olof Johansson
2018-09-20  2:14       ` Edward Cree
2018-09-21  1:48         ` Rik van Riel
2018-09-21  2:16           ` unixing
2018-09-21 13:07           ` Frank Ch. Eigler
2018-09-21 16:34             ` \0xDynamite
2018-09-21 23:15               ` Theodore Y. Ts'o
2018-09-21 23:20                 ` Joey Pabalinas
2018-09-21 23:31                 ` jonsmirl
2018-09-21 23:59                   ` Bernd Petrovitsch
2018-09-24 18:59                     ` \0xDynamite
2018-09-24 19:45                       ` Bernd Petrovitsch
2018-09-25  2:24                         ` gratuitouslicensesarerevocable
2018-09-25 17:14                         ` \0xDynamite
2018-09-26  0:41                           ` Bernd Petrovitsch
2018-09-26 19:34                             ` \0xDynamite [this message]
2018-09-26 20:55                               ` Joey Pabalinas
2018-09-28 18:34                                 ` \0xDynamite
2018-09-28 15:56                             ` Alan Cox
2018-09-28 19:38                               ` jonsmirl
2018-09-29 12:44                               ` Eric S. Raymond
2018-09-29 12:46                               ` Eric S. Raymond
2018-09-22  0:05                   ` Joey Pabalinas
2018-09-22  0:24                     ` jonsmirl
2018-09-24 17:43                       ` Max Filippov
2018-09-24 18:07                         ` jonsmirl
2018-09-23 18:44                 ` \0xDynamite
2018-09-25 23:48                 ` Michael Woods
2018-09-24 17:25             ` unconditionedwitness
2018-09-25 11:28         ` Pavel Machek
2018-09-25 12:36           ` Christoph Conrads
2018-09-25 13:13             ` Eric S. Raymond
2018-09-25 13:41               ` Christoph Conrads
2018-09-25 17:38                 ` \0xDynamite
2018-09-25 13:28             ` Pavel Machek
2018-09-26 10:24               ` Martin Steigerwald
2018-09-25 15:14             ` Theodore Y. Ts'o
2018-09-25 22:30               ` Eric S. Raymond
2018-09-26 11:17               ` Christoph Conrads
2018-09-20  3:07       ` Theodore Y. Ts'o
2018-09-20  4:18       ` Willy Tarreau
2018-09-20  9:27         ` unconditionedwitness
2018-09-20 22:57           ` Edward Cree
2018-09-23 14:50             ` Christoph Conrads
2018-09-23 18:41             ` \0xDynamite
2018-09-24 17:21             ` unconditionedwitness
     [not found]               ` <c61eb2d545150d46428f4bc25843cd58@redchan.it>
     [not found]                 ` <201809241941.44460.dr.klepp@gmx.at>
     [not found]                   ` <20180924204809.GK23968@linuxmafia.com>
2018-09-25  2:09                     ` [DNG] Fwd: " gratuitouslicensesarerevocable
2018-09-20  9:29         ` unconditionedwitness
  -- strict thread matches above, loose matches on Subject: below --
2018-09-20 21:18 Christoph Conrads
2018-09-21  8:09 ` Martin Steigerwald
2018-09-21 11:36   ` Christoph Conrads
2018-09-17 11:48 Lukas Wunner
2018-09-17 12:24 ` Greg Kroah-Hartman
2018-09-18 19:16   ` Pavel Machek
2018-09-19 10:30     ` Mauro Carvalho Chehab
2018-09-18 20:16   ` Lukas Wunner
     [not found]     ` <61b4a3f9-ccd1-061c-1c1b-ec993b056c66@bosch-fellbach.de>
2018-09-20 10:57       ` Lukas Wunner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMjeLr_cx5+96NGedcYB-MjugA53_j+tksP0Na8W9GY-PAhoZA@mail.gmail.com \
    --to=dreamingforward@gmail.com \
    --cc=bernd@petrovitsch.priv.at \
    --cc=corbet@lwn.net \
    --cc=ec429@cantab.net \
    --cc=fche@redhat.com \
    --cc=jonsmirl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=riel@surriel.com \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.