Re: User oriented release notes

[Joachim Noreiko <jnoreiko yahoo com>]

--- Quim Gil <qgil desdeamericaconamor org> wrote:

> - Integrate marketing and ""business"" visions with
> the technical vision
> that is guiding the 2.18 release. Since day zero.

<snip> 

> Someone
> needs to think what these bodies need and how the
> next release is going
> to help them, be useful to them.

I think you're absolutely right.
But there is this perception that developers on Free
projects "work only on what they want to work on" and
"only on what's fun", and that therefore, for example,
you "can't demand that bug X be fixed"... I know this
is the sort of rhetoric you see on slashdot, and
therefore a little bit exaggerated.
But I do get a general feeling that developers resent
any outside intervention, whether that's by marketing,
documentation, or usability people.
This is bad for GNOME. Bugs don't get fixed, features
are developed in isolation without reference to the
rest of the dektop interface, and the big decisions
get deferred indefinitely.
 
> - Planning and production of the ""release notes""
> following the release
> cycle. We start deciding who are our audiences, what
> we want to give
> them, how we present the information to them. We
> don't need to wait a
> feature freeze to go ahead with this. 

The same way that I want to be able to start writing
documention for new features before freeze... ;)


                
___________________________________________________________ 
To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. 
http://uk.security.yahoo.com