public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Wernfried Haas <amne@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] July Council Meeting: Requested Agenda Item
Date: Sat, 10 Jun 2006 09:27:31 +0200	[thread overview]
Message-ID: <20060610072731.GA16323@superlupo.rechner> (raw)
In-Reply-To: <1149906516.4234.91.camel@gaspode>

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

On Sat, Jun 10, 2006 at 04:28:36AM +0100, Christel Dahlskjaer wrote:
> I would like to ask that the Council discuss the current state and
> future of the GWN at their next meeting.

Council? Why escalate things? Have you talked to Ulrich about the
problems mentioned below? Isn't the GWN somehow a userrel issue? ;-)

> 1. Reliability. The GWN claims to be a weekly publication, yet it
> frequently fails to publish without prior warning. There was no edition
> this week, and Patrick Lauer says that it is "unknown" whether there
> will be an edition next week as Ulrich Plate is AWOL.

I agree there are problems due to Ulrich being awol every now and
then, but what can the council do about it? Fire him so the GWN is
unmaintained? ;-)

> 2. Permissions. Although it could be considered flattering that the GWN
> should choose a developer's blog as inspiration for an article, they
> should ensure that they have the developer / author's permission before
> quoting them (see previous complaints by brix, ciaranm and others).

Why? What makes blog posts different to mailing list/forum threads,
new versions being released etc? Do you want to ask people for
permission then, too?

> I also believe that when posting an article or interview, a copy should
> be sent to the relevant people to ensure that they are ok with what is
> being posted (my dev of the week interview, for example, was rather
> screwed up and misrepresentative). When someone contacts GWN to have
> something corrected, it would be appreciated were the GWN staff to at
> least deign to acknowledge receipt, even if for some reason they choose
> not to honour the corrections or post a retraction (although refusing to
> publish corrections is extremely insulting to those wronged).

Considering Ulrich is appearently still/again awol, could that be the
reason? I have requested small fixes (like wrong email addresses in
stuff i submitted) every now and than and got what i asked for.

> 3. Misinformation, misquotations and outright fabrications. Sure,
> there's freedom of the press, but that shouldn't be used as an excuse
> for deliberately making up quotes and printing intentional
> misinformation.

Huh? Can you back that statement up?

> From a PR perspective, Gentoo could benefit greatly by better
> utilisation of the GWN. I believe that as it stands, however, the GWN is
> discouraging people from contributing and damaging Gentoo's credibility.

I have submitted a bunch of articles to the GWN, and it has always
worked fine for me. Yes, Ulrich is awol at times and sometimes there
are smaller corrections to make in the final article, but i never felt
discouraged to submit my stuff. Worst case it takes a few extra days
to get published.

> Another thing that concerns me is the way the articles are written. It
> is blatanly obvious that the GWN writers are not native English speakers
> as both the grammar and the flow of the articles is far from attractive.
> Having read through the archives, I notice that there was once a time
> when the GWN was a great publication, and I would like to think that it
> could become great yet again; in its current state, though, it is doing
> more harm than good.

I disagree. GWN could use some more manpower to improve this and that,
but i don't see the harm - at least i could easily come up with lots
of stuff happening that does more harm (Not pointing my finger at
anyone and leaving it up to everyone's imagination to think of
something that does damage Gentoo in a terrible way).

> Lack of content and poorly written or incorrect articles are often
> justified by the GWN team on grounds of overwork and insufficient
> manpower. When I asked why they were not recruiting, I was informed that
> no-one has any interest in contributing. Upon speaking with others,
> however, I find that this is not the case -- people are interested, but
> fear (and rightly so) that their work will be edited in such a way that
> it is no longer something with which they want to be associated.

I'm sure a solution can be found to that problem - actually Ulrich is
quite a nice guy to talk to, so if those people came out of hiding
those problems may be solved by talking.

> Another complaint is that the GWN rejects any writing style which has
> any degree of character or levity. Any attempt at dececnt writing (the
> kind that would make it into publication in English newspapers or
> magazines, for example), is met with the claim that "the GWN is not a
> humorous publication".

http://www.gentoo.org/news/en/gwn/20060522-newsletter.xml#doc_chap3
Look at the picture and tell me it's not at least a tiny bit
humorous. Agreed, the joke is a bit obvious.

> I would like to see discussion about the way the GWN is
> (mis)representing Gentoo, how we can better actualise its full potential
> and what can be done to address the concerns listed above. 

I'm still not sure why the council should discuss the issue in the
first place, i think everyone agrees that the GWN is a bit
understaffed (for whatever reason) and some stuff doesn't work too
well. So i assume helping out with the GWN and helping those who fear
it for some reason may be the best way to solve these problems.

cheers,
	Wernfried

-- 
Wernfried Haas (amne) - amne at gentoo dot org
Gentoo Forums: http://forums.gentoo.org
IRC: #gentoo-forums on freenode - email: forum-mods at gentoo dot org

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

  reply	other threads:[~2006-06-10  7:34 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-10  2:28 [gentoo-dev] July Council Meeting: Requested Agenda Item Christel Dahlskjaer
2006-06-10  7:27 ` Wernfried Haas [this message]
2006-06-10 12:13   ` Christel Dahlskjaer
2006-06-11 23:08     ` Henrik Brix Andersen
2006-06-12  3:16       ` Donnie Berkholz
2006-06-12  3:31         ` Alec Warner
2006-06-10  7:35 ` Tobias Scherbaum
2006-06-10 12:19   ` Christel Dahlskjaer
2006-06-10  8:07 ` Lars Weiler
2006-06-10 12:26   ` Christel Dahlskjaer
2006-06-10  8:27 ` George Shapovalov
2006-06-10 11:06   ` Luis Francisco Araujo
2006-06-10 12:34   ` Christel Dahlskjaer
2006-06-10  8:56 ` Patrick Lauer
2006-06-10 12:44   ` Christel Dahlskjaer
2006-06-10 14:42   ` Ciaran McCreesh
2006-06-15  5:30     ` Mike Frysinger
2006-06-10 15:37   ` Alec Warner
2006-06-10 23:00     ` Patrick Lauer
2006-06-11  0:23       ` Marius Mauch
2006-06-11 10:55         ` Josh Saddler
2006-06-11 10:29     ` Henrik Brix Andersen
2006-06-10 10:40 ` Daniel Drake
2006-06-10 22:59   ` Ciaran McCreesh
2006-06-11  0:21   ` Christel Dahlskjaer
  -- strict thread matches above, loose matches on Subject: below --
2006-06-11 15:50 Christel Dahlskjaer
2006-06-11 18:17 ` Wernfried Haas
2006-06-11 15:50 Christel Dahlskjaer
2006-06-11 15:51 Christel Dahlskjaer

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=20060610072731.GA16323@superlupo.rechner \
    --to=amne@gentoo.org \
    --cc=gentoo-dev@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