From: "Ywe Cærlyn" <ywecrn@protonmail.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: GNU Kind Communication Guidelines / New Code Of Conduct = Insufficient Pseudoreligion
Date: Sat, 27 Oct 2018 15:09:21 +0000 [thread overview]
Message-ID: <Ce1OrZUIKKJZyE28D1mL8aNrD4BML-9pLpY6UKDn6n8ctccnxJto5ai2626rc37CLPJTpxWAOuHUbjFhAtm3bBr1BrjH6kQRrCwyWQT0rug=@protonmail.com> (raw)
Hello.
As a researcher I started a trend in here a few years ago, where criticism of the lack of coherent philosophy behind Linux, now seems to have resulted in a few lines of pseudoreligious statements, that supposedly is the answer to this, called "GNU Kind Communication Guidelines" and "New Code Of Conduct".
Again, ofcourse none of this will solve anything. A full and coherent philosophy is needed. I/O in the 50s was indeed based in "God", and a biblical background. For a full coherent philosophy, globally, one needs the roots, and corrected roots, and that means a Quran now, with full corrected Ibrahimic background. Islam indeed is an inescapable growing trend, and just as any good development should be accepted.
.
Indeed The Quran states, deal justly, and fair pay measures should be implemented kernelwise. So that indeed available source can be a real alternative in this businessdominated sector.
A global fair pay available source system, would be the logical conclusion and next move, and requires such a philosophical coherence.
And one day people might be grown enough to do without Pingu idols: https://www.youtube.com/watch?v=N-hg7ENwFUg
Do not wait for GNU7 Unyx w/ Mate.
This is it.
Best,
Ywe Cærlyn
WIP - https://www.youtube.com/channel/UCR3gmLVjHS5A702wo4bol_Q
next reply other threads:[~2018-10-27 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 15:09 Ywe Cærlyn [this message]
2018-10-31 14:07 GNU Kind Communication Guidelines / New Code Of Conduct = Insufficient Pseudoreligion Ywe Cærlyn
2018-11-06 12:02 ` Ywe Cærlyn
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='Ce1OrZUIKKJZyE28D1mL8aNrD4BML-9pLpY6UKDn6n8ctccnxJto5ai2626rc37CLPJTpxWAOuHUbjFhAtm3bBr1BrjH6kQRrCwyWQT0rug=@protonmail.com' \
--to=ywecrn@protonmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).