The file 'cgps.c' (in your source) is ok, so you can take 'cgps.c' like exemple.

Since when have you started interfering in the content and licensing practices of the projects applying for your site?

We license under BSD and have been doing so for five years; we have no intention of including a GNU header or GNU copyright notices in our code, as that would create legal exposure for users of our library that we wish to avoid. We follow normal practice for non-GNU projects, in which the project license is specified once in a prominent README or LICENSE file and considered to adhere to the entire distribution.

I was the founding president of the Open Source Initiative and a co-author and for years principal maintainer of the Open Source Definition, and I must say I find being lectured as you have done extremely offensive. You are not a lawyer. Don't pretend to be a lawyer or tell people what is legally required, because you don't know.

I'll put it bluntly: you need to back off of this crap, not just with me but with everyone. Leave project leads to take the measures they think are legally prudent; it is their liability, not yours. You have no business requiring anything beyond an OSD-conformant license, and if you insist on meddling in what doesn't concern you I will spread the word that gna is now being run by legalistic assholes and anyone with sense should stay far, far away from it.

License headers required in source code:

Before releasing your project under the license you choose, you
must 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 the plain text
version the license (usually this file is named "COPYING"). The
GPL is available from <http://www.gnu.org/licenses/gpl.txt>.

Additional instructions are available from
<http://www.gnu.org/licenses/gpl-howto.html>, that are usually
valid for libre software licenses.

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>

Source code required:

Please include an (temporary) URL pointing to the source code,
or attach a tarball to this item.

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.