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

[Mathieu Roy]

Hi,

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

address@hidden said:

> A package was submitted to savannah.nongnu.org
> This mail was sent to address@hidden, address@hidden
> 
> Bret D Weinraub <address@hidden> described the package as follows:
> License: x11
> Other License: 
> Package: m80
> System name: m80
> Type: non-GNU
> 
> Description:
> Project M80 Savannah (non-gnu) description.
> 
> Project m80 has the following main components:
> - a (just another) build tool composed of GNU m4, GNU make, and some
> custom  utilities for embedding macros in code of any type (C, Perl, 
> Java, etc).

What do you mean by "composed of". Do you mean "linked against",
"relying on" or really composed of, which to me would mean that your 
project include m4,make (I not a native english speaker).

By checking the tarball, I assume that you do not mean "include". 

> - m4 libraries designed to be included within code using m80 as its
> build engine.  These code-generating libraries are intended to make
> advanced features available to code without runtime OO overhead.  -
> a number of code generators that have been built for semi-custom
> purposes, that we intend to integrate into the framwork.  These code
> generators are in several application areas, including: +
> multi-environment deployment and configuration management +
> web-facing applications and deployment + database management,
> configuration management, and data warehousing.
> 
> pre-pre-alpha: http://renwix.com/code/m80-0.1.tar.gz

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,


-- 
Mathieu Roy
 
 << Profile  << http://savannah.gnu.org/users/yeupou <<
 >> Homepage >> http://yeupou.coleumes.org           >>
 << GPG Key  << http://stock.coleumes.org/gpg        <<