[Savannah-register-public] [task #5863] Submission of secure democracy

[Stephan Peijnik]

Follow-up Comment #4, task #5863 (project administration):

Hi,

I'm sorry this took so long, but I'm now re-evaluating the project you
submitted for approval in Savannah.
There are some problems I've found and these problems need fixing before we
can approve your submission.


First of all, the address of the FSF has changed, and is now:

  51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA

Please update your license notices.

Please update the copy of the license (usually, the 'COPYING' file) in your
package as well.

Updated versions of the GPL, LGPL and GFDL can also be found at:
http://www.gnu.org/licenses/gpl.txt
http://www.gnu.org/licenses/lgpl.txt
http://www.gnu.org/licenses/fdl.txt

You can find some background and a possible migration script at
https://savannah.gnu.org/forum/forum.php?forum_id=3766


Second thing I noticed is, that the license does not contain the last
section, titled "How to Apply These Terms to Your New Programs".

Please use a complete verbatim copy of the license, which may be found at
http://www.gnu.org/licenses/gpl.txt, http://www.gnu.org/licenses/lgpl.txt or
http://www.gnu.org/licenses/fdl.txt.

The license must be copied verbatim and in its entirety.


Another thing that needs fixing is described below:

In order to release your project properly and unambiguously under the GNU
GPL, please place copyright notices and permission-to-copy statements at the
beginning of every copyrightable file, usually any file more than 10 lines
long.

For more information, see http://www.gnu.org/licenses/gpl-howto.html.

If some of your files cannot carry such notices (e.g. binary files), then you
can add a README file in the same directory containing the copyright and
license notices. Check
http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html for further
information.

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,
see http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude.


About your second point:

I'm somehow intersted on what GNU.FREE is, as I don't know anything about it.
This is not related to the processing of your submission, but rather a
question out of interest.


Now something on your fourth point, about assigning a co-copyright to the
FSF:

I'm afraid I can't give you a straight answer on that, but I've contacted the
people who are able to provide both you and me with information on that
topic.
However, I'd really like you to make the other changes needed meanwhile and I
will of course inform you about any information I get regarding this point.


If you are willing to make the changes mentioned above, please provide us
with an URL to an updated tarball of your project.  Upon review, we will
reconsider your project for inclusion in Savannah.

To help us better keep track of your registration, please use the tracker's
web interface following the link below. Do not reply directly, the
registration process is not driven by e-mail, and we will not receive such
replies.

Regards.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/task/?5863>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/