taskSavannah Administration - Tasks: task #7641, Submission of Night Light IRC...

 
 

task #7641: Submission of Night Light IRC Proxy/Bouncer

Submitter:  Jonas Kvinge <jonaster>
Submitted:  Sun 06 Jan 2008 02:56:50 PM UTC
   
 
Should Start On:  Sat 05 Jan 2008 11:00:00 PM UTC Should be Finished on:  Tue 15 Jan 2008 11:00:00 PM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Cancelled Privacy:  Public
Assigned to:  Beuc Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Mon 28 Jan 2008 09:06:05 AM UTC, comment #8: 

Hi,

Can you resubmit your project?
The current submission is cancelled and cannot be used to activate a project anymore.

Sylvain Beucler <Beuc>
Sat 26 Jan 2008 01:53:10 PM UTC, comment #7: 

I have upgraded to GPLv3 and made changes to the license in each file. You can look at it at:

http://ircproxy.svn.sourceforge.net/viewvc/ircproxy/trunk/

Jonas Kvinge <jonaster>
Sun 20 Jan 2008 04:06:24 PM UTC, comment #6: 

Hi,

"As long as I want to use openssl in my project I should pick another license? Will LGPL be okay?"

This much depends on your application. If you use the LGPL, or an exception to the GNU GPL (see http://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs), you can use openssl, but at the same time you cannot use GPL'd code and GPL'd libraries anymore, because those remain incompatible with openssl and cannot be linked with it, even indirectly.

Sylvain Beucler <Beuc>
Sun 20 Jan 2008 03:46:39 PM UTC, comment #5: 

As long as I want to use openssl in my project I should pick another license? Will LGPL be okay?

Jonas Kvinge <jonaster>
Fri 11 Jan 2008 10:17:45 PM UTC, comment #4: 

Hi,

"I am not sure what you mean by project development should happen primarily on Savannah. With project development do you mean submitting new releases and communicating with other developers?"

I mean that if Savannah is just a mirror (for code or downloads), we won't host the project.

"Right now you can run ./configure --disable-ssl and it will build without SSL support, the openssl is not required then.  With the --disable-ssl it does not look for the openssl library at all. Is it sufficient if I make SSL support disabled by default so that you have to run ./configure --enable-ssl to make it compile with SSL support?"

This is not a compile-time issue, this is a source issue directly. The GPL'd source code that depends on incompatibly-licensed legally cannot be redistributed without violating your license (the GPL).

"I learned how to use openssl by myself and it took me quite a while but if gnuTLS is very similar I don't see any problem making it work. Another question then is, if I make it work with both openssl and gnuTLS, can it still use the openssl library if it is found on the system and gnuTLS is not found on the system?"

If your code works with GnuTLS and if exactly that same code "happens to work" with OpenSSL, there's no problem in the source code - but this will still be a problem for binaries, because you link compiled GPL'd code with compiled GPL-incompatible code.


"Which files are considered non-free? Is it configure.in and Makefile.in ? Is it sufficient to just remove the "All rights reserved" line and only keep the Copyright? Or must I add the GNU license note to those files as well?"

When you don't write anything after a copyright notice, it's the same as "All rights reserved", which means you don't give any right to the end user - no copy, no modification, etc.

If the file is trivial (rule of thumb: < 10 lines), then the file is considered not copyrightable, and no notice is necessary.

In all other cases, you need to add a copyright notice and a license header.

See also this page:
http://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html#License-Notices-for-Other-Files
for a short all-permissive copyright notice that may be used for short files.


"Currently I'm moving from my apartment and will have limited access to the internet in the next weeks and limited time to do a new release. I will do a new release as soon as I am established at my new place, or before if I get the time."


I'm closing the submission for now, please feel free to resubmit as soon as you have the time for it.

Feel free to ask if you have more questions.

Regards.

Sylvain Beucler <Beuc>
Wed 09 Jan 2008 12:12:29 AM UTC, comment #3: 

I am not sure what you mean by project development should happen primarily on Savannah. With project development do you mean submitting new releases and communicating with other developers?

Jonas Kvinge <jonaster>
Wed 09 Jan 2008 12:06:00 AM UTC, comment #2: 

Right now you can run ./configure --disable-ssl and it will build without SSL support, the openssl is not required then. With the --disable-ssl it does not look for the openssl library at all. Is it sufficient if I make SSL support disabled by default so that you have to run ./configure --enable-ssl to make it compile with SSL support? I learned how to use openssl by myself and it took me quite a while but if gnuTLS is very similar I don't see any problem making it work. Another question then is, if I make it work with both openssl and gnuTLS, can it still use the openssl library if it is found on the system and gnuTLS is not found on the system?

Which files are considered non-free? Is it configure.in and Makefile.in ? Is it sufficient to just remove the "All rights reserved" line and only keep the Copyright? Or must I add the GNU license note to those files as well?

These might be dumb questions but I don't understand all the aspects of the licensing.

Currently I'm moving from my apartment and will have limited access to the internet in the next weeks and limited time to do a new release. I will do a new release as soon as I am established at my new place, or before if I get the time.

Jonas Kvinge <jonaster>
Tue 08 Jan 2008 06:33:08 PM UTC, comment #1: 

Hi,

I'm evaluating the project you submitted for approval in Savannah.


Your project uses openssl, but its license is unfortunately
incompatible with the GNU GPL. This means peolpe cannot legally
redistribute ircproxy. Please investigate using alternatives such as GnuTLS instead (which as a partial openssl-compatible API, for the first steps).


Also, we do not allow to host your project on Savannah and SourceForge at the same time, if Savannah is just a project mirror.  Your project development should happen primarily on Savannah. How do you plan to use your Savannah account?


Last, a few files have a license notice that only say "All right
reserved", which is naturally non-free. Please fix these.


If you are willing to make the changes mentioned above, please provide us with an URL to an updated tarball of your project.  Upon review, we will reconsider your project for inclusion in Savannah.

To help us better keep track of your registration, please use the
tracker's web interface by following the link below. Do not reply
directly; the registration process is not driven by e-mail, and we will not receive such replies.

Regards.

Sylvain Beucler <Beuc>
Sun 06 Jan 2008 02:56:50 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: Night Light IRC Proxy/Bouncer
  • System Name:  ircproxy
  • Type: non-GNU software & documentation
  • License: GNU General Public License v2 or later





Description:

ircproxy is an advanced multi-user IRC bouncer written in C with IPv6 and SSL support. It should work on most unix systems and is known to be working on FreeBSD, OpenBSD, GNU/Linux, Solaris and HP-UX.

It can proxy simultaneous users at the same time to different IRC servers.

The IRC connection can stay connected to IRC when the IRC client disconnects, the user can then later reattach to the same IRC connection.

Private messages and channel activity can an be logged when no IRC clients are attached. You can then see what you have been missing while you're offline.

It is also possible to attach multiple IRC clients on the same IRC connection. This is useful if you want to be connected from home and work at the same time without cloning.




Other Software Required:

c-ares + MIT + http://daniel.haxx.se/projects/c-ares/
openssl + Apache style + http://www.openssl.org/



Tarball URL:

http://downloads.sourceforge.net/ircproxy/ircproxy-1.3.3c.tar.gz


Jonas Kvinge <jonaster>

 

(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 jonaster (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2008-01-11 Beuc StatusWait reply Cancelled
        Open/ClosedOpen Closed
    2008-01-08 Beuc StatusNone Wait reply
        Assigned toNone Beuc

    Back to the top

    Powered by Savane 3.13-bb6a.
    Corresponding source code