From: Jonathan Larmour <jifl@eCosCentric.com>
To: ecos-maintainers@sources.redhat.com
Subject: Re: [gnu.org #25869] eCos as an FSF project?
Date: Thu, 10 Apr 2003 23:21:00 -0000 [thread overview]
Message-ID: <3E95FC5C.9070204@eCosCentric.com> (raw)
In-Reply-To: <20030410214734.GH1904@gnu.org>
I don't think there are any problems with the FSF's response other than,
obviously, the documentation....
FSF General Contact Address wrote:
>
> Such non-free documentation would be problematic, yes.
So we can't even distribute the documentation with eCos even if it's not
assigned to the FSF. The documentation is unfortunately IMO too important
to lose. Most of it, including much of the RedBoot stuff, is pretty much
irreplaceable really.
> Red Hat disclaims all changes made by its employees to a number of GNU
> programs. We may approach them about doing the same for eCos if you all
> are dedicated to making it a GNU project, and may be able to deal with this
> problem by obtaining full copyright on the document and relicensing it.
It seems that approaching Red Hat is back on the agenda (again!).
I think we need a definite decision now on this before we try to get Red
Hat's permission to assign copyright or relicense the docs under the FDL.
If Red Hat don't oblige I believe we have consensus that the only feasible
alternative is dropping assignments (but retaining a disclaimer).
There probably isn't any sensible way to do this other than a vote, and
there are 7 of us so no worries about a tie... so is this categorically
what everyone agrees with? Please reply ASAP, as I'd like to get the ball
rolling with Red Hat ASAP. Vote on
ecos-maintainers-private[at]ecoscentric.com if you prefer.
I vote to go ahead with Red Hat, but if that fails, drop assignments but
retain a disclaimer.
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.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
next prev parent reply other threads:[~2003-04-10 23:21 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 [this message]
2003-04-11 7:50 ` Andrew Lunn
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=3E95FC5C.9070204@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-maintainers@sources.redhat.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).