public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@jifvik.org>
To: Tony Moretto <tmoretto@redhat.com>,
	Mark Webbink <mwebbink@redhat.com>,
	Michael Tiemann <tiemann@redhat.com>,
	ebachalo <ebachalo@redhat.com>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: eCos licence
Date: Tue, 06 May 2003 15:24:00 -0000	[thread overview]
Message-ID: <3EB7D38E.5000804@jifvik.org> (raw)
In-Reply-To: <3E9B297A.40607@jifvik.org>

Hi guys,

I'm just wondering if any of you have had a chance to look at the below 
message? It only takes the right person to say "yes" for it to happen :-).

I've also added Eric B in the hope that maybe he's the right person? Sorry 
for the wide posting, but I'd just like to get this sorted one way or the 
other.

Jifl

Jonathan Larmour wrote:
> Hi all,
> 
> I'd like to ask you for some help.... us eCos guys have now decided that 
> it's probably best for everyone in the community if eCos becomes a GNU 
> project. We have approached the FSF, and they are willing to do this. 
> This is a very positive move for eCos as I hope you'd all agree.
> 
> However we have one stumbling block which we need Red Hat's help with: 
> the current eCos documentation is licenced under the Open Publication 
> Licence <http://www.opencontent.org/openpub/> (along with the OPL option 
> "B" that prohibits publication in paper form without the copyright 
> holder's permission). The current documentation is a mixture of stuff 
> that is copyrighted by individual eCos maintainers, which we can deal 
> with no problem, but also copyright Red Hat.
> 
> Unfortunately the FSF do not find this documentation licence acceptable, 
> and so we would be very grateful if Red Hat could do one of two things: 
> either declare that RH is willing to licence it under the Free 
> Documentation Licence <http://www.fsf.org/copyleft/fdl.html>, or, even 
> better, assign copyright for the documentation to the FSF. Obviously 
> assigning to the FSF is something Red Hat is pretty familiar with! But 
> either option is fine.
> 
> As I'm sure you agree, right now there's no real value to Red Hat in the 
> current documentation licence as it now includes work by others, and so 
> Red Hat would now be bound by the same OPL restrictions too!
> 
> So we'd be grateful if you could help with this. Removing this stumbling 
> block would mean that eCos and RedBoot both have a secure and bright 
> future with the FSF.
> 
> Thanks in advance!
> 
> Jifl


-- 
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine

      reply	other threads:[~2003-05-06 15:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-14 21:34 Jonathan Larmour
2003-05-06 15:24 ` Jonathan Larmour [this message]

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=3EB7D38E.5000804@jifvik.org \
    --to=jifl@jifvik.org \
    --cc=ebachalo@redhat.com \
    --cc=ecos-maintainers@sources.redhat.com \
    --cc=mwebbink@redhat.com \
    --cc=tiemann@redhat.com \
    --cc=tmoretto@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).