public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew.lunn@ascom.ch>
To: Jonathan Larmour <jifl@ecoscentric.com>
Cc: Gary Thomas <gary@mlbassoc.com>,
	eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: FSF license?
Date: Thu, 02 Dec 2004 08:21:00 -0000	[thread overview]
Message-ID: <20041202082134.GP9303@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <41AE07B4.1070504@eCosCentric.com>

On Wed, Dec 01, 2004 at 06:04:36PM +0000, Jonathan Larmour wrote:
> Gary Thomas wrote:
> >Any news on this?  Any hopes that it will *ever* happen?
> >
> >We've been in a holding pattern for nearly a year...
> 
> I was thinking about this just last night. I propose that when it hits one 
> year in, ooo, 6 weeks, we send RH legal a warning that if it isn't resolved 
> ASAP we will issue a Press Release expressing our 
> dissatisfaction/disappointment etc. with Red Hat for breaking their promise.
> 
> And if they don't respond, indeed issue a Press Release, and send it to 
> lwn, slashdot, etc.etc. Perhaps even have it at the front of the ecos web 
> site.
> 
> It's time to force the issue. If we wait till Jan 13th the PR will be able 
> to be written for better effect.

How about sending the warning two weeks before the year is up letting
them know that on the anniversary the press release will be published.
I think its important to put a date to the threat so they at least
know when they have to do something by. A straight year seems better
than 1 year plus a couple of weeks.

     Andrew

  parent reply	other threads:[~2004-12-02  8:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-01 14:55 Gary Thomas
2004-12-01 18:04 ` Jonathan Larmour
2004-12-01 18:23   ` Gary Thomas
2004-12-02  8:21   ` Andrew Lunn [this message]
2004-12-02 14:28     ` Jonathan Larmour

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=20041202082134.GP9303@biferten.ma.tech.ascom.ch \
    --to=andrew.lunn@ascom.ch \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=gary@mlbassoc.com \
    --cc=jifl@ecoscentric.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).