From: Andrew Lunn <andrew.lunn@ascom.ch>
To: Jonathan Larmour <jifl@ecoscentric.com>
Cc: ecos-maintainers@sources.redhat.com
Subject: Re: [gnu.org #25869] eCos as an FSF project?
Date: Fri, 11 Apr 2003 07:50:00 -0000 [thread overview]
Message-ID: <20030411075051.GQ20614@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <3E95FC5C.9070204@eCosCentric.com>
> I vote to go ahead with Red Hat, but if that fails, drop assignments
> but retain a disclaimer.
Agreed.
> Something else to think about is whether we should plough ahead with
> 2.0 final anyway, or wait till we hear from Red Hat, or at the very
> least wait for some time period for Red Hat. For "just" the
> documentation, they will hopefully be amenable to an accommodation -
> it's not like the FSF are an unknown quantity! Something to consider
> anyway, and it's obvious we can't wait with 2.0 going stale, so I
> suggest a drop dead date, which we wouldn't be real close anyway, as
> there are still some outstanding 2.0 issues.
Make the 2.0 release when its ready independent of what's going on
with FSF, assignment etc.
2.1 can be with the changes for FSF. Hopefully, when releases are
closer together there is much less work involved in making a release.
Andrew
next prev parent reply other threads:[~2003-04-11 7:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <rt-25869@gnu.org>
[not found] ` <rt-25869-69834.13.1459854406747@rt.gnu.org>
2003-03-28 19:57 ` FSF General Contact Address
2003-04-03 19:51 ` Jonathan Larmour
[not found] ` <rt-25869-73954.4.22037571649483@rt.gnu.org>
2003-04-10 22:08 ` FSF General Contact Address
2003-04-10 23:21 ` Jonathan Larmour
2003-04-11 7:50 ` Andrew Lunn [this message]
2003-04-11 12:02 ` Nick Garnett
2003-04-13 18:20 ` Bart Veer
2003-04-14 19:50 ` Jonathan Larmour
2003-05-19 22:20 FSF General Contact Address
2003-05-19 22:56 ` 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=20030411075051.GQ20614@biferten.ma.tech.ascom.ch \
--to=andrew.lunn@ascom.ch \
--cc=ecos-maintainers@sources.redhat.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).