[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Savannah-hackers] submission of Yet Another Communication System -
From: |
Sylvain BEUCLER |
Subject: |
Re: [Savannah-hackers] submission of Yet Another Communication System - savannah.nongnu.org |
Date: |
Sun, 22 Aug 2004 23:00:54 +0200 |
User-agent: |
Mutt/1.4.2.1i |
As we have not had a response from you, we have deleted your project
from the pending queue. If you would still like to have your project
hosted at Savannah, please re-submit it for evaluation.
Regards,
--
Sylvain
On Tue, Aug 10, 2004 at 09:14:58PM +0200, Sylvain Beucler wrote:
> Hi,
>
> Sorry for the delay.
>
> I'm still evaluating the project you submitted for approval in Savannah.
>
> On 2004.08.03 22:07 Fonseca wrote:
> >Hi, Sylvain Beucler...
> >
> > I have only a bunch of inoperant source codes just
> >for testing the potential and specific tests like
> >cryptogrphy.
> >
> > I know I have a lot of work to do before releasing
> >it on web.
> >
> > URL: http://sagui.dynu.com/YACSYS-prototype-0.0.0.tgz
>
> I cannot fetch this url.
> Maybe you'll want to send it to me by mail?
>
> > I am concerned on preparing it all for a full GPL
> >compliant system.
>
> We need projects hosted at Savannah to already have appropriate
> copyright and licenses notices, so as to avoid any legal issue.
>
> Here is what we send to project that did not do that step yet:
> ========
> Before releasing your project under the GPL, please place
> copyright notices and permission to copy statements at the beginning
> of every file of source code.
> In addition, if you haven't already, please copy a copy of the plain
> text version of the GPL, available from
> (http://www.gnu.org/licenses/gpl.txt), into a file named "COPYING".
>
> Additional instructions are available from
> http://www.gnu.org/licenses/gpl-howto.html.
>
> The GPL FAQ explains why these procedures must be followed. To learn
> why a copy of the GPL must be included with every copy of the code,
> for example, go to
> http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude
> ========
>
> Please do this before to send me a new tarball.
>
> > About the Crypt::Tea, I've just used it for testing
> >any crypto lib. I want to do one myself.
>
> If you plan to drop Crypt::Tea asap, then we won't reject the project
> for using this non-free dependency.
> I wait for you updated tarball before to tell you whether your project
> is accepted or not :)
>
> --
> Sylvain
>
>
> >Thanks ...
> >
> >
> >
> >
> >
> > --- Sylvain Beucler <address@hidden> escreveu:
> >> Hi,
> >>
> >> I'm evaluating the project you submitted for
> >> approval in Savannah.
> >>
> >> > Romeu Henrique Capparelli Fonsec
> >> <address@hidden> described the
> >> > package as follows:
> >> > License: gpl
> >> > Other License:
> >> > Package: Yet Another Communication System
> >> > System name: yacos
> >> > Type: non-GNU
> >> >
> >> > Description:
> >> > Event Based Mail (and other messaging ways)
> >> Communication System
> >> > (no short name for this yet)
> >> >
> >> > A system based on a database (sqlite or mysql or
> >> postgresql) for
> >> > sending multiple messages. These messages are
> >> controled by events
> >> > (e.g. received, opened, request_for_more). These
> >> events can be
> >> > generated externaly (MPI, ICP) or internally
> >> (Database, trigger). All
> >> > operations is logged on DB.
> >> >
> >> > I will use a external MTA (e.g Postfix)
> >> >
> >> > The Goal of this project is to permit
> >> communication on demand or
> >> > 'opt-ins'. Some uses are:
> >> > - E-mail based courses (lessons are send on
> >> demand)
> >> > - E-mail based marketing (with anti-spam
> >> politics)
> >> > - SMS calls from central
> >> > - etc.
> >> >
> >> >
> >> >
> >> > Other Software Required:
> >> > perl module on CPAN: Crypt::Tea
> >> >
> >> > Other Comments:
> >> > For now I have only a bunch of codes on PHP and
> >> Perl. I will depend on
> >> > any non-GPL lib or prog.
> >> > In the first phase it will be a
> >> Linux+Apache+Php+Postfix+Perl system
> >>
> >> Please include an (temporary) URL pointing to the
> >> source code. The
> >> description you gave when registering will not be
> >> read by the general
> >> public. If you are still concerned with privacy,
> >> however, you can
> >> forward the code to me by email.
> >>
> >> We wish to review your source code, even if it is
> >> not functional, to
> >> catch potential legal issues early.
> >> For example, to release your program properly under
> >> the GPL you must
> >> include a copyright notice and statement permitting
> >> copying at the
> >> beginning of every file of source code. This is
> >> explained in
> >> http://www.gnu.org/licenses/gpl-howto.html. Our
> >> review would help
> >> catch potential omissions such as these.
> >>
> >>
> >> Also, Crypt::Tea is released under the Artistic
> >> license, which does
> >> not qualify as a free software license. Check
> >>
> >http://www.gnu.org/licenses/license-list.html#ArtisticLicense
> >> We do not accept non free software dependencies.
> >>
> >> However, most Perl packages (including Perl itself)
> >> are dual licensed
> >> GPL + Artistic, which solves this issue. I am pretty
> >> sure you could
> >> talk the Crypt::Tea author, Abhijit Menon-Sen
> >> <address@hidden>, into
> >> re-releasing his work under this dual license.
> >>
> >> Are you willing to do this?