Re: communication

Alan Hourihane <[email protected]>
Newsgroups gmane.comp.xfree86.forum
Message-ID <[email protected]>
On Sat, Mar 22, 2003 at 08:44:37PM -0500, Havoc Pennington wrote:
> On Sun, Mar 23, 2003 at 01:24:29AM +0000, Alan Hourihane wrote: 
> > I've seen praise for Keith from the KDE and Gnome teams for the work
> > he's done to enhance the desktop, yet these projects bring with them
> > the belief that XFree86 is not listening to them. It strikes me as though
> > Keith is the one injecting these projects with that belief.
> 
> As a single desktop developer, I don't personally feel that XFree86
> doesn't listen - there are tons of features in 4.3 that we wanted to
> see, and they were done well. No complaints on that. However, as you
> say:
  
Havoc - thanks for saying that you have no complaints!

> > It's bizarre. In this situation of Keith being THE person representing
> > this specific communication channel - and he's not managed it at all well.
> 
> Which seems to say that Keith was the only one interested in the
> desktop. And indeed, many of the desktop-related features (fontconfig,
> Xft, cursors, randr, etc.) are coming from Keith.
> 
> So speaking for myself only, I am worried about the *future*, not
> necessarily the past. Who will be the new person representing this
> communication channel, if not Keith? Are other XFree86 developers
> interested?

Getting back to the idea of an XFree86 developer. Anyone can be one.
And just because people on the Core Team have the CVS access privilege
doesn't mean to say that an XFree86 developer can't discuss or submit
new work to XFree86 to be included via the patch submission mechanism. 

There's nothing stopping Keith continuing to do what he does and submit
patches to XFree86. He's has every opportunity to do this. In fact, doing
it this way may well spark more discussion rather than having things
directly committed by Keith. 

Alan.

Alan.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.