Re: Requesting Approval of Release notes general structure




Hi,

Claus Schwarm wrote:
 * psychology: people are more likely to remember what they see often.
If we keep the GNOME release notes structure stable for a few years,
people will learn the talking points: "every GNOME release improves
features, usability, performance, internationalization and
accessibility" -- the magic of repetition. Additionally, repeating the
"feature improvements" page works against myths spread about GNOME such
as: "Due to the usability stuff, GNOME has no features!"

This is an interesting way to look at it - I would have thought that if
we always have the same headline "features" - usability, performance,
i18n, a11y - don't we run the risk of exactly the opposite effect (same
old same old) rather than the desired one underlining our commitment to
those things?

Perhaps I'm misunderstanding your point here, because this seems to be
what you're saying yourself with the inverted pyramid point. I don't
think that what you did for 2.16 is incompatible with what Gervais
proposed, though. And I think it's reasonable to have a short section
describing GNOME to first-timers in every release notes.

Cheers,
Dave.

-- 
Dave Neary
GNOME Foundation member
bolsh gnome org



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]