public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: harri.siirtola@vtt.fi
Cc: ecos-discuss@sources.redhat.com, carl@openfuel.com
Subject: Re: [ECOS] Porting ecos on at91 eb01 board
Date: Thu, 05 Jul 2001 08:57:00 -0000	[thread overview]
Message-ID: <3B448E6F.C3AA43CC@redhat.com> (raw)
In-Reply-To: <3.0.32.20010705104355.009f87a0@vttmail.vtt.fi>

harri.siirtola@vtt.fi wrote:
> -------------------------------------------------------------------------
> harri.siirtola@vtt.fi wrote:
> >
> > At 19:56 4.7.2001 +0100, Jonathan Larmour wrote:
> > >With Carl's permission we could bring Carl's eCos tree tarball onto the
> > >eCos site and update it with your changes.
> > >
> > >If you would be interested, perhaps if Carl and yourself could provide a
> > >copyright assignment (assuming Carl does own all the copyright on it),
> > >would you be willing to bring this port up to scratch so it could be
> > >included in the main eCos sources? I'm sure a lot of folks would be pleased
> > >if it was, it seems quite in demand on the list.
> >
> > I'm ready to give it without any copyright hassle. For such a simple port
> > (and probably not complete), I don't want to make things too complicated.
> > Let me know what Carl thinks, my port is based on his code anyway.
> >
> > >Jifl
> >
> >         Harri
> 
> Sorry, I've been out of touch for a while.
> You guys have my full permission to release the code and do practically
> what you like with it :-)

If you are stating that you're putting the files into the public domain,
that would avoid the assignment itself. But when I talked about the
assignment, I was also including the "disclaimer" part which has to be
signed by your employer. This is needed because most people's contracts in
the software industry say that all intellectual property belongs to the
employer. This is even true of universities. So we'd really need that at
least from both of you.

We can still put together a tarball that is distributed separately, but it
wouldn't be able to go in the eCos sources properly meaning it may be
subject to bitrot.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions    http://www.redhat-techworld.com/

  reply	other threads:[~2001-07-05  8:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-05  0:46 harri.siirtola
2001-07-05  8:57 ` Jonathan Larmour [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-05 23:23 harri.siirtola
2001-07-06 11:35 ` Jonathan Larmour
2001-07-05  0:02 harri.siirtola
2001-07-04  2:59 harri.siirtola
2001-07-04 11:56 ` Jonathan Larmour
2001-07-04  2:27 eric mini

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=3B448E6F.C3AA43CC@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=carl@openfuel.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=harri.siirtola@vtt.fi \
    /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).