Re: [Savannah-hackers] submission of paparazzi - savannah.nongnu.org

[Rudy Gevaert]

Hi,

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

On Tue, Jan 28, 2003 at 05:29:49AM -0500, address@hidden wrote:
> 
> A package was submitted to savannah.nongnu.org
> This mail was sent to address@hidden, address@hidden
> 
> 
> antoine drouin <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: paparazzi
> System name: paparazzi
> Type: non-GNU
> 
> Description:
> This project aims to create a low cost open source UAV (Unmaned Air Vehicule).

Note that Savannah supports projects of the Free Software
movement, not projects of the Open Source movement.
We are careful about ethical issues and insist on
producing software that is not dependent on proprietary
software.

While Open Source as defined by it's founders means 
Free Software, it's frequently misunderstood.
For more information, read
http://www.gnu.org/philosophy/free-software-for-freedom.html


> 
> The onboard hardware consists of a Pic MCU (microcontroller unit) and several 
> sensors (GPS, pressure...). Code is written in assembly using GPASM 
> (http://gputils.sourceforge.net). 
> We are planning to test a linux handheld with 802.11 for higher level 
> computations and communications.
> 
> The ground station consist of a laptop running Gnu/Linux. 
> For now we use RTTY (http://www.ele.uva.es/~jesus/rtty/rtty-2.0.html) for the 
> downlink, but 802.11 might remove this need.
> We have a GUI written in GTK that displays the position of the plane on a map 
> and the indications from the intruments.
> We have also developed code to deal with the GPS binary protocol (SIRF).
> 
> Code is not online, but i can mail you a copy 

Please register your project again including a URL
(could be temporary) where the source code can be found.
The description you give during project registration will be
read by Savannah administrators and not by the general Savannah
public (if you are still concerned with privacy, you can also
send me a copy of the code by e-mail).

We would like to look at your source code, even if it is still
not functional, to help you fix potential legal issues which
would be harder to find and to solve after the project gets
approved. For example, 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, as advise in http://www.gnu.org/licenses/gpl-howto.html

(Or mail it to address@hidden)

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

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