Fwd: Re: X.Org Foundation - Conference Call Minutes - 1st April 2004

mark kandianis <[email protected]>
Newsgroups gmane.comp.xfree86.forum
Message-ID <[email protected]>
>Resent-Date: 4 Apr 2004 20:46:44 -0000
>Date: Sun, 4 Apr 2004 22:13:41 +0200
>From: Egbert Eich <[email protected]>
>To: [email protected]
>Cc: Alan Coopersmith <[email protected]>
>Subject: Re: X.Org Foundation - Conference Call Minutes - 1st April 2004
>X-Mailer: VM 7.17 under Emacs 21.2.1
>X-Spam-Status: No, hits=-4.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
>version=2.63
>Resent-To: [email protected]
>Resent-From: [email protected]
>Reply-To: [email protected]
>X-Mailing-List: xorg_foundation:archive/latest/366
>X-Loop: [email protected]
>Resent-Sender: [email protected]
>
>Mark W. Snitily writes:
>  > Alan Coopersmith wrote:
>  > I can't agree with your comments more!  We (i.e. the old X.Org)
>  > spent a lot of time and money having Metro Link (i.e. a lot of
>  > _my_ time and others at Metro Link) work as an X.Org contractor
>  > to provide bug fixes and enhancements simultaneously to both the
>  > then current X11R6.6 SI and the then current XFree86 4.x source
>  > tree.  In a way this really was a merger and hence, the new
>  > X.Org source tree builds/improves upon both the old SI and
>  > XFree86.  I would consider this to be a very important point.
>  >
>
>We should keep the facts straight here. The 6.6 merger was done
>by XFree86 well before 4.3 came out. About anything from the
>sample implementation that was done after 6.6 and hasn't been
>part of XFree86 already has been reverted before the release
>as it introduced unjustifiable backward incompatibilities.
>
>The differences to XFree86 that can be attributred to X.Org
>are mainly IPv6 fixes, and documentation updates, however
>they where created after the SI was closed.
>Therefore, yes we should mention those changes, but we should
>keep the facts straight, and not claim that we are releasing
>a pile of earthshaking new stuff.
>Honesty will hpeofully pay off and we should be able to explain
>to the press why we are not shipping the 'code which will X
>win on the desktop' now.
>
>Egbert.
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.