public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew.lunn@ascom.ch>
To: Alex Schuilenburg <alexs@ecoscentric.com>
Cc: Jonathan Larmour <jifl@ecoscentric.com>,
	Andrew Lunn <andrew@lunn.ch>,
	eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: [ECOS] Status of eCos copyright assignments to the FSF?
Date: Sun, 02 Jan 2005 16:43:00 -0000	[thread overview]
Message-ID: <20050102164217.GB26889@donkey.ma.tech.ascom.ch> (raw)
In-Reply-To: <41D5D608.9030406@ecoscentric.com>

You raise a lot of points, which i will just address three.

> >>both Paul and I are happy to engage Red Hat legal once again to pursue 
> >>this matter with the maintainers blessing.

RedHat appears to be ignoring all emails from the maintainers. Why do
you think they will not ignore you as well? How are you different from
us? 

> >>Failing that, I suggest that you rather draft an open letter (sent 
> >>registered) 

I don't see the difference between a registered mail letter and an
email. We all use email every day. We know that if we don't receive a
bounce, its very likely it landed in the recipients inbox. All a
registered letter tells us it reached the receptionist on the front
desk. Either way, it just as easy to file into /dev/null. 

To me, the deliverary mechansim is not important. What is important is
to try to find out why RH policy is to forward everything to
/dev/null. 

> I can understand your frustrations, but you should not let them get in 
> the way of what you want to achieve nor let them alienate you from the 
> people you need support from.

What i find frustrating is not the time its taking, its the lack of
dialog. Why does RH simply not reply saying,

"We are working on it, it should be done any time soon",

or

"Sorry for the delay. We consider it a low priority task, and our
legal team was overloaded by that SCO thing... Hopefully we can get to
this sometime soon..."

The experiance from the last year is that all our attempts to start a
dialog by sending emails to various people does not work. So what we
need is some other way of kick starting the dialog. Maybe this comes
down to one of us actually phyically going and knocking on the door?

        Andrew

  parent reply	other threads:[~2005-01-02 16:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-28 19:07 FWD: " Andrew Lunn
2004-12-29  0:35 ` Alex Schuilenburg
2004-12-31  1:18   ` Jonathan Larmour
2004-12-31 22:43     ` Alex Schuilenburg
2005-01-02 16:10       ` Jonathan Larmour
2005-01-02 16:43       ` Andrew Lunn [this message]
2005-01-03 16:49         ` Alex Schuilenburg

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=20050102164217.GB26889@donkey.ma.tech.ascom.ch \
    --to=andrew.lunn@ascom.ch \
    --cc=alexs@ecoscentric.com \
    --cc=andrew@lunn.ch \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --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).