public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: Daniel Stone <daniel@fooishbar.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Keith Packard <keithp@keithp.com>
Cc: xorg@lists.freedesktop.org
Subject: Re: State of Linux graphics
Date: Wed, 31 Aug 2005 01:23:35 -0400	[thread overview]
Message-ID: <9e473391050830222371dd4f10@mail.gmail.com> (raw)
In-Reply-To: <1125464500.8730.68.camel@localhost.localdomain>

Before you shut my account off I made you this offer:

On 8/31/05, Jon Smirl <jonsmirl@gmail.com> wrote:
> Quit being a pain and write a response to the article if you don't
> like it. Censorship is not the answer. Open debate in a public format
> is the correct response. If you want me to I'll add your reponse to
> the end of the article.

I will still include your response if you want to write one.

On 8/31/05, Daniel Stone <daniel@fooishbar.org> wrote:
> On Wed, 2005-08-31 at 00:50 -0400, Jon Smirl wrote:
> > On 8/30/05, Daniel Stone <daniel@fooishbar.org> wrote:
> > > 'As a whole, the X.org community barely has enough resources to build a
> > > single server. Splitting these resources over many paths only results in
> > > piles of half finished projects. I know developers prefer working on
> > > whatever interests them, but given the resources available to X.org,
> > > this approach will not yield a new server or even a fully-competitive
> > > desktop based on the old server in the near term. Maybe it is time for
> > > X.org to work out a roadmap for all to follow.'
> > >
> > > You lose.
> >
> > Daniel Stone, the administrator of freedesk.org, has just taken it
> > upon himself to censor my article on the state of the X server. His
> > lame excuse is that I have stopped working the core of Xegl. It
> > doesn't seem to matter that I contributed 1,000s of lines of code to
> > fd.o that I am continuing to do maintenance on. So much for this being
> > a free desktop.
> 
> Sigh.  As I explained in the long thread we had in private mail, I have
> done several cleanups now on inactive accounts and projects.  You are
> absolutely not the first, and will not be the last.  I have not done
> such sweeps for a while, because I have not had time.  The realisation
> that your account was doing nothing other than hosting an HTML page now
> that I have some amount of time to look at fd.o again was enough to spur
> me to start a cleanup, and indeed, I am in the process of pinging many
> other dormant contributors; many of which have merely stopped working on
> X and may return, rather than having posted long statements of
> resignation to the list.
> 
> And, as I explained, a simple statement of intent from you that you
> intend to resume active development will be enough to justify your
> account being renewed.
> 
> (Alternately, if another administrator re-enables your account, I will
> not stop this.  I'm not the sole admin, not by far ...)
> 
> Possibly impolitic and bad timing, sure.  But my intent was not to
> censor.
> 
> > Can some else provide a place for me to host the article?
> 
> Is the wiki insufficient?  It is currently hosting such insignificant
> articles as the 6.9/7.0 release plan, f.e. ...
> 
> 


-- 
Jon Smirl
jonsmirl@gmail.com

  parent reply	other threads:[~2005-08-31  5:23 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30 16:03 State of Linux graphics Jon Smirl
2005-08-30 17:26 ` David Reveman
2005-08-30 18:13   ` Jon Smirl
2005-08-30 22:38   ` Dave Airlie
2005-08-31  6:33   ` Allen Akin
2005-08-31  8:11     ` Anshuman Gholap
2005-08-31 17:20     ` David Reveman
2005-08-31 17:48     ` Jim Gettys
2005-08-31 18:23       ` Jon Smirl
2005-08-31 19:06       ` Allen Akin
2005-08-31 19:14         ` Jim Gettys
2005-08-31 18:29     ` Keith Packard
2005-08-31 20:06       ` Allen Akin
2005-08-31 20:20         ` Ian Romanick
2005-09-01  1:04           ` James Cloos
2005-08-31 21:06         ` Keith Packard
2005-09-01  1:58           ` Allen Akin
2005-09-01  3:11             ` Ian Romanick
2005-09-01  6:00               ` Antonio Vargas
2005-09-01 10:20                 ` Alan Cox
2005-09-01 13:57                   ` Antonio Vargas
2005-09-01  6:11               ` Allen Akin
2005-09-01  3:59             ` Keith Packard
2005-09-01 15:24               ` Brian Paul
2005-09-01 15:59                 ` Jim Gettys
2005-09-01 16:39                   ` Andreas Hauser
2005-09-01 20:18                     ` Jim Gettys
2005-09-01 20:38                       ` Jon Smirl
2005-09-01 21:29                         ` Sean
2005-09-01 16:09                 ` Alan Cox
2005-09-01 16:04                   ` Brian Paul
2005-09-01 17:21                     ` Ian Romanick
2005-09-01 17:26                       ` Keith Whitwell
2005-09-01 20:03               ` Allen Akin
2005-08-31  3:11 ` Daniel Stone
2005-08-31  4:29   ` Jon Smirl
2005-08-31  4:50   ` Jon Smirl
     [not found]     ` <1125464500.8730.68.camel@localhost.localdomain>
2005-08-31  5:17       ` Jon Smirl
2005-08-31  5:23       ` Jon Smirl [this message]
2005-08-31  5:40         ` Jon Smirl
2005-08-31  6:15 ` Eric Anholt
2005-08-31 13:38   ` Jon Smirl
  -- strict thread matches above, loose matches on Subject: below --
2005-09-02  2:44 rep stsb
2005-09-03  4:00 mcartoaje

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9e473391050830222371dd4f10@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=daniel@fooishbar.org \
    --cc=keithp@keithp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xorg@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox