From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Dual Head
Date: Thu, 13 Jul 2006 12:15:47 -0500 [thread overview]
Message-ID: <200607131215.53030.bss03@volumehost.net> (raw)
In-Reply-To: <5bdc1c8b0607130650x3cf6fc75uda0f52077548b26a@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2330 bytes --]
On Thursday 13 July 2006 08:50, "Mark Knecht" <markknecht@gmail.com> wrote
about 'Re: [gentoo-amd64] Re: Dual Head':
> On 7/13/06, Duncan <1i5t5.duncan@cox.net> wrote:
> <SNIP>
> slaveryware
> <SNIP>
> freedomware
> <SNIP>
>
> Must we use such charged language around here?
Duncan's had this discussion with a number of people, I'm sure. I seem to
remember this list (or another gentoo list) having a small sub-thread
about it. Actually, it got me thinking and, now, among company that
understands the sentiment I use the same terminology along with
smatterings of "too bad I can't use <that> in the free world".
I choose not to use it on the list or most other setting, because it rubs
some people wrong, particularly the word "slaveryware" [1]. Generally,
this is because people see it as making light of slavery. I don't; EULAs
and the vast majority of software licenses in use today *do* take away
your rights and attempt to put you in shackles so you can't get away.
It's unfortunate that people see this as acceptable, but then again there
were hundreds of years of human history in which slavery was seen as
acceptable.
Then again, I'm pretty far "out there" even among my friends. Just as
selling yourself into slavery was made illegal, I do see a time when Rule
of Law will prevent one from giving/trading/selling away their software
freedoms. I do hope that there are some allowances made from the
artistic/creative aspects of source code (and software in general).
In any case, Duncan's not going to change. If you are offended I encourage
you to take up the issue with Duncan off-list. If that will/does not
satisfy you, you will probably need to just killfile Duncan and hope "such
charged language" doesn't get quoted too often.
--
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh
[1] "Freedomware" is usually less of an issue since it's really just a
alternate shortening of "Free/Libre, Open-Source Software"
normally "F/LOSS". Personally I like "freedomware" because it helps
emphasize what Stallman, GNU, and the FSF provide with their software:
freedom.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-07-13 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 5:06 [gentoo-amd64] Dual Head Trevor Rhodes
2006-07-13 13:38 ` [gentoo-amd64] " Duncan
2006-07-13 13:50 ` Mark Knecht
2006-07-13 14:00 ` Mark Haney
2006-07-13 17:11 ` [gentoo-amd64] " Duncan
2006-07-13 17:15 ` Boyd Stephen Smith Jr. [this message]
2006-07-13 18:25 ` [gentoo-amd64] " Kyle Liddell
2006-07-13 18:40 ` Piotr Pruszczak
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=200607131215.53030.bss03@volumehost.net \
--to=bss03@volumehost.net \
--cc=gentoo-amd64@lists.gentoo.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