public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Henrik Brix Andersen <brix@gentoo.org>
To: gwn-feedback@gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Misquoted in the GWN
Date: Mon, 28 Nov 2005 10:48:01 +0100	[thread overview]
Message-ID: <20051128094800.GA32340@dmz.brixandersen.dk> (raw)

[-- Attachment #1: Type: text/plain, Size: 2007 bytes --]

A friend of mine just alerted me to the fact, that I am featured in
this weeks Gentoo Weekly News. Odd, I thought, noone had asked me
anything regarding the GWN...

So I fired up a web browser and there it was - first section in the
GWN [1]. Seems the GWN authors have read my blog entry [2] and decided
to bring their own version of it to the public.

* The GWN talks about WiFi Protected Access (WPA). My Blog talks about
  IEEE 802.11/wired authentication in general.

* The GWN talks about "my plans" for deprecating xsupplicant. My blog
  doesn't say anything about this.

* The GWN talks about removing xsupplicant from Gentoo Portage. My
  blog certainly doesn't say anything about this.

* The GWN doesn't even link to my blog entry, from which they must
  have gotten the initial idea for this article, thus not allowing
  their readers to see that the information provided is incorrect.

Now, why wasn't I contacted prior to quoting my blog in the GWN? A
simple "will this be ok?" kind of mail would have sufficed. I could
have pointed out the wrong assumptions in the article before it was
spread to thousands of users world wide, and instead we could have had
a concise article which reflected the truth.

Instead I now face the possibility of being flamed in my inbox for "my
plans to remove xsupplicant from Gentoo Portage". I've already been
approached twice on IRC about these "plans"...

I suggest that in the future, all developers who are directly quoted
in the GWN are contacted prior to posting the quotes. I realize that
this will put a bit more work load on the GWN authors, but it should
be as simple as sending a mail with the relevant section quoted for
the developer to accept.

Regards,
Brix

[1]: http://www.gentoo.org/news/en/gwn/20051128-newsletter.xml
[2]: http://planet.gentoo.org/developers/brix/2005/11/25/wpa_supplicant_vs_xsupplicant
-- 
Henrik Brix Andersen <brix@gentoo.org>
Gentoo Metadistribution | Mobile computing herd

[-- Attachment #2: Type: application/pgp-signature, Size: 211 bytes --]

             reply	other threads:[~2005-11-28  9:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-28  9:48 Henrik Brix Andersen [this message]
2005-11-28 11:30 ` [gentoo-dev] Misquoted in the GWN Simon Stelling
2005-11-28 11:46   ` George Shapovalov
2005-11-28 11:54     ` Henrik Brix Andersen
2005-11-28 17:54 ` Ciaran McCreesh
2005-11-28 18:46   ` Patrick Lauer
2005-11-28 18:54     ` Ciaran McCreesh
2005-11-28 19:42       ` Grobian
2005-11-28 18:59     ` Lance Albertson
2005-11-28 19:00     ` Stephen P. Becker
2005-11-28 19:05     ` Jeroen Roovers
2005-11-28 19:19     ` Grant Goodyear
2005-11-29 13:03 ` [gentoo-dev] " Duncan

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=20051128094800.GA32340@dmz.brixandersen.dk \
    --to=brix@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gwn-feedback@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