Re: Join gtk-devel-list

Havoc Pennington <[email protected]> writes:
> Michael Meeks <[email protected]> writes: 
> > 	It would be _really_ good if we could try and keep people focused on
> > fixing Gnome 2.0, porting applications and getting it out of the door -
> > in my opinion. Encouraging people to work on software that is scheduled
> > for 6 months away, while the existing code base has serious bugs,
> > mis-features, incoherencies, lack of accessibility etc. etc. seems a
> > serious mistake.
> 
> I don't want to encourage anyone to do that; but there are people that
> hack on GTK only and not GNOME, and there are people who are just
> doing this already by themselves. So I do want to encourage everyone
> to keep an eye on gtk-devel-list.
> 
> I don't intend to work on new GTK API myself, except for the 2.2
> "emergency fixes" release.
> 

I should offer more reassurance: I'd be willing to bet Owen will be
too busy with 2.0.x and 2.2 for the next couple months to seriously
look at any big APIs, so I don't think any real decisions will be made
for a while. What's happening now is brainstorming and some people are
fooling with prototypes.

It's not so much that I think we're designing these things now;
rather, I think people are starting to think about them now, and if
people sort of keep one eye on the discussion, we'll all be closer to
the same page in a few months.

Here's what I would highlight in the archives, to save time for 
those without enough of it:

General 2.2/2.4/2.6 plans:
  http://mail.gnome.org/archives/gtk-devel-list/2002-March/msg00266.html

Menu thread:
  http://mail.gnome.org/archives/gtk-devel-list/2002-March/msg00516.html

Combo box:
  http://mail.gnome.org/archives/gtk-devel-list/2002-March/msg00457.html

File selector:
  http://mail.gnome.org/archives/gtk-devel-list/2002-March/msg00179.html


So, please don't panic or feel the need to write huge RFCs, but at the
same time I hope everyone will keep on eye on this stuff.

(The reason I posted my mail is that in the past people seemed really
surprised at certain things coming from GTK, and I think anyone
working on our devel platform simply _must_ scan gtk-devel-list for
relevant stuff, even if they skip the boring threads.)

Havoc