taskSavannah Administration - Tasks: task #7734, Submission of dyncall

 
 

task #7734: Submission of dyncall

Submitted by:  Tassilo Philipp <tphilipp>
Submitted on:  Sun 03 Feb 2008 12:30:09 PM UTC  
 
Should Start On:  Sun 03 Feb 2008 12:00:00 AM UTC Should be Finished on:  Wed 13 Feb 2008 12:00:00 AM UTC
Category:  Project Approval Priority:  5 - Normal
Status:  Done Privacy:  Public
Percent Complete:  0% Assigned to:  Sylvain Beucler <Beuc>
Open/Closed:  Closed Effort:  0.00

Add a New Comment (Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

( Jump to the original submission)

Tue 05 Feb 2008 09:11:47 AM UTC, comment #6: 

Sylvain,

I understand what you mean - but I really don't see no point in grepping through my 280 files and change the license text... my (the author's) intent is to release a free software library with a very unrestrictive license.
And yeah, if the FSF licensing team can prove that my license is invalid, please go on and do it.
Heck, the next time I release something it will be PD. ;)

Tassilo Philipp <tphilipp>
Mon 04 Feb 2008 10:09:47 PM UTC, comment #5: 

> IANAL, but you aren't one either.


... but I did take the time to discuss this with the FSF licensing team.

> In fact, the licence text in use is exactly the same the
> OpenBSD project uses for newer code. That would mean that this
> detail makes the new OpenBSD source non-free, too.


Authors' intent is important, and the Pine authors clearly showed an intent to make the license non-free. This, added to the latent ambiguity, is primarily what made it non-free.

> Sorry, but this is just a bit too ridiculous - I didn't write
> this library to have legal problems by releasing it freely and
> non-closed. Furthermore the license in use has far less
> restrictions than the GPL or LGPL...  And yeah, in order to
> avoid any kind of license problem I did even take 2 minutes to
> paste the license text into every single file in the release.
>
> I'm not out for blood, and I'm taking this seriously, but hey,
> I enjoy doing a free release, and I'm sure that if you find a
> lawyer that wants to find a problem in the ISC license, he will
> find one for
> sure... (e.g. http://bsd.slashdot.org/bsd/07/01/15/1757235.shtml)


Geez, we just suggested to add "/or" somewhere in your license because it caused troubles in the past..

Sylvain Beucler <Beuc>In charge of this item.
Mon 04 Feb 2008 09:28:53 PM UTC, comment #4: 

IANAL, but you aren't one either. In fact, the licence text in use is exactly the same the OpenBSD project uses for newer code. That would mean that this detail makes the new OpenBSD source non-free, too.
Sorry, but this is just a bit too ridiculous - I didn't write this library to have legal problems by releasing it freely and non-closed. Furthermore the license in use has far less restrictions than the GPL or LGPL...
And yeah, in order to avoid any kind of license problem I did even take 2 minutes to paste the license text into every single file in the release.

I'm not out for blood, and I'm taking this seriously, but hey, I enjoy doing a free release, and I'm sure that if you find a lawyer that wants to find a problem in the ISC license, he will find one for sure... (e.g. http://bsd.slashdot.org/bsd/07/01/15/1757235.shtml)

Tassilo Philipp <tphilipp>
Mon 04 Feb 2008 08:35:04 PM UTC, comment #3: 

Hi,

Can you tell us why that would be a problem?

After more research, the reason we ask is that the Pine program was distributed under a license which had this kind of wording, and their authors weirdly argued that this allowed to privately modify and distribute verbatim, but did not allow to distribute modified versions.
- Their position:
http://www.washington.edu/pine/faq/legal.html
- A Debian developer commenting on the issue:
http://people.debian.org/~terpstra/message/20021112.091356.2048f162.en.html This made the software non-free.

That why we'd appreciate you change "and" in "and/or" - not in order to mimic the ISC, but instead to avoid this possible license misinterpretation.

Regards.

Sylvain Beucler <Beuc>In charge of this item.
Sun 03 Feb 2008 01:25:50 PM UTC, comment #2: 

Sorry, I won't "clarify" the license part, because it says "modeled after the ISC license" and not "this is the ISC license".

Tassilo Philipp <tphilipp>
Sun 03 Feb 2008 12:51:46 PM UTC, comment #1: 

Hi,

I approved your project.

You'll receive a confirmation mail shortly.

Before uploading your code at Savannah, though, we'd appreciate if you clarified the license by substiting "and" with "and/or" in its first sentence, as highlighted in these pages:
http://en.wikipedia.org/wiki/ISC_licence
http://groups.google.com/group/comp.protocols.dns.bind/msg/e709d108c81e2ce3

Regards.

Sylvain Beucler <Beuc>In charge of this item.
Sun 03 Feb 2008 12:30:09 PM UTC, original submission:  

A new project has been registered at Savannah
This project account will remain inactive until a site admin approves or discards the registration.

Registration Administration

While this item will be useful to track the registration process, approving or discarding the registration must be done using the specific Group Administration page, accessible only to site administrators, effectively logged as site administrators (superuser):

Registration Details

  • Name: dyncall
  • System Name:  dyncall
  • Type: non-GNU software & documentation
  • License: Modified BSD License (The license in use is modeled after the ISC license.)

Description:

The dyncall library encapsulates architecture-, OS- and compiler-specific function call semantics in a virtual "bind argument parameters from left to right and then call" interface allowing programmers to call C functions in a completely dynamic manner. In other words, instead of calling a function directly, the dyncall library provides a mechanism to push the function parameters manually and to issue the (foreign function) call afterwards.
This means, that a program can determine at runtime what function to call, and what parameters to pass to it. The library is written in C and assembly and provides a very simple C interface to program against.

Tarball URL:

http://www.dyncall.org/r0.1/dyncall-0.1.tar.gz

Tassilo Philipp <tphilipp>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by Beuc (Posted a comment)
  • -email is unavailable- added by tphilipp (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

     

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2008-02-03 Beuc StatusNone => Done
        Assigned toNone => Beuc
        Open/ClosedOpen => Closed

    Back to the top


    Powered by Savane 3.5