This is the mail archive of the ecos-patches@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: Please advice w.r.t. language/tcl


Øyvind Harboe wrote:
> 
> I took over as a maintainer after the original authors. I'd say the
> chance is slim.
> There is no manpower to hunt everybody down who contributed.

Ugh. Yes, strictly it needs permission from all Jim copyright holders -
anyone who has contributed meaningful (i.e. copyrightable) changes. Would
it help to know that people who contribute small changes and fixes do not
need to be consulted? There has to be something amounting to a
copyrightable "work" for copyright to be relevant.

> Jim Tcl has an eCos repository in it's official CVS server. I haven't tried, but
> it should be possible to delete Jim Tcl from eCos and add the Jim Tcl
> eCos repository
> to ECOS_REPOSITORY.

That hack does not work for configtool users, so it's not a great solution.
I'm sure you or I would be fine, but quite a lot of people use the
configtool in fact. It may be the least worst option though.

> Jim Tcl for athttpd is optional, so only anyone using
> Jim Tcl for athttpd, would need to add Jim Tcl to ECOS_REPOSITORY.
> 
> I don't know if ecosconfig would protest against the unused missing Jim Tcl
> module, but hopefully it would only produce an error if Jim Tcl was
> actually in use.

The relevant CDL in ATHTTPD can be made "active_if CYGPKG_JIMTCL".

> Jim Tcl, like jffs2, is used for non-eCos stuff so it needs a
> diffferent home than
> the eCos repository. ahttpd on the other hand is only for eCos.

Sure.

>>> http://cvs.berlios.de/cgi-bin/viewcvs.cgi/*checkout*/jim/jim/ChangeLog?rev=HEAD&content-type=text/plain
>>>
>>>
>>> What's the best way forward here?
>> The policy has been before that (assuming a compatible licence!) we will
>> tolerate stuff from existing established open source projects, and as long
>> as they are self-contained. Apart from the licence issue above, Jim would
>> fit that. But any changes to Jim to port to eCos should be assigned to the
>> FSF as they are specific to eCos - the rationale being the same as for
>> assignments in general.
> 
> I & Anthony wrote those. They amount to .cdl files + docs + two three #if's.

Anthony is certainly ok, and we need to get you sorted out......

>> Which reminds me Øyvind, where have things got to in your assignment
>> process? I believe you started on it a while back, so if there's anything
>> you want me to chase with the FSF, let me know and I can do some prodding.
>> You can mail me off-list if so.
> 
> I filed off a copyright assignment years ago. Got word years ago
> that it was in order and haven't heard anything since.

You filed a copyright assignment with Red Hat. One was not filed with
eCosCentric, nor the FSF. A Red Hat assignment is no use for recent work.
This was as announced here:
http://ecos.sourceware.org/ml/ecos-discuss/2005-01/msg00317.html

Has stuff written by you since 2005-01-14 been checked in? If so, that's
unfortunate. But as long as we get this sorted soon, we don't need to worry
about reverting stuff. Either way, you'll need to start the assignment
process off.

To request an assignment form, please fill in the form at
http://cvs.savannah.gnu.org/viewvc/gnulib/doc/Copyright/request-assign.future?revision=1&root=gnulib
and e-mail it to <assign@gnu.org>. Be sure to complete the list of changed
files - that's what assigns your existing changes.

Jifl
-- 
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------       Opinions==mine


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