software/!RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2002/001766.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices Coding] contributing to ircservices : legal and coding standards problems
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20contributing%20to%20ircservices%20%3A%20legal%20and%20coding%20standards%20problems&In-Reply-To=">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="001763.html">
  11    <LINK REL="Next"  HREF="001767.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices Coding] contributing to ircservices : legal and coding standards problems</H1>
  15     <B>Lucas Nussbaum</B>
  16     <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20contributing%20to%20ircservices%20%3A%20legal%20and%20coding%20standards%20problems&In-Reply-To="
  17        TITLE="[IRCServices Coding] contributing to ircservices : legal and coding standards problems">lucas at lucas-nussbaum.net
  18        </A><BR>
  19     <I>Fri Dec 13 01:05:08 PST 2002</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="001763.html">[IRCServices Coding] Problem with &quot;Extension data found for nonexisting nick &quot;
  22 </A></li>
  23         <LI>Next message: <A HREF="001767.html">[IRCServices Coding] contributing to ircservices : legal and coding standards problems
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#1766">[ date ]</a>
  27               <a href="thread.html#1766">[ thread ]</a>
  28               <a href="subject.html#1766">[ subject ]</a>
  29               <a href="author.html#1766">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>Hi,
  35
  36 Ircservices 5, with its module support, looks like the best services
  37 package around. Furthermore, the development of other services projects
  38 seems to have slow down, or stopped. It would probably be a good time to
  39 make users come back from ircservices-forked projects to ircservices.
  40
  41 The problem is that several functionnalities are still missing. Several
  42 people would be strongly interested in a botserv module, so I started to
  43 look at how module are implemented, etc... Several things stated in
  44 <A HREF="ftp://ftp.esper.net/ircservices/docs/6.html">ftp://ftp.esper.net/ircservices/docs/6.html</A> disturb me.
  45
  46 1/ While developping a complex module such as botserv, I'll probably
  47 come accross things like missing callbacks, etc. I haven't started
  48 coding, but it seems there's no callback for messages sent to a channel.
  49 (I'm not sure of the m_privmsg callback not ignoring channel privmsgs).
  50 So I'll probably have to modify things in ircservices. Since my
  51 module(s) would be distributed under the GPL (I'm not even part of the
  52 team of any network), I have 3 solutions :
  53 - fork ircservices, but I don't want to. I don't have time and don't
  54   want to maintain such a project, and forking is counter-productive.
  55 - distribute patches to modify ircservices core. Those are difficult to
  56   maintain, and are counter-productive too : my needs of new callbacks
  57 will probably be met by other module developpers too.
  58 - contribute source code to ircservices, but then there's what is in
  59   section 6.3 :
  60 &quot;Furthermore, any submissions of modules, code, documentation, or any
  61 other information (collectively &quot;information&quot;) become the sole property
  62 of the author of IRC Services, and by submitting such information, you
  63 agree to transfer any and all rights you may have in said information to
  64 said author. If you do not agree to the above, or you are not permitted
  65 (by law, contract, or otherwise) to transfer all of your rights in the
  66 information to the author(s) of IRC Services, then you may not submit
  67 the information. (If you cannot comply with this paragraph but would
  68 still like to submit something, please contact the author to discuss
  69 your situation.)&quot;
  70 a. this is against french law, and probably laws from many other
  71 countries : some rights of the author can't be given to someone else.
  72 b. this is against the free software idea.
  73 c. if I code sthing, then contribute it to ircservices, I would no
  74 longer be the author of this, so I couldn't, for example, include it in
  75 a commercial product I distribute.
  76 I don't understand why this clause is needed. There's no risk with
  77 including GPLed code or FDLed documentation in a project, since neither
  78 the GPL nor the FDL can be revoked. Could you please explain ?
  79
  80 2/ Coding standards (section 6.4)
  81 I understand your identifier naming conventions. But there's no need for
  82 Formatting conventions. What about using GNU indent, which is highly
  83 configurable, and provide a .indent.pro file for ircservices, so that
  84 everyone can submit code that matches your very own formatting
  85 conventions ?
  86 --
  87 Lucas Nussbaum
  88 MySQL to IRC gateway : <A HREF="http://www.lucas-nussbaum.net/thales/">http://www.lucas-nussbaum.net/thales/</A>
  89
  90 </PRE>
  91
  92 <!--endarticle-->
  93     <HR>
  94     <P><UL>
  95         <!--threads-->
  96         <LI>Previous message: <A HREF="001763.html">[IRCServices Coding] Problem with &quot;Extension data found for nonexisting nick &quot;
  97 </A></li>
  98         <LI>Next message: <A HREF="001767.html">[IRCServices Coding] contributing to ircservices : legal and coding standards problems
  99 </A></li>
 100          <LI> <B>Messages sorted by:</B>
 101               <a href="date.html#1766">[ date ]</a>
 102               <a href="thread.html#1766">[ thread ]</a>
 103               <a href="subject.html#1766">[ subject ]</a>
 104               <a href="author.html#1766">[ author ]</a>
 105          </LI>
 106        </UL>
 107
 108 </body></html>