[Savannah-register-public] [task #14571] Submission of Comparison Plotter to visually evaluate ocean model simulations

2017-07-04 Thread Pavel Kharitonov
Follow-up Comment #8, task #14571 (project administration):

You sent me two messages via Savannah interface; I replied to both via email;
do you get my replies?

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14577] Submission of rsys

2017-07-03 Thread Pavel Kharitonov
Update of task #14577 (project administration):

  Status:None => Cancelled  
 Assigned to:None => ineiev 
 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

GNU is already a free software operating system; please be more specific and
provide a tarball with real sources.

Cancelling.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14575] Submission of Experimental GSEGrafix

2017-07-03 Thread Pavel Kharitonov
Update of task #14575 (project administration):

  Status:None => In Progress
 Assigned to:None => ineiev 

___

Follow-up Comment #1:

These files lack copyright and license notices:
gsegraphics.css NEWS, some data files in help_files/
(some files say they are public domain; it would be
desirable to mention their authors if possible), many *.texi files
in texinfo_files/.

Also, Savannah discourages short non-descriptive names;
what about gsegrafix-experimental instead of gsee?

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14571] Submission of Comparison Plotter to visually evaluate ocean model simulations

2017-06-30 Thread Pavel Kharitonov
Follow-up Comment #7, task #14571 (project administration):

I'm sorry, I'm not a scientist, and I'm not quite familiar with the
situation.

> I would think a list of coordinates is not copyrightable. 

A list of coordinates is a kind of map; maps are copyrightable.

> as I note in the README_data.md, it is a practice to use the data for any
(scientific?) purpose

...until Elsevier sues Sci-Hub.

Ideally, you could generate sample data; if it's too hard, you could keep them
out of your package and add references.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14571] Submission of Comparison Plotter to visually evaluate ocean model simulations

2017-06-29 Thread Pavel Kharitonov
Follow-up Comment #5, task #14571 (project administration):

Thank you!

I still see two issues with lacking notices: logo.png and third-party files in
data/. The former is minor, the latter to my mind is essential.



___

Reply to this item at:

  

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




[Savannah-register-public] [task #14571] Submission of Comparison Plotter to visually evaluate ocean model simulations

2017-06-27 Thread Pavel Kharitonov
Follow-up Comment #3, task #14571 (project administration):

Thank you; unfortunately, some issues remained.

After reading data/README_data.md, the license of some files
in that directory remains unclear (and it would be desirable
to have explicit copyright notices for them).

scripts/put_colourbar.jnl scripts/put_text.jnl still lack notices.

Files like TODO.txt, tracers.txt and logo.png also should have
notices (for formats like images, such notices are usually put
in a README file in the same directory).

Having CC SA-BY in disjunction is fine; the requirement is to be free to use
it under the FDL.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14573] Submission of test

2017-06-27 Thread Pavel Kharitonov
Update of task #14573 (project administration):

  Status:None => Cancelled  
 Assigned to:None => ineiev 
 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

Cancelling; if you want to really register a project, please use more specific
name and description.

Thank you!

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14571] Submission of Comparison Plotter to visually evaluate ocean model simulations

2017-06-26 Thread Pavel Kharitonov
Update of task #14571 (project administration):

  Status:None => In Progress
 Assigned to:None => ineiev 

___

Follow-up Comment #1:

Thank you for submitting your package!

On Ferret licensing: first, OSD is not a license, it's a set of criteria for
licenses, then, Ferret is a work of the US, it's public domain.  It's true
that page you pointed at is confusing.

On notices in scripts: those scripts already contain description, author,
requirements, and history; it doesn't seem to me that adding copyright and
license notices would make the comments crucially longer.

On CC BY-SA: it's compatible with GPLv3, but not with further versions (and
not with the FDL). Savannah's requirements for software is to be
GPLv3+-compatible, and for manuals to be FDL1.3+-compatible.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14542] Submission of MemPool library

2017-06-22 Thread Pavel Kharitonov
Follow-up Comment #6, task #14542 (project administration):

One more todo item: create a home page. Please ask webmast...@gnu.org if you
need any help with that.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14542] Submission of MemPool library

2017-06-22 Thread Pavel Kharitonov
Update of task #14542 (project administration):

  Status: In Progress => Done   
 Open/Closed:Open => Closed 

___

Follow-up Comment #5:

Approving.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14539] Submission of Rheolef

2017-06-22 Thread Pavel Kharitonov
Follow-up Comment #2, task #14539 (project administration):

If there is no further interest, I'll cancel this submission.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14536] Submission of LibreRead

2017-06-22 Thread Pavel Kharitonov
Update of task #14536 (project administration):

  Status: In Progress => Done   
 Open/Closed:Open => Closed 

___

Follow-up Comment #26:

Thank you, approving.

>Those are PDFjs files, and I've put the COPYRIGHT AND LICENSE inside the
respective directories. Is it necessary that I should mention all the
filenames too in the COPYRIGHT?

Yes, it would be nice to have them listed there, and an explicit notice that
the conditions from the LICENSE apply to them.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14536] Submission of LibreRead

2017-06-22 Thread Pavel Kharitonov
Follow-up Comment #24, task #14536 (project administration):

I agree, I could do better.

LICENSE is the text of the license; copyright notices are copyright notices,
they claim who the copyright holders of the respective files are; and license
notices say that the files are under the license in question. The text of the
license doesn't list the copyright holders of the files, and it doesn't say
what files it apply to. Those are different texts.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14542] Submission of MemPool library

2017-06-22 Thread Pavel Kharitonov
Follow-up Comment #3, task #14542 (project administration):

Thank you; I've filed a request about eCos license to licensing@.

Now, GNU Maintainer Information

recommends that all non-trivial files have copyright and license notices;
in your package, README has none; could you add them?
(You could use a simple license for "other files"
.)

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14542] Submission of MemPool library

2017-06-21 Thread Pavel Kharitonov
Update of task #14542 (project administration):

  Status:None => In Progress
 Assigned to:None => ineiev 

___

Follow-up Comment #1:

First, your submission says 'the GPLv2+ + eCos exception',
but your files refer to the GPLv3. By the way, have you ever read
section (3) of the GPLv3? It has nothing to do with distributing
source code. And this is where we come to a dark corner:
how should the eCos exception apply to software under the GPLv3
(and later versions)? Is that section of the GPLv2 still in effect?
But those files are not under the GPLv2 any more.

On the other hand, I can only see your and FSF's copyright
notices in your code; perhaps the FSF will be willing
to re-release it under the LGPLv3+ or some other unambiguous license.

What did gnueval say? What do you think?

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14529] Submission of Real Time Application Interface (for Linux)

2017-06-21 Thread Pavel Kharitonov
Follow-up Comment #21, task #14529 (project administration):

Thank you.

Files like addons/comedi/kcomedi.c have a wrong license notice,
it ends like


 * You should have received a copy of the GNU Lesser General Public
 * License along with this library; if not, write to the Free Software
 * 
 */


All non-trivial files should have copyright and license notices; in your
rtai-5.1-mora.tgz, ChangeLog and some README files have none.

I feel I failed to explain this so far; do you think there is
something hard to understand about it?

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14536] Submission of LibreRead

2017-06-19 Thread Pavel Kharitonov
Follow-up Comment #21, task #14536 (project administration):

Please add copyright notices for those files coming from PDF.js; since *.map
files are generated, you may consider removing them instead.

If some file is public domain, you should mention it explicitly.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14536] Submission of LibreRead

2017-06-18 Thread Pavel Kharitonov
Follow-up Comment #14, task #14536 (project administration):

Thank you!

Could you write something more explicit in COPYRIGHT files relating
to the images? Ideally, it should list particular files, and say
it applies to them.

Also, some files refer to Apache 2.0 license without providing its
full text; it would be nice if the text of that license could be easily
found in the distribution tarball of your package.

Those are minor issues, and I'd probably approve your package,
but images in static/css/images still have no copyright and license notices,
as well as static/js/pdfjs/build/*.map, and some other files.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14536] Submission of LibreRead

2017-06-17 Thread Pavel Kharitonov
Follow-up Comment #12, task #14536 (project administration):

Thank you; let us proceed with LibreRead itself.

All non-trivial files should have valid license and copyright notices
; this applies to the
source files, READMEs and images.  Many files in LibreRead lack them; could
you fix that?

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14536] Submission of LibreRead

2017-06-17 Thread Pavel Kharitonov
Follow-up Comment #10, task #14536 (project administration):

Thank you for clarifications!

> There is no Elasticsearch code I'm including in my project.

Generally, you don't need to include any code to
form a combined executable

you said you basically link to it, and it's sufficient.

The license of Elasticsearch may or may not impose conditions
on programs that use it; but it's a dependency, and it must
be free in order to host a project that depends on it on Savannah.
When I download Elasticsearch sources from GitHub,
I see in core/licenses/lucene-NOTICE.txt:


JUnit (junit-4.10) is licensed under
the Common Public License v. 1.0
See http://junit.sourceforge.net/cpl-v10.html


The CPL is GPL-incompatible
.


The KStem stemmer in
analysis/common/src/org/apache/lucene/analysis/en
was developed by Bob Krovetz and Sergio Guzman-Lara
(CIIR-UMass Amherst) under the BSD-license.


The Original BSD License is GPL-incompatible
.

core/licenses/spatial4j-NOTICE.txt refers to the
Eclipse Public License ,
which is GPL-incompatible.

At last, core/licenses/jts-LICENSE.txt is the text of the LGPLv3.
In other words, the authors of Elasticsearch used some code without
permission.  This technically means that the users aren't allowed to copy,
modify and redistribute Elasticsearch.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14536] Submission of LibreRead

2017-06-16 Thread Pavel Kharitonov
Follow-up Comment #5, task #14536 (project administration):

PDF.js: I think you are right, Node.js is not a dependency, so it's
compatible.

Elasticsearch is not completely Apache 2.0. Its licenses are listed in
NOTICE.txt, they include the LGPLv3 (supplied in a way that in fact
violates that license), and a number of licenses for netty, some of
them are ambiguously mentioned (like "BSD Style License"), but not
provided in the text of the notice.

Let us take for granted that they are GPLv3+-compatible. However,
in the text of the source files, no GNU licenses are ever mentioned,
so the user has to assume that only the exact versions of the licenses
apply. The LGPLv2.1 may be upgraded to any version of the GPL since 2,
but the LGPLv3 is not compatible with future versions of the GPL.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14524] Submission of Turnador

2017-06-15 Thread Pavel Kharitonov
Update of task #14524 (project administration):

  Status: In Progress => Cancelled  
 Open/Closed:Open => Closed 

___

Follow-up Comment #3:

No response; cancelling.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14513] Submission of SImple Library

2017-06-15 Thread Pavel Kharitonov
Update of task #14513 (project administration):

  Status:   Need Info => Cancelled  
 Open/Closed:Open => Closed 

___

Follow-up Comment #2:

No response; cancelling.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14536] Submission of LibreRead

2017-06-15 Thread Pavel Kharitonov
Update of task #14536 (project administration):

  Status:None => In Progress
 Assigned to:None => ineiev 

___

Follow-up Comment #1:

Thank you for submitting your package!

When I download PDF.js I see "install Node.js" in README, this suggests PDF.js
uses that library; in its turn, some parts of Node.js are released under the
OpenSSL license, and it is GPL-incompatible.  So it looks like your package
isn't going to be GPL-compatible: you can allow linking your code with
Node.js, but your users shan't be able to combine your package with
third-party GPLed software.

(I couldn't find licenses for some parts of Elasticsearch, so I can't tell if
similar issues apply to that dependency.)

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14539] Submission of Rheolef

2017-06-15 Thread Pavel Kharitonov
Update of task #14539 (project administration):

  Status:None => In Progress
 Assigned to:None => ineiev 

___

Follow-up Comment #1:

Hello, Pierre!

Thank you for submitting your package.

First, all non-trivial files should have valid copyright and license notices
; files like
COPYING.FRENCH, ChangeLog, README haven't.

Then, I've just picked utils/doubledouble/math.cc and noticed that it says
"Except where otherwise indicated, this program is free software". I really
don't like this; for me, this suggests that it is not free software somewhere,
making the whole thing proprietary.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14538] Submission of postqgrep

2017-06-15 Thread Pavel Kharitonov
Update of task #14538 (project administration):

  Status:None => Done   
 Assigned to:None => ineiev 
 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

Hello, Jim!

I'm approving your project; please add a copyright notice to Makefile.PL (it
has only license notice),
https://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html

Thank you!

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14524] Submission of Turnador

2017-06-08 Thread Pavel Kharitonov
Follow-up Comment #2, task #14524 (project administration):

If three is no further interest, I'll cancel this submission.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14529] Submission of Real Time Application Interface (for Linux)

2017-06-07 Thread Pavel Kharitonov
Follow-up Comment #19, task #14529 (project administration):

I think that'll do,
https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html


___

Reply to this item at:

  

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




[Savannah-register-public] [task #14512] Submission of Traditional Chinese WWW (zh_TW)

2017-06-06 Thread Pavel Kharitonov
Update of task #14512 (project administration):

  Status: In Progress => Done   
 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

Approving, with Cheng-Chia Tseng as co-ordinator.

Thank you!

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14529] Submission of Real Time Application Interface (for Linux)

2017-06-05 Thread Pavel Kharitonov
Follow-up Comment #17, task #14529 (project administration):

Savannah has no issue with waiting until the package is fixed.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14532] Submission of FRITZ!Box voicebox converter

2017-06-05 Thread Pavel Kharitonov
Update of task #14532 (project administration):

  Status: In Progress => Done   
 Open/Closed:Open => Closed 

___

Follow-up Comment #5:

Thank you; approving.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14532] Submission of FRITZ!Box voicebox converter

2017-06-05 Thread Pavel Kharitonov
Follow-up Comment #3, task #14532 (project administration):

The GNU project  didn't
start as a quick hack.  NAVSTAR didn't start as a quick hack.  The
Encyclopédie didn't start as a quick hack.

Yes, my point is about the size: the users may send patches or may not, it may
grow or may not.  Unless it does, it makes little sense to have a Savannah
group for it; and until it does, its need for a dedicated Savannah group is
limited.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14529] Submission of Real Time Application Interface (for Linux)

2017-06-04 Thread Pavel Kharitonov
Follow-up Comment #15, task #14529 (project administration):

> 5)  I don't think that Paolo, or anyone else, can commit to change the
already distributed tarball. Nor to change the old, pre-existing CVS history,
where the first commit of some files was without copyright notices.

I don't think it's necessary to rewrite history in such ways.  It would be
sufficient if you got the most recent working copy, make those changes and
produce a new tarball from it.  When you import VCS history, those changes
will result in a single commit, so it shouldn't be very complicated.

If this is still too hard for you, you'll have to speak to gnu-advisory or rms
about an exception; Savannah admins are not in the position to make such
decisions.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14529] Submission of Real Time Application Interface (for Linux)

2017-06-02 Thread Pavel Kharitonov
Follow-up Comment #13, task #14529 (project administration):

* Yes, this is a common requirement.
* In carbonkernel Makefile.am is likely to be uncopyrightable (it's
effectively less than 10 lines long); for longer files, please file a bug
report in their tracker.  Likewise for other projects.
* One can get an impression that you aren't really willing to follow our
policies.  In such cases it may be better for all if people withdraw their
registration.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14529] Submission of Real Time Application Interface (for Linux)

2017-06-01 Thread Pavel Kharitonov
Follow-up Comment #10, task #14529 (project administration):

If you are not a VCS expert, Savannah admins will help you; however, I'm
afraid having necessary texts in place is a prerequisite for registering on
Savannah.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14529] Submission of Real Time Application Interface (for Linux)

2017-06-01 Thread Pavel Kharitonov
Follow-up Comment #8, task #14529 (project administration):

Thank you, this tarball is just what I wanted.

When your package is registered on Savannah, you'll get a write access to its
newly created repositories, so you'll be free to import any history as you
wish.

Now, all files, including documentation, makefiles and configure scripts,
should have valid license and copyright notices
 --- not just *.c and *.py
files.

I also couldn't find the text of the GPL in your tarball.

At last, the postal address of the FSF used in your notices is outdated, I
recommend use the URL like GPL HowTo
 suggests.

Could you fix that?

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14529] Submission of Real Time Application Interface (for Linux)

2017-06-01 Thread Pavel Kharitonov
Follow-up Comment #6, task #14529 (project administration):

This looks like a repository. Could you provide a link to a distribution
tarball, without any VCS files?

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14529] Submission of Real Time Application Interface (for Linux)

2017-06-01 Thread Pavel Kharitonov
Follow-up Comment #4, task #14529 (project administration):

Please post a link to your tarball.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14528] Submission of relax

2017-06-01 Thread Pavel Kharitonov
Follow-up Comment #5, task #14528 (project administration):

Please let us know when a fixed tarball is ready.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14530] Submission of DDC/CI Python script

2017-06-01 Thread Pavel Kharitonov
Update of task #14530 (project administration):

  Status: In Progress => Done   
 Open/Closed:Open => Closed 

___

Follow-up Comment #3:

Thank you, approving.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14528] Submission of relax

2017-05-31 Thread Pavel Kharitonov
Update of task #14528 (project administration):

  Status:   Need Info => In Progress

___

Follow-up Comment #3:

All nontrivial files, including changelogs and images, should have valid
license and copyright notices
; some files e.g. in docs/
and graphics/ have not.

Could you fix that?

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14509] Submission of toGPRi v1 tools

2017-05-31 Thread Pavel Kharitonov
Update of task #14509 (project administration):

  Status:None => Done   
 Open/Closed:Open => Closed 

___

Follow-up Comment #11:

Thank you, approving.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14527] Submission of Tangomon

2017-05-30 Thread Pavel Kharitonov
Update of task #14527 (project administration):

  Status: In Progress => Done   
 Open/Closed:Open => Closed 


___

Reply to this item at:

  

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




[Savannah-register-public] [task #14527] Submission of Tangomon

2017-05-30 Thread Pavel Kharitonov
Follow-up Comment #3, task #14527 (project administration):

Probably you are right, copyright notices are not needed
in the case of CC0; however, the original copyright holders
still should be listed:
https://www.gnu.org/prep/maintain/html_node/FSF_002dCopyrighted-Package.html
https://wiki.creativecommons.org/wiki/CC0_FAQ#May_I_apply_CC0_to_computer_software.3F_If_so.2C_is_there_a_recommended_implementation.3F

It is also recommended to provide the text of CC0 in the tarball.

Regarding the rest, it looks like
CC use "author" in the sense of "copyright holder"

("2. Author  - Who owns the material"), and their licenses admit
that the work may not be accompanied with copyright notice.

Still I think you should write down notices for the GPL'd
sounds/hurt.wav as the GPL HowTo recommends

(the name of the copyright holder seems
Matthias Braun , the copyright year can be figured out
from the year when the file was released).

Approving.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14528] Submission of relax

2017-05-30 Thread Pavel Kharitonov
Update of task #14528 (project administration):

  Status:None => Need Info  
 Assigned to:None => ineiev 

___

Follow-up Comment #1:

I can't download the tarball; could you attach it in a comment?

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14509] Submission of toGPRi v1 tools

2017-05-30 Thread Pavel Kharitonov
Follow-up Comment #9, task #14509 (project administration):

If the format of the files strongly discourages embedded comments, you could
put the notices in a README
 file in
the same directory.

You are going to distribute examples effectively as a part of your package. 
They should be distributable, and without notices they are not.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14513] Submission of SImple Library

2017-05-29 Thread Pavel Kharitonov
Update of task #14513 (project administration):

  Status:None => Need Info  
 Assigned to:None => ineiev 

___

Follow-up Comment #1:

Hello, Christophe!

Since your library provides nothing new and serves no particular purpose, I
wonder if it's worth publishing at all.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14527] Submission of Tangomon

2017-05-29 Thread Pavel Kharitonov
Follow-up Comment #1, task #14527 (project administration):

Hello, Julie!

Files in data/ directory lack valid copyright notices
 (please
note that it's copyright holders that should be listed, not authors).

README.txt also has no copyright notice.

Could you fix that?

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14527] Submission of Tangomon

2017-05-29 Thread Pavel Kharitonov
Update of task #14527 (project administration):

  Status:None => In Progress
 Assigned to:None => ineiev 


___

Reply to this item at:

  

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




[Savannah-register-public] [task #14526] Submission of Secure Service For All Messages

2017-05-29 Thread Pavel Kharitonov
Follow-up Comment #1, task #14526 (project administration):

No source tarball; cancelling.

If I'm mistaken and you really have something to submit, please provide a
complete source tarball, list your dependencies, describe your package in a
more clear way.

Thank you!

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14526] Submission of Secure Service For All Messages

2017-05-29 Thread Pavel Kharitonov
Update of task #14526 (project administration):

  Status:None => Cancelled  
 Assigned to:None => ineiev 
 Open/Closed:Open => Closed 


___

Reply to this item at:

  

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




[Savannah-register-public] [task #14509] Submission of toGPRi v1 tools

2017-05-29 Thread Pavel Kharitonov
Follow-up Comment #7, task #14509 (project administration):

Thank you!

octave-workspace still has no copyright and license notices; neither do the
examples.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14524] Submission of Turnador

2017-05-29 Thread Pavel Kharitonov
Update of task #14524 (project administration):

  Status:None => In Progress
 Assigned to:None => ineiev 

___

Follow-up Comment #1:

Hello, William!

Please list the dependencies of your package; also, turnador and turnador.conf
in your tarball have no valid copyright and license notices.

At last, please don't submit compressed VCS repositories, just a distribution
tarball.

Thank you!

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14520] Submission of Comunidade Curitiba Livre

2017-05-25 Thread Pavel Kharitonov
Update of task #14520 (project administration):

  Status:None => Done   
 Assigned to:None => ineiev 
 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

Approving.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14517] Submission of Debbugs for GNU

2017-05-23 Thread Pavel Kharitonov
Follow-up Comment #5, task #14517 (project administration):

Thank you, you were right, I hadn't read that discussion carefully; now I
have, but it still isn't clear for me why this package should be exempt from
Savannah policy.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14515] Submission of New Introduction to Programming in Emacs Lisp

2017-05-23 Thread Pavel Kharitonov
Update of task #14515 (project administration):

  Status: In Progress => Done   
 Open/Closed:Open => Closed 

___

Follow-up Comment #5:

Thank you, approving.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14515] Submission of New Introduction to Programming in Emacs Lisp

2017-05-22 Thread Pavel Kharitonov
Follow-up Comment #4, task #14515 (project administration):

Thank you!

Unfortunately, you seem to have failed to attach the right text: your file
ends with the text of the LGPLv3 rather than the FDL.

If you intend to use the LGPL, you should replace the license notice and
attach the text of the GPLv3 because the LGPLv3 is a set of permissions on top
of the GPLv3.

If you want to use the FDL, you should include it and specify your cover texts
and invariant sections, please check FDL HowTo
.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14515] Submission of New Introduction to Programming in Emacs Lisp

2017-05-22 Thread Pavel Kharitonov
Update of task #14515 (project administration):

  Status:None => In Progress
 Assigned to:None => ineiev 


___

Reply to this item at:

  

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




[Savannah-register-public] [task #14515] Submission of New Introduction to Programming in Emacs Lisp

2017-05-22 Thread Pavel Kharitonov
Follow-up Comment #3, task #14515 (project administration):

Yes, please attach a new tarball to a comment in this discussion.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14517] Submission of Debbugs for GNU

2017-05-22 Thread Pavel Kharitonov
Follow-up Comment #3, task #14517 (project administration):

I don't believe omitting the review of notices is up to Savannah admins; you
could ask licens...@fsf.org if you think you can convince them (it may take
much longer time to wait a response from them than to fix the code).

WRT diverging from the upstream: why not suggest them your fixes?

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14514] Submission of BASHRC file

2017-05-22 Thread Pavel Kharitonov
Update of task #14514 (project administration):

  Status:None => Cancelled  
 Assigned to:None => ineiev 
 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

Hello, denisse!

I'm afraid, your project is too simplistic; we don't register such projects.

Cancelling.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14515] Submission of New Introduction to Programming in Emacs Lisp

2017-05-22 Thread Pavel Kharitonov
Follow-up Comment #1, task #14515 (project administration):

Hello, Jean-Christophe!

Your file lacks valid copyright and license notices
; also, the text of the
FDL should come with the package it covers.

Did you copy anything from Robert J. Cassel's manual? If yes, has it an
FDL-compatible license?

Thank you!

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14517] Submission of Debbugs for GNU

2017-05-22 Thread Pavel Kharitonov
Update of task #14517 (project administration):

  Status:None => In Progress
 Assigned to:None => ineiev 

___

Follow-up Comment #1:

Hello, Ludovic!

Files like html/Access.html~ look like backup copies; could you remove
non-relevant files, it would make review easier.

Many files have no valid license and copyright notices
, this should be fixed;
some files in html/ have incorrect notices like "Copyright (C) years holder,
years holder...". the correct form has a line with "Copyright (C)" per holder.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14512] Submission of Traditional Chinese WWW (zh_TW)

2017-05-19 Thread Pavel Kharitonov
Update of task #14512 (project administration):

  Status:None => In Progress
 Assigned to:None => ineiev 


___

Reply to this item at:

  

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




[Savannah-register-public] [task #14017] Submission of Dragons of Lore

2017-05-15 Thread Pavel Kharitonov
Update of task #14017 (project administration):

  Status:   Need Info => Cancelled  
 Open/Closed:Open => Closed 

___

Follow-up Comment #2:

Cancelling per task #14457.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14031] Submission of Priests of Lore

2017-05-15 Thread Pavel Kharitonov
Update of task #14031 (project administration):

  Status:  Wait reply => Cancelled  
 Open/Closed:Open => Closed 

___

Follow-up Comment #2:

Cancelling per task #14457.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14465] Submission of Assassin of the Underdark

2017-05-15 Thread Pavel Kharitonov
Update of task #14465 (project administration):

  Status:None => Cancelled  
 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

Cancelling per task #14457.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14457] Submission of pyisabella

2017-05-15 Thread Pavel Kharitonov
Update of task #14457 (project administration):

 Open/Closed:Open => Closed 


___

Reply to this item at:

  

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




[Savannah-register-public] [task #14457] Submission of pyisabella

2017-05-15 Thread Pavel Kharitonov
Update of task #14457 (project administration):

  Status: In Progress => Cancelled  

___

Follow-up Comment #7:

Cancelling.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14509] Submission of toGPRi v1 tools

2017-05-15 Thread Pavel Kharitonov
Follow-up Comment #3, task #14509 (project administration):

Thank you!

Please attach a new tarball to your comment when it's ready.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14509] Submission of toGPRi v1 tools

2017-05-12 Thread Pavel Kharitonov
Update of task #14509 (project administration):

 Assigned to:None => ineiev 

___

Follow-up Comment #1:

Hello, Javier!

Thank you for your submission!

Unfortunately, there are some issues to resolve.

Your submission says "GPLv2 or later", but the license you
include is GPLv3, and the license notices in your files
confirm GPLv3+.  Was it a mistake?

Then, all files should have valid copyright and license notices
.
Files in examples/ have not.

Some Octave files like rf_crwb.m lack both copyright and license
notices.

In other files, copyright notice ("© 2016 Javier Sanjurjo Pinto.")
is not quite correct, please check 
https://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html for the
recommended format.

The PDF file has no source, this makes the whole package
unredistributable, because by using the GPL you require that
the redistributors provide the corresponding source code,
but your users will have none.

There is another thing to make sure: the PDF file says it's part
of your PhD work.  Such works typically qualify as "works for hire",
their copyright holders are the universities rather than their
authors.  Did you arrange a copyright assignment?

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14503] Submission of pairinteraction

2017-05-09 Thread Pavel Kharitonov
Update of task #14503 (project administration):

  Status: In Progress => Cancelled  
 Open/Closed:Open => Closed 

___

Follow-up Comment #5:

>  Is the issue that it cannot be distributed under GPL later than v3?

Yes, it is.

>  If that is the case, this is a show-stopper for us and we have to withdraw
our application.

Thank you, cancelling.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14503] Submission of pairinteraction

2017-05-08 Thread Pavel Kharitonov
Follow-up Comment #3, task #14503 (project administration):

At last, I couldn't find source code for Anaconda on the site you've listed,
and I couldn't check its license.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14503] Submission of pairinteraction

2017-05-08 Thread Pavel Kharitonov
Follow-up Comment #2, task #14503 (project administration):

Similar issue with PyQt: it's GPLv3-only.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14503] Submission of pairinteraction

2017-05-08 Thread Pavel Kharitonov
Update of task #14503 (project administration):

  Status:None => In Progress
 Assigned to:None => ineiev 

___

Follow-up Comment #1:

Thank you for submitting your package!

Savannah has a policy that all package dependencies be redistributable under
the GPLv3 or later (at redistributor's option).

wignerSymbols is released in such a way that it isn't clear if the user may
distribute it under later versions of the LGPL (in fact, it doesn't even
include the text of the GPLv3 which is a part of the LGPLv3).  In files like
src/wignerSymbols-cpp.cpp, one can read just "LGPL", this may be interpreted
as "any version of the LGPL", but files like src/xerprn.f have no license
notice at all, so the user has to assume the exact license provided in
LICENSE.txt (or no license at all).

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14504] Submission of No X Utilities

2017-05-08 Thread Pavel Kharitonov
Update of task #14504 (project administration):

  Status:None => Cancelled  
 Assigned to:None => ineiev 
 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

You submitted your package as a part of the GNU project; such packages have a
different evaluation procedure, please check
https://www.gnu.org/help/evaluation.html.

Cancelling.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14414] Submission of GNUstep Non-FSF

2017-05-08 Thread Pavel Kharitonov
Follow-up Comment #21, task #14414 (project administration):

Thank you!

I still can't find copyright and license notices for files like
GNUMail.suiteModel and GNUMail.scriptSuite.

Files like Resources/Russian.lproj/README don't list the files
they apply to.

Bundles/Face/Face.h has a confusing statement:

// This code has been created by Carl Edman 
// (C) Copyright 1995, but otherwise this file is perfect freeware.

Could you clarify the status of that file? Generally, "freeware" is
proprietary software
.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14499] Submission of HUBAngl

2017-05-08 Thread Pavel Kharitonov
Update of task #14499 (project administration):

  Status: In Progress => Done   
 Open/Closed:Open => Closed 

___

Follow-up Comment #6:

Thank you, approving.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14499] Submission of HUBAngl

2017-05-04 Thread Pavel Kharitonov
Follow-up Comment #4, task #14499 (project administration):

Yes, please attach new tarball to your comment, and list all essential
dependencies in the text of comment.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14499] Submission of HUBAngl

2017-05-02 Thread Pavel Kharitonov
Follow-up Comment #2, task #14499 (project administration):

P.S. Please don't include VCS files in your tarball; this makes evaluation
easier.  Thank you!

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14499] Submission of HUBAngl

2017-05-02 Thread Pavel Kharitonov
Update of task #14499 (project administration):

  Status:None => In Progress
 Assigned to:None => ineiev 

___

Follow-up Comment #1:

Thank you for submitting your package!

First --- could you list your dependencies (with their licenses and links to
their sites)?

Then, README and images lack copyright and license notices,
please check
https://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14414] Submission of GNUstep Non-FSF

2017-05-02 Thread Pavel Kharitonov
Follow-up Comment #19, task #14414 (project administration):

Thank you for fixing IMAGES_README!

> .gorm and .nib files are actually bundles, thus what counts is
> the directory containing those files, which are under program
> control and should not contain extraneous files (an editor might
> remove them on a open/save cycle or possible give an error).

Are you saying they are not parts of your source code?  Then why not remove
them?

> The README file is in this case in Resources/English.lproj/

These files only contain copyright and license notices, they don't say what
files they apply to.  I believe this is necessary.

Bundles/Account/English.proj has no such README at all.

Also, please remove (supposedly) backup files like
Documentation/IMAGES_README~.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14414] Submission of GNUstep Non-FSF

2017-05-01 Thread Pavel Kharitonov
Follow-up Comment #17, task #14414 (project administration):

Thank you!

Please note that my point was not how you could or couldn't split
a copyright notice, but whether what you split was a valid
copyright notice in the first place.

It looks like Documentation/IMAGES_README has a few typos,
these files are missing:

Bundles/Face/stamp.tiff
Bundles/Sending/English.lproj/SendingView.nib/delete_20.tiff
Bundles/Sending/MailIcon_send.tiff
Bundles/PGP/pgp-mail.tiff
Bundles/PGP/signed+encrypted_80.tiff
Bundles/Fonts/fonts.tiff

...and the tarball doesn't contain these files listed in it:

Bundles/Faces/stamp.tiff
Bundles/Fonts/Fonts.tiff
Bundles/PGP/signe+encrypted_80.tiff
Bundles/Receiving/MailIcon_send.tiff

Also, I recommend adding a full licensing notice for these files
to Documentation/IMAGES_README, not just saying "GPLv2 or later";
and the file is non-trivial, it should have a copyright and licensing
notices for itself.

Files like Bundles/Compose/English.lproj/ComposeView.nib/info.nib
and Bundles/Compose/English.lproj/ComposeView.nib/classes.nib still
have no copyright and license notices.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14166] Need Link for Tutorial - Facing issues with compatibility antis

2017-04-27 Thread Pavel Kharitonov
Follow-up Comment #2, task #14166 (project administration):

(it doesn't look like there is 'antis' package on Savannah)

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14166] Need Link for Tutorial - Facing issues with compatibility antis

2017-04-27 Thread Pavel Kharitonov
Update of task #14166 (project administration):

Category:None => Approved Projects to be
Reviewed
  Status:None => Cancelled  
 Assigned to:None => ineiev 
 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

This doesn't look like a submission of a package.

Cancelling.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14414] Submission of GNUstep Non-FSF

2017-04-25 Thread Pavel Kharitonov
Follow-up Comment #15, task #14414 (project administration):

> What would be invalid in that copyright line? Even the guide you cite states
that copyrights can be split over multiple lines if too long

It states copyright line can be split (for example, if there are many years).
The copyright notice still should look like "Copyright (C) year1, year2, year3
copyright-holder".

>Copyright (C) x1-x2 Author 1
> x3-x4 Author 2 

(Please note that authors are not relevant, it's copyright holders that
matter.)

The page I mentioned
 explains
that if there are multiple copyright holders, you can include copyright
notices for other holders (it doesn't say you could include other copyright
holders in the same notice).

Bundles/Clock/*.tiff don't seem to have copyright and license notices. 

Even image files and sound files should contain copyright notices and license
notices, if their format permits. Some formats do not have room for textual
annotations; for these files, state the copyright and copying permissions in a
README file in the same directory.


___

Reply to this item at:

  

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




[Savannah-register-public] [task #14414] Submission of GNUstep Non-FSF

2017-04-24 Thread Pavel Kharitonov
Follow-up Comment #12, task #14414 (project administration):

Thank you!

The second line in README still doesn't form a valid copyright notice, it
lacks the "Copyright (C)" part.

In files like Bundle/Clock/ClockController.h, FSF's address is twice outdated;
I recommend using the URL like the GPL HowTo suggests.

There are still files like Documentation/PREFERENCES that lack valid copyright
notices.

By the way, have you any deadline for this approval process?  If the tarball
be fixed one file a day, it may last two years.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14437] Submission of TouristTycoon

2017-04-23 Thread Pavel Kharitonov
Update of task #14437 (project administration):

  Status: In Progress => Cancelled  
 Open/Closed:Open => Closed 

___

Follow-up Comment #4:

No response; cancelling.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14485] Submission of otterbrowserarch

2017-04-23 Thread Pavel Kharitonov
Update of task #14485 (project administration):

  Status:None => Cancelled  
 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

Savannah doesn't host storage projects.  Other hosting services offer storage
space.  Please use them.

Cancelling.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14414] Submission of GNUstep Non-FSF

2017-04-22 Thread Pavel Kharitonov
Follow-up Comment #10, task #14414 (project administration):

> I went through all copyright notices of all source files, they had the same
issues as the Readme file. I amended that.
> Furthermore, the copyright and license attribution of the icon was wrong. I
fixed that. 

Thank you!

The copyright notice in GNUMail.xpm ("Copyright (C) 2000") is still invalid,
please check
https://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html

Also, the second line in README doesn't form a valid copyright notice, it
lacks the "Copyright (C)" part.

If you distribute some files under the LGPL, you should include a copy of that
license in your tarball; you don't (please note that you may redistribute
LGPLed works under the ordinary GPL, but then you should update the license
notice in those files).

> However, let's be reasonable: inserting a copyright and license statement in
a ChangeLog file is absurd, I have never seen that

(_Warning: that some of these pages are about 1Mbyte long_)
https://git.savannah.gnu.org/cgit/emacs.git/tree/ChangeLog.1
https://bitbucket.org/skypher/fdisk/src/94911b8cfd93cf8226584135fb9d753ab7582ded/ChangeLog?at=default
http://git.savannah.gnu.org/cgit/bison.git/tree/ChangeLog-2012
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob;f=ChangeLog;h=e555d07f67840cdd1ec6dcdba2bbf708daeb883c;hb=HEAD
https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=blob;f=ChangeLog-2011;h=01601fa61cb496ce343dd45848e20e590702d944;hb=HEAD

I don't see why it is absurd.  The texts of changelogs are copyrightable, and
if I redistribute copyrightable texts without explicit permission, I
technically violate copyright; if I technically violate copyright, under some
regimes I can end up in jail.

Do you want your users to be imprisoned?

> and the file needs to be essentially machine-creatable from the SVN commits.
It holds no further information and is not a support file to the project. 

Then you can just omit it.  If some tools require a file named ChangeLog, you
can add a non-copyrightable stub directing to VCS.

Now. All files should have valid copyright and license notices
.  Files like
Bundles/Clock/ClockController.h don't.

I wonder if you attached a wrong file.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14475] Submission of Dr. Theobold

2017-04-20 Thread Pavel Kharitonov
Update of task #14475 (project administration):

  Status:None => Done   
 Assigned to:None => ineiev 
 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

Thank you, approving.

I'd recommend adding copyright and license notices to README.txt to eliminate
the chance that you'll forget to add them when the file grows to copyrightable
sizes.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14414] Submission of GNUstep Non-FSF

2017-04-18 Thread Pavel Kharitonov
Follow-up Comment #8, task #14414 (project administration):

All files should have valid copyright and license notices.  The copyright
notices you've added to Documentation/README and GNUMail.xpm are not valid;
please check
https://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html for the
correct format of copyright notices.

Also, some files like ChangeLog still have no license and copyright notices. 
Please check all files in your tarball.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14471] Submission of Org Edna

2017-04-18 Thread Pavel Kharitonov
Follow-up Comment #3, task #14471 (project administration):

In license notices of org-edna-tests.el and org-edna.el, FSF's address is
provided instead of the URL where to find the GPL, I'd recommend to update
this.

Approving.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14471] Submission of Org Edna

2017-04-18 Thread Pavel Kharitonov
Update of task #14471 (project administration):

  Status: In Progress => Done   
 Open/Closed:Open => Closed 


___

Reply to this item at:

  

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




[Savannah-register-public] [task #14457] Submission of pyisabella

2017-04-17 Thread Pavel Kharitonov
Follow-up Comment #6, task #14457 (project administration):

I suggest that your packages don't belong to Savannah at all.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14471] Submission of Org Edna

2017-04-17 Thread Pavel Kharitonov
Update of task #14471 (project administration):

  Status:None => In Progress
 Assigned to:None => ineiev 


___

Reply to this item at:

  

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




[Savannah-register-public] [task #14471] Submission of Org Edna

2017-04-17 Thread Pavel Kharitonov
Follow-up Comment #1, task #14471 (project administration):

org-edna-tests.el and org-edna.el lack copyright notices
; their
"license notices" are misleading: they say they are not part of Emacs, and
provide license notices for Emacs (not for them).

Could you fix this?

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14472] Submission of GitAutoStar

2017-04-17 Thread Pavel Kharitonov
Update of task #14472 (project administration):

  Status:None => Cancelled  
 Assigned to:None => ineiev 
 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

Please provide a meaningful description; list your dependencies.

Cancelling.

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14444] Submission of Memcopy

2017-04-14 Thread Pavel Kharitonov
Follow-up Comment #15, task #1 (project administration):

You can use CVS  or enable
other version control systems in group settings
.

For further info, please see Savannah documentation,
https://savannah.nongnu.org/userguide/
https://savannah.gnu.org/maintenance/FrontPage/

___

Reply to this item at:

  

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




[Savannah-register-public] [task #14437] Submission of TouristTycoon

2017-04-13 Thread Pavel Kharitonov
Follow-up Comment #3, task #14437 (project administration):

If there is no further interest, I'll cancel this submission.

___

Reply to this item at:

  

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




  1   2   3   4   >