This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Procedure to release GPL code for eCos


So for this port from Linux to ecos, is the FSF copyright assignment necessary or optional?

Right now, all we have is some "hello world" and basic test applications. No real world stuff. So no issues with releasing those either.

Just one more thing. Should we make this ported code into a separate library that can be linked when making the final binary, or add it to libtarget.a?

Aditya

Jonathan Larmour wrote:
Aditya Vaidya wrote:
Well, unfortunately its only licensed under GPL; no dual license for
sure. So is there any way that the community would accept such code?

Not in our own source base currently. Even if we did consider having contributions like that, they would have to go into a separate repository so that people didn't accidentally use GPL stuff without realising the licence.

Even if it's not in the repository, say if we start a sourceforge
project or something like that to keep it going?

Sure, eCos is an open project so you are welcome to do so. We can put a link on our website if that helps.

And would there be any licensing issues for releasing such code? Is GPL
code even usable with eCos? Say I don't mind releasing all my code
including that of the application, at least the GPL code could be useful
for educational projects, if not commercial ones.

Sure, see my other mail.


Jifl

Andrew Lunn wrote:
On Mon, Mar 10, 2008 at 04:20:21PM +0530, Aditya Vaidya wrote:
So this would be the procedure to follow if we port some Linux code
to eCos, correct?
Upps. Sorry missed the GPL part.

We cannot accept plain GPL code into the eCos repository. Is the code
only available under GPL? Some parts of the kernel is dual licensed,
eg under MIT or BSD. We might consider such code.

Could you be more specific about what code we are talking about.

Also there was some talk about adding an option in the configtool to allow use of GPL code. Any further word on that?
Nope. There was talk about making a second tree for code which could
not be modified GPL, but it is just talk so far.

Sorry for the confusion,

Andrew





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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]