Re: A call to action

[Kevin Cullis <kevincu orci com>]

Gerry Chu wrote:
> 
> > > I think some core GNOME developer (eazel?) needs to organize the mailing
> > > list, the hitsquad, and developers to commit to a written down
> > process on
> > > how new ui designs for GNOME / GTK programs and widgets are going to be
> > > finalized into _release_ form.
> >
> > What sort of written down process do you have in mind? And does it
> > require that degree of formality? (I've no idea how the decision
> > making structure within GNOME works.)
> >
> > It shouldn't be too hard to make for each discussion a document
> > containing a description of our suggestions and then to present that
> > document to the appropriate people. However, we may require more
> > discussion with the developers than that would provide...
> 
> I think that whatever we do, we have to involve the maintainers and
> developers of the component itself, as no one likes to be told how their
> little piece of GNOME should look like.

Don't forget the LDP, Help Guides, and documentation people, they're the
ones also communicating with the users.

> 
> The idea was floating in my mind that a committee form, composed of people
> from the gui-list, gtk, eazel, and helixcode that can make a commitment to
> work on designing GNOME for a significant time period, and can back up their
> opinions with design principles.  The committee would start with current or

Absolutely yes!  A more formal design document is essential stating the
key principles of design and focus.

> hitsquad designs, and go around to the maintainers or the mailing list of
> the component being designed, and work something out.  So basically, the
> committee will say what GNOME will look like, and perhaps necessarily by
> extension, what the feature set for the next release will be.  We would have
> to get agreement from the developers and from semi-GNOME projects (like
> sawfish) to give the committee that responsibility.  I also understand Eazel
> is thinking about putting together a ui testing lab, so the committee could
> work with that too.  Finally, when the component is redesigned, it would be
> put up on the www or shown to the greater mailing list itself for comment.

Again, absolutely!

Kevin

begin:vcard 
n:Cullis;Kevin
tel;home:720-489-9283
x-mozilla-html:FALSE
adr:;;8285 S Poplar Way #202;Englewood;CO;80112;USA
version:2.1
email;internet:kevincu orci com
x-mozilla-cpt:;0
fn:Kevin Cullis
end:vcard