Re: [Savannah-hackers] submission of Virtual Private Ethernet - savannah.nongnu.org

[Rudy Gevaert]

Hi,

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

On Thu, Feb 20, 2003 at 03:08:12PM -0500, address@hidden wrote:
> 
> A package was submitted to savannah.nongnu.org
> This mail was sent to address@hidden, address@hidden
> 
> 
> Marc A. Lehmann <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: Virtual Private Ethernet
> System name: vpe
> Type: non-GNU
> 
> Description:
> vpe stands for virtual private ethernet, and is \"yet another tunnel 
> solution\" featuring encapsulation, compression and encryption
> of ethernet packets.
> 
> The differences between vpe and most other \"vpn\"\'s is that this
> implements a real network, that is, multiple hosts connected
> with a virtual ethernet.
> 
> The goals of this project are to provide a very basic, featureless
> but robust, small (in memory) and fast solution that is relatively easy to 
> setup (only one shared config file + autogenerated rsa keys)
> and uses a single UDP port only.
> 
> The reason I wrote (or started to write) it is that I didn\'t find another 
> solution that runs stable and conencts multiple hosts.
> 
> I used tincd (GPL) as a base, threw away all the tincd code exceot the 
> configure, Makefiles, m4 macros and rpelacement functions that were mostly 
> taken from other free projects.

In order to release your project under the GPL you
should write copyright notices and copying permission
statements at the beginning of every source-code file, and
include a copy of the plain text version of the GPL
(http://www.gnu.org/licenses/gpl.txt). Copy it for instance
into a file named COPYING.

Please follow the advice of http://www.gnu.org/licenses/gpl-howto.html

The GPL FAQ can also help you understand the reason behind
thoses recommendations. For example, there is an entry explaining
why the GPL requires including a copy of the GPL with
every copy of the program:
 http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude


> 
> http://data.plan9.de/vpe-0.1.tar.gz
> 
> Does still contain the doc subdir form the tincd distribution, but it\'s work 
> in progress, and will be cleaned up before the first check-in.
> 
> Other Software Required:
> openssl
> 
> Other Comments:
> I wouldn\'t mind at all to making this program (if wanted ;) part of the GNU 
> project, but I didn\'t select it yet because the source certainly isn\'t up 
> to the GNU standards yet. It would be helpful if the page would state that 
> you cna apply for a GNU project later (which I assume, but maybe it\'s not as 
> easy), or at least tell the actual requirements to apply for that (the 
> refernces don\'T go into this topic).
> 

When you feel your code is mature enough you can mail to
address@hidden and ask for inclusion into the GNU project.  The
transition from nongnu to gnu can easily be done by us

Please register your project once more with the changes mentioned
above. The way we handle pending projects makes it difficult to keep
track of projects that have been answered but have not been approved
yet, so we erase them and we ask you to register the project again every
time some change has to be done to the registration, and users might
have to register their projects several times. Thank you for your
understanding.

Some users find it useful to use the big re-registration URL provided in
the acknowledgment e-mail you received after registration.

Regards,


-- 
Rudy Gevaert                address@hidden              
Web page                    http:/www.webworm.org
GNU/Linux for schools       http://www.nongnu.org/glms
Savannah hacker             http://savannah.gnu.org