From: Jonathan Larmour <jifl@eCosCentric.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: Way forward with FSF
Date: Fri, 31 Oct 2003 11:15:00 -0000 [thread overview]
Message-ID: <3FA2446B.5060702@eCosCentric.com> (raw)
In-Reply-To: <1344.62.166.230.82.1067589561.squirrel@www.chez-thomas.org>
Gary Thomas wrote:
> Since there doesn't seem to be any timetable for the FSF to move, I think
> it behooves us to go ahead with this plan(*). I am OK with eCosCentric being
> the center point (I'm like Andrew and don't have the inclination or resources
> to take this on).
Great. I'll give Mark a little more time to chime in, but otherwise it
looks pretty promising.
> (*) Right now, I think the community thinks of this as a major stumble and
> that our current approach of waiting for the FSF is growing stale. At least
> this way, it'll look like we are interested in the integrity of the codebase
> while still accepting new work (and the RH assignment is surely an impediment
> for some contributors). When this is announced, it must be made very clear
> that it is an interim solution, chosen only to keep the project/codebase
> alive while waiting for the FSF.
Absolutely. And the instant the FSF wakes up and we reach agreement,
everything would get transferred, no delays, ifs or buts.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
next prev parent reply other threads:[~2003-10-31 11:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 17:22 Jonathan Larmour
2003-10-30 18:54 ` Andrew Lunn
2003-10-30 19:48 ` Jonathan Larmour
2003-10-31 10:43 ` Andrew Lunn
2003-10-31 11:07 ` Jonathan Larmour
2003-10-31 8:39 ` Gary Thomas
2003-10-31 11:15 ` Jonathan Larmour [this message]
2003-10-31 10:36 ` Andrew Lunn
2003-10-31 11:04 ` 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=3FA2446B.5060702@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=gary@mlbassoc.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).