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] |
On Mon, Mar 10, 2008 at 06:16:34PM +0530, Aditya Vaidya wrote:So the copyright assignment would only come into the picture for new code. That clears things up a lot. Thanks.
So for this port from Linux to ecos, is the FSF copyright assignment necessary or optional?
It is not even possible. You don't own the code so you cannot assign
it to FSF.
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?
I would make it an eCos package. ecosconfig will work with multiple
repositories. So if somebody wants to use the packet, they just need
to download your package from where ever and then set ECOS_REPOSITORY
appropriately.
The important thing here is that the code is stored somewhere separate with a big fat warning it is GPL, not mod GPL. 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] |