[kde-linux] Users guide to KDE?

[Kevin Krammer]

On Sunday 06 July 2008, Randy Kramer wrote:

> The burden in the first case is that the reader always has to remember, in
> the 2nd case a reminder is always in front of him.  (Agreed, he might not
> always read the reminder, but I'm hoping it will something that triggers
> before he (presumably, accidentally) starts any rumors.)

Hmm, right, but I think that such a disclaimer will just add to the noise with 
very little positive impact.

> I was thinking of it being a standard footer (or header) in all posts from
> the list.  Thus no one has to try to remember to include it.  When (if)
> there is a release announcement on the list, the announcer should make a
> point, something like, "contrary to the standard footer on this list, this
> is a release announcement (or plan, or whatever)".

Isn't that already implied by the name of the list?
Postings on kde-devel or kde-core-devel are IMHO obviously about development, 
postings on kde-announce are obviously announcements.

> > From my point of view this would be kind of backwards, especially since
> > the media (e.g. blog, mailinglist) already shows the difference to the
> > official press releases (on project's homepage or directly linked to from
> > there).
>
> Not sure I follow you here--are you saying that the media already knows
> that documents on the development discussion lists are not release
> announcements?

What I meant is that the form of publication or the way it is transported 
usually define the scope quite clearly.

A blog is usually a kind of public diary, a person's view of the world, what 
they are currently doing or what they think about things others are doing.

A thread on kde-devel is usually a question&answer session between an 
application developer and other application developers or even core 
developers.

A thread on kde-core-devel is usually a discussion of core developers on 
topics such as architecture, policies and roadmaps.

A text published directly on www.kde.org is usually an official statement of 
the project as a whole.

> Even if so, what about more casual readers of the development discussion
> lists?

Would still implicitly understand that postings there are discussions between 
developers, unless they are incapable of understanding the concept 
of "development discussion" and have subscribed to the wrong mailingslist 
based on this misconception.

Cheers,
Kevin

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-linux/attachments/20080706/76de85a8/attachment.sig>