public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: "eCos Disuss" <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Are copyright assignments detrimental to eCos?
Date: Fri, 28 Mar 2008 02:59:00 -0000	[thread overview]
Message-ID: <c09652430803271141v7c87f4b5y4f83503c41359607@mail.gmail.com> (raw)

I believe that a sluggish patch + commit process is detrimental to eCos.

Clearly copyright assignments slow things down.

Why copyright assignments at this point?

Is it an anachronism?

Why should *all* of eCos require copyright assignments?

What about other projects imported to eCos? Do they too have copyright
assignments in order? jffs2? zlib?

-- 
Øyvind Harboe
http://www.zylin.com - eCos ARM & FPGA developer kit

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2008-03-27 18:42 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28  2:59 Øyvind Harboe [this message]
2008-04-02 19:01 ` Jonathan Larmour
2008-04-03  9:38   ` Markus Schaber
     [not found]     ` <47F4A57F.1080501@gaisler.com>
2008-04-03 11:14       ` Jiri Gaisler
2008-04-03 18:49         ` Alexander Neundorf
     [not found]           ` <47F55A47.7070602@gaisler.com>
2008-04-03 22:40             ` Jiri Gaisler
2008-04-04  4:11               ` Alexander Neundorf
2008-04-04  9:02               ` Markus Schaber
     [not found]                 ` <47F5F130.2030800@gaisler.com>
2008-04-04  9:36                   ` Jiri Gaisler
     [not found]                     ` <20080404114231.7efcf59a@kingfisher.sec.intern.logix-tt.com>
     [not found]                       ` <47F5FC4A.2080401@gaisler.com>
2008-04-04 10:50                         ` Jiri Gaisler
2008-04-04 15:33                           ` Alex Schuilenburg
2008-04-04 16:09                             ` Markus Schaber
2008-04-04 16:13                               ` Markus Schaber
2008-04-04 16:25                                 ` Andrew Lunn
2008-04-04 16:26                                   ` Markus Schaber
2008-04-04 14:58                         ` Andrew Lunn
     [not found]                           ` <47F642D0.7000907@xylanta.com>
2008-04-04 15:17                             ` Andrew Lunn
2008-04-04 15:20                           ` Andy Jackson
2008-04-04 16:47                             ` Markus Schaber
2008-04-07  8:00                             ` Gary Thomas
     [not found]                           ` <47F6450C.4090302@gaisler.com>
2008-04-04 15:17                             ` Jiri Gaisler
2008-04-04 16:06                               ` Alex Schuilenburg
     [not found]                                 ` <47F65C78.5050005@gaisler.com>
2008-04-04 23:18                                   ` Jiri Gaisler
2008-04-05  0:44                                     ` Jonathan Larmour
2008-04-07 12:18                                     ` Alex Schuilenburg
     [not found]                                       ` <47FA1CE4.8090708@gaisler.com>
2008-04-07 13:17                                         ` Jiri Gaisler
2008-04-07 13:28                                           ` Gary Thomas
     [not found]                                             ` <47FA2438.4090904@gaisler.com>
2008-04-07 13:44                                               ` Jiri Gaisler
2008-04-07 15:51                                             ` Gregg Levine
2008-04-04 15:45                             ` Andrew Lunn
2008-04-04 10:00                   ` Chris Zimman
2008-04-04 15:09                     ` Andrew Lunn
2008-04-04 15:46                       ` Chris Zimman
2008-04-03 18:46     ` Bart Veer
2008-04-03 19:01   ` Alexander Neundorf

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=c09652430803271141v7c87f4b5y4f83503c41359607@mail.gmail.com \
    --to=oyvind.harboe@zylin.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).