[task #16542] Submission of Ajla

[Ineiev]

Update of task #16542 (group administration):

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

___

Follow-up Comment #5:

Thank you, cancelling.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16540] Submission of Republishing Public Domain Books with Lisp

[Ineiev]

Follow-up Comment #3, task #16540 (group administration):


> The thing is that this is not just fiction, this is a proper program that is
programmed in a DSL (`#lang`) of Racket called Pollen[0]. If you were able to
get the source code, check the `pollen.rkt` file. I shall be adding a few of
those more, which would implement the typographical capacities of Pollen. So
the goal is to use the power of free software, and especially the dialect of
lisp in providing better typographical reproductions of classic literature.
Does this help in giving a better idea of the project? 

Yes, I hope so.

> The original work remains to be in the public domain, the changes that are
re-licensed according to CC-BY-SA 4.0 are the typographical and design changes
that were made in reproducing the copy/edition of the book(s). As the original
content is in public domain, it is totally feasible to make changes to it and
_relicense those changes_ accordingly.

Yes, provided the changes are copyrightable; still don't you find it
surprising when the copyright lines list persons who have little relation to
the authors?

> Particularly, the things that will be under CC-BY-SA would be the design
layout used in each format (PDF, EPUB, HTML/CSS) and the cover picture. I also
intend to add a foreword and appendix to the book, so they shall also be under
CC-BY-SA while the particular content of the book and its translation remain
safely under Public Domain.

I see.  The foreword is likely to be copyrightable, other things may or may
not.

> > I'm not sure if CC BY-SA 4.0 is technically incompatible with Savannah
hosting
> > requirements in this case, but releasing a work under confusing terms
isn't a
> > good practice.
> I am not sure which part of it is confusing,

You are going to release a work that is essentially in public domain under
different terms.

> but would like further comment. As far as GNU's compatibility goes, the
License Compatibility list from FSF[2] confirms that being  a copyleft license
it _is_ compatible with all versions of GPL as long as it is not used on
software, which I assure you it is not.

I'm really puzzled how you could interpret the entry you referred to this way.
 It clearly says CC BY-SA is incompatible with any GPL version but 3.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16542] Submission of Ajla

[Ineiev]

Follow-up Comment #3, task #16542 (group administration):


> The files that don't contain copyright and license notices are generated.

Files like README don't look like generated.

> Does copyright apply to generated files?

It depends.  If I generate a tarball from Emacs sources, it will be
copyrighted by the FSF.  If I generate a file with a command like *yes | head
-n 83521 > file*, then it will not be copyrightable; however, even when some
file is public domain or uncopyrightable, it's useful to add a note clarifying
that.

> For example, I took GNU binutils, I wrote a script that extracts the
encoding of ARM64 constants and I put the result to the files arm64-w.inc and
arm64-x.inc. Who owns the copyright of these files? Me? Binutils authors?
Nobody (because a table of numbers can't be copyrighted)? Please, describe how
to properly attribute copyright in cases like this.

Generally, the derived works inherit the copyright status of the works they
are derived from.

> I intend to use the domain www.ajla-lang.cz as the primary home page of the
Ajla project.
> 
> But I also need git hosting and I would use Savannah for that - Savannah
wouldn't be mirror or backup, it would be the main git repository for Ajla
(while the WWW homepage would be www.ajla-lang.cz) - is it OK to use it this
way?

If you need just Git, you could consider using a simpler service like
repo.or.cz.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16542] Submission of Ajla

[Ineiev]

Update of task #16542 (group administration):

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

___

Follow-up Comment #1:

A few files in your tarball miss valid copyright and license notices; in those
that do include a copyright notice, its form doesn't match what we use. 
Please check //savannah.gnu.org/maintenance/ValidNotices/.

[comment #0 original submission:]
> == Other Comments: ==
> I would like to host the Ajla git repository on Savannah.

We don't require all parts of the project to be hosted at Savannah, but we
expect that it will be used primarily (e.g. not as a mirror or backup).


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16542>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16538] Submission of Zaurbox

[Ineiev]

Follow-up Comment #6, task #16538 (group administration):

[comment #5 comment #5:]
> I have sent a new tarball, is it OK?

No, not really.

It seems to me, you have basic understanding of most things needed, but
couldn't collect all the pieces together yet.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16540] Submission of Republishing Public Domain Books with Lisp

[Ineiev]

Update of task #16540 (group administration):

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

___

Follow-up Comment #1:

The tarball URL you provided doesn't work for me, so I only can see the text
of your submission; generally, Savannah is a forge for software and
documentation, fiction is out of its scope.

Another general note is, the works in public domain are inherently
unrestricted, so applying any license to them must be legally void.  I'm not
sure if CC BY-SA 4.0 is technically incompatible with Savannah hosting
requirements in this case, but releasing a work under confusing terms isn't a
good practice.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16540>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16538] Submission of Zaurbox

[Ineiev]

Follow-up Comment #4, task #16538 (group administration):

Thank you!

Your new README.md is identical to the one packed in the original submission.

Please update sh.c as well; also, please
[//www.gnu.org/licenses/gpl-howto.html#license-files add the text version of
the GPL] to your tarball, that's the canonical format, and using it will make
life of your users easier.

(And of course you are aware that your
[//www.gnu.org/prep/maintain/html_node/License-Notices-for-Code.html an
overall copyright notice should be included in your README], aren't you?)

[comment #2 comment #2:]
...
> Oh, I forgot to update README...

Still the comment in your submission is quite misleading,

[comment #0 original submission:]
> I added "Neither the name[...]permission." clause to Expat license.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16538] Submission of Zaurbox

[Ineiev]

Update of task #16538 (group administration):

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

___

Follow-up Comment #1:

First, you should determine the license of your package.  Currently, your
source files say it's GPLv3 or later, while README.md says it's the Expat
license, and your submission mentions it's actually not the Expat license but
a license derived from it.

Then, the licenses are written to be followed.  When you copy other people's
licensed work, you should check the requirements and follow them.  In
particular, this applies to texor.c.  sh.c is a special case because the
original work is dedicated to public domain.  You correctly mention the
author, but I'd like to recommend additionally copying the exact text of the
dedication to the file.

Please read [//savannah.gnu.org/maintenance/ValidNotices/] once again; and
until you are really familiar with licensing issues, I suggest that you should
choose your licenses from our list, without any modifications.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16538>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16534] Submission of dr

[Ineiev]

Update of task #16534 (group administration):

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

___

Follow-up Comment #4:

No response; cancelling.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16537] Submission of Learn GNU Linux

[Ineiev]

Update of task #16537 (group administration):

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

___

Follow-up Comment #1:

In order to evaluate a submission, we need a tarball with something
substantial; even if it doesn't contain a complete functional package, we
should be able to get a general idea about it.

Please re-submit when you have something we could check; also, please list
licenses of your dependencies next time.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16537>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16534] Submission of dr

[Ineiev]

Follow-up Comment #3, task #16534 (group administration):

Still the package seems very simple to me.  May I suggest that you re-submit
it when it's clear that your program is big enough for a dedicated Savane
group?


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16534] Submission of dr

[Ineiev]

Update of task #16534 (group administration):

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

___

Follow-up Comment #1:

Your package is basically a short single file; its functionality can be
expressed with a line like

find $1 -maxdepth 1 -type d ! -name . -print


We discourage simplistic packages on Savannah.  They can be hosted on a single
web page and needn't a full-fledged Savannah group.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16534>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16532] Submission of Michael 'Mac' McDaniel

[Ineiev]

Update of task #16532 (group administration):

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

___

Follow-up Comment #1:

Your package is basically a short single file.  We discourage simplistic
packages on Savannah.  They can be hosted on a single web page and needn't a
full-fledged Savannah group.

Cancelling.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16532>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16530] Submission of uweb browser documentation for AOSP

[Ineiev]

Update of task #16530 (group administration):

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

___

Follow-up Comment #2:

No response; cancelling.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16530>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16511] Submission of Andesaurux

[Ineiev]

Update of task #16511 (group administration):

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

___

Follow-up Comment #7:

No response; cancelling.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16497] Submission of Andesaurux

[Ineiev]

Update of task #16497 (group administration):

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

___

Follow-up Comment #8:

No response; cancelling.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16511] Submission of Andesaurux

[Ineiev]

Follow-up Comment #6, task #16511 (group administration):

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


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16511] Submission of Andesaurux

[Ineiev]

Follow-up Comment #5, task #16511 (group administration):

Let us start with the minor issue: could we please proceed in the original
task #16497?


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16511] Submission of Andesaurux

[Ineiev]

Follow-up Comment #3, task #16511 (group administration):

I see; could we proceed in task #16497?  As an admin of Savannah, I can update
the license displayed on the main page of your package; however, I strongly
suggest that you choose the licenses from our list.  We can't evaluate new
licenses for compatibility with the GPL, and the GNU Project generally
discourages proliferation of licenses.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16511] Submission of Andesaurux

[Ineiev]

Update of task #16511 (group administration):

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

___

Follow-up Comment #1:

You re-submit the same package as in task #16497.  Why?


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16511>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16499] Submission of libcroco

[Ineiev]

Follow-up Comment #4, task#16499 (group administration):

[comment #2 comment #2:]
> Sure: I looked it up in the Copyright file of the top-level directory of
libxml2. The URL is
https://gitlab.gnome.org/GNOME/libxml2/-/raw/master/Copyright?ref_type=heads=false

Thank you.  That's the Expat license.

> Wikipedia says that it is a form of the MIT license:
https://en.wikipedia.org/wiki/Libxml2

Wikipedia isn't sufficiently reliable source for our purpose, neither for
naming licenses, nor for referring to licensing terms of software.

> Can I make the changes in a local git repository, and then you (or some
other Savannah admin) imports the git repository with the original history
plus with my additional commits?

Yes; you'll be able to push it yourself.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16499] Submission of libcroco

[Ineiev]

Update of task#16499 (group administration):

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

___

Follow-up Comment #1:


> MIT license

[//www.gnu.org/licenses/license-list.html#Expat MIT has used many licenses]. 
Can you specify the license, preferably with a link to the place where the
package declares it?

Then, the COPYRIGHTS file says,


Except where otherwise noted in the source code all the files are:

 Copyright (C) 2003-2004 Dodji Seketeli.  All Rights Reserved.


This means proprietary software.  Such things need fixing before the package
is hosted on Savannah.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16499>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16497] Submission of Andesaurux

[Ineiev]

Follow-up Comment #7, task#16497 (group administration):

I agree that the intentions matter; however, the actions are more important.

The question at hand is whether your package is likely to follow our hosting
requirements.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16497] Submission of Andesaurux

[Ineiev]

Follow-up Comment #4, task#16497 (group administration):

Your new submission still has so many issues, I even have to doubt that you've
ever read our hosting requirements.  You misidentified the license your
package uses, your files miss valid copyright and license notices, your README
says it's [//www.gnu.org/philosophy/floss-and-foss.html open source].

Frankly speaking, I'm pessimistic.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16484] Submission of Andesaurux Kernel

[Ineiev]

Update of task#16484 (group administration):

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

___

Follow-up Comment #5:

Cancelling per task #16497


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16497] Submission of Andesaurux

[Ineiev]

Follow-up Comment #3, task#16497 (group administration):


> My previous request was to publish my OS(at that time it was a kernel), but
forgot to list dependencies

I see; so I'm cancelling your previous request.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16497] Submission of Andesaurux

[Ineiev]

Update of task#16497 (group administration):

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

___

Follow-up Comment #1:


> It is written in C(mostly), it is aimed at POSIX-compatability and being
very lightweigh(imagine that OS uses only 3 MB of RAM, it means that it will
work even on computer from 1985).

Probably you mean 1995.  In 1985, many computers had a 8-bit MCU and less than
64 kB RAM.

Now, to the point: how does this relate to your previous request, task #16484?


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16497>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16495] Submission of chirag gadhiya

[Ineiev]

Update of task#16495 (group administration):

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


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16495>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16484] Submission of Andesaurux Kernel

[Ineiev]

Follow-up Comment #4, task#16484 (group administration):

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


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16493] Submission of Emirhan Ucan

[Ineiev]

Update of task#16493 (group administration):

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

___

Follow-up Comment #1:

Savannah is a software forge for [//www.gnu.org/philosophy/free-sw.html free
software].  We don't host packages that identify themselves as
[//www.gnu.org/philosophy/open-source-misses-the-point.html open source].

Besides that, we don't host software with proprietary dependencies.

Cancelling.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16493>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16482] Submission of brp - portable preprocesser

[Ineiev]

Update of task#16482 (group administration):

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

___

Follow-up Comment #5:

Thank you, cancelling.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16485] Submission of NetUseMod

[Ineiev]

Update of task#16485 (group administration):

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

___

Follow-up Comment #12:

Sorry for wasting your time.

Cancelling.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16485] Submission of NetUseMod

[Ineiev]

Follow-up Comment #10, task#16485 (group administration):

Thank you!

[comment #9 comment #9:]
> Some packaging rules changed in recent year which I was not aware of.

Not really.

> I added other tool licenses and a README in the image directory for
copyright notice.
> (the image is not important - just to show small logo in browser tab.)

It's important enough to be included in the tarball.  Could you use a complete
license notice as recommended in the GPL?  There should be no ambiguities left
about what copyright and license notices applies to the image files and to
README itself.

Since your tarball doesn't include parts of your dependencies, including their
licenses may be confusing.  That's not what I wanted, though I may have been
unclear.  I wanted you to tell, in this discussion, what their licensing terms
are, exactly.

Then, I could point to the files that still lack the copyright and license
notices, but the tarball is so small that it shouldn't be hard for you to find
them.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16489] Submission of ArcadeFighter Game Engine

[Ineiev]

Follow-up Comment #5, task#16489 (group administration):


> Regarding my previous submission, like I said, I do understand my mistake
and I do understand why you take it seriously, but it will take a wile to stop
using some terms as I have never been formally introduced to them before and
have been using as synonym so far.

Yes; and one of the hosting requirements is using the right terms for a few
things.  Until the maintainers get used to it, they can't fulfill that
requirement.

> You don't have to trust my word for it, If you take a look at the README.md
file from my submission you will se I even placed a remark about this very
issue under the License section. It really was just a relapse of my part.

I did read it, and even that [//www.gnu.org/philosophy/floss-and-foss.html is
not what we actually expect].

> Regarding the current state of the project, I'm apply for the non-gnu
repository and I believe I have met the criteria under
[https://savannah.gnu.org/register/requirements.php] and
[https://savannah.gnu.org/maintenance/HowToGetYourProjectApprovedQuickly/].

If you can't identify the issues, you surely aren't ready to follow the
requirements.

> Anyway, I'm here for the learning process, give me the list of worst
problems with my code and I'll do my best to fix it properly before trying to
submit it again.

Applying for hosting isn't like entering a school, it's more like an exam. 
You have too much to learn.

> The project is still on its early stages, so you can also feel free to send
me any other minor suggestions you have to make it more to the Savannah
standards,

Savannah can't afford continually fixing all hosted packages.  We have to rely
on package maintainers.

> I will be sure to add them to the todo list.

...and effectively never do (that's not necessarily because you are not
serious about them---some issues may turn out just very hard to resolve). 
Still I don't think this is what complying with requirements means.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16489] Submission of ArcadeFighter Game Engine

[Ineiev]

Follow-up Comment #3, task#16489 (group administration):

[comment #2 comment #2:]
> Because I learned my lesson and still want to use Savannah for my project.

I see, thanks for your clarifications.

> I did explain the misunderstanding on the last time, but had no follow up.

I'm sorry, I think I had no time.

> What are you saying? That I'm banned or that I need to state a better
reason?

You filed exactly the same submission again, didn't you?  In my book, that
doesn't count as learning one's lesson.

And to tell the truth, your tarball has more incompatibilities with the
Savannah hosting requirements, they wouldn't be easy to fix.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16489] Submission of ArcadeFighter Game Engine

[Ineiev]

Update of task#16489 (group administration):

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

___

Follow-up Comment #1:

This submission was cancelled.  Why do you re-submit?


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16489>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16485] Submission of NetUseMod

[Ineiev]

Follow-up Comment #8, task#16485 (group administration):

[comment #5 comment #5:]
> I am not including anything from procmail, perl dancer2 in my project.

Good point; understanding how the dependencies relate to your package is
important, however, it's also essential to understand how those dependencies
are licensed.

[comment #6 comment #6:]
> removed Image.

This solution calls for clarification.  If the package needs that file, it's
likely to be re-added at some point.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16488] Submission of ArcadeFighter Game Engine

[Ineiev]

Update of task#16488 (group administration):

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

___

Follow-up Comment #1:

Savannah is a software forge for [//www.gnu.org/philosophy/free-sw.html free
software].  We don't host packages that identify themselves as
[//www.gnu.org/philosophy/open-source-misses-the-point.html open source].

Cancelling.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16488>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16485] Submission of NetUseMod

[Ineiev]

Follow-up Comment #4, task#16485 (group administration):

[comment #2 comment #2:]
> done
> 
> (file #55561)

Thank you, please check for missing copyright and license notices again.

Please note that images also require copyright and license notices. See
http://www.gnu.org/prep/maintain/maintain.html#Copyright-Notices for more
information.

[comment #3 comment #3:]
> procmail - https://github.com/BuGlessRB/procmail...
> perl Dancer2 - https://metacpan.org/dist/Dancer2

Why don't you list their licenses?  It may make people think that you either
can't identify them, or just don't care.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16482] Submission of brp - portable preprocesser

[Ineiev]

Follow-up Comment #3, task#16482 (group administration):

[comment #2 comment #2:]
> > Please list your dependencies with their licenses (ideally, with links to
their distribution terms).
> 
> --> Delete unnecessary files and descriptions that are not related to
dependencies in ./external, brp is all original script.
> --> Unify the license of each file from GPLv3+ to AGPLv3+.

This doesn't address my request, I'm sorry I didn't express it clearly.  In
order to evaluate your package, I need to check its dependencies.

> > Please make sure that all copyrightable files in your tarball have
[//savannah.gnu.org/maintenance/ValidNotices/ valid copyright and license
notices].
> 
> --> Add license notice to files with less than 10 lines of code, excluding
notes. If I have overlooked something, please let me know the file name.

It looks like you have a wrong idea of copyrightability.  Please read the
documentation I refer to.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16461] Submission of sinaps is not a password safe

[Ineiev]

Update of task#16461 (group administration):

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

___

Follow-up Comment #10:

It looks like the used tools make it unreasonably hard do comply with Savannah
hosting requirements.

Cancelling since no response followed.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16485] Submission of NetUseMod

[Ineiev]

Update of task#16485 (group administration):

  Depends on: => bugs #65157


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16485] Submission of NetUseMod

[Ineiev]

Update of task#16485 (group administration):

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

___

Follow-up Comment #1:

Please make sure that all copyrightable files in your tarball have
[//savannah.gnu.org/maintenance/ValidNotices/ valid copyright and license
notices].

Please list your dependencies with their licenses (ideally, with links to
their distribution terms).

Also, please include an exact copy of the GPL from
https://www.gnu.org/licenses/.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16485>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16454] Submission of GNU's Debbugs

[Ineiev]

Update of task#16454 (group administration):

 Open/Closed:Open => Closed 


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #13308] Submission of SlashNerd

[Ineiev]

Update of task#13308 (group administration):

  Status:  Wait reply => Cancelled  
 Assigned to: agn => None   
 Open/Closed:Open => Closed 

___

Follow-up Comment #19:

I'm sorry, we failed to evaluate this package that time; if you are still
interested, please re-submit.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #13309] Submission of Slashnerdcode

[Ineiev]

Update of task#13309 (group administration):

  Status:  Wait reply => Cancelled  
 Assigned to: agn => None   
 Open/Closed:Open => Closed 

___

Follow-up Comment #2:

I'm sorry, we failed to evaluate this package that time; if you are still
interested, please re-submit.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #14222] Submission of Ad Reaper

[Ineiev]

Update of task#14222 (group administration):

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

___

Follow-up Comment #3:

Your package is basically two short files.  We discourage simplistic packages
on Savannah.  They can be hosted on a single web page and needn't a
full-fledged Savannah group.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?14222>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16484] Submission of Andesaurux Kernel

[Ineiev]

Update of task#16484 (group administration):

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

___

Follow-up Comment #3:

Please list your dependencies with their licenses (ideally, with links to
their distribution terms).

Please make sure that all copyrightable files in your tarball have
[//savannah.gnu.org/maintenance/ValidNotices/ valid copyright and license
notices].

Since your package are licensed permissively, there is no need in the LICENSE
file because the complete license text should be included in every file.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16484>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16482] Submission of brp - portable preprocesser

[Ineiev]

Update of task#16482 (group administration):

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

___

Follow-up Comment #1:

Please list your dependencies with their licenses (ideally, with links to
their distribution terms).

Please make sure that all copyrightable files in your tarball have
[//savannah.gnu.org/maintenance/ValidNotices/ valid copyright and license
notices].


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16482>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16477] Submission of ajlisp

[Ineiev]

Update of task#16477 (group administration):

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

___

Follow-up Comment #5:

Thank you, approving.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16477] Submission of ajlisp

[Ineiev]

Follow-up Comment #3, task#16477 (group administration):

[comment #2 comment #2:]
> I have updated it so that the files in ex/ also have the license and
copyright notices

Thank you!

> and I also added a copyright notice to the README file.

Copyrightable files should have both copyright and license notices.  Why
didn't you add a license notice to it?


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16480] Submission of Memlernilo

[Ineiev]

Update of task#16480 (group administration):

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

___

Follow-up Comment #1:

Your package is basically a short single file.  We discourage simplistic
packages on Savannah.  They can be hosted on a single web page and needn't a
full-fledged Savannah group.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16480>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16481] Submission of Automaton

[Ineiev]

Update of task#16481 (group administration):

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

___

Follow-up Comment #1:

Your package is a short single file.  We discourage simplistic packages on
Savannah.  They can be hosted on a single web page and needn't a full-fledged
Savannah group.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16481>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16479] Submission of Memlernilo

[Ineiev]

Update of task#16479 (group administration):

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

___

Follow-up Comment #1:

Please resubmit your package in English.

English is the only language the whole Savannah team understands,
and it is required for archiving and transparency purposes.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16479>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16477] Submission of ajlisp

[Ineiev]

Update of task#16477 (group administration):

 Assigned to:None => ineiev 

___

Follow-up Comment #1:

Please make sure that all copyrightable files in your tarball have
[//savannah.gnu.org/maintenance/ValidNotices/ valid copyright and license
notices].


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16477>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16473] no email got sent regarding Savannah #65092

[Ineiev]

Update of task#16473 (group administration):

Category:None => Approved Projects to be
Reviewed


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16468] Submission of Bash Bear Trap

[Ineiev]

Update of task#16468 (group administration):

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

___

Follow-up Comment #1:

Your package is basically a relatively short single file.  We discourage
simplistic packages on Savannah.  They can be hosted on a single web page and
needn't a full-fledged Savannah group.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16468>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16469] can't upload to download area by scp or sftp

[Ineiev]

Update of task#16469 (group administration):

Category:None => Approved Projects to be
Reviewed

___

Follow-up Comment #1:

[//savannah.nongnu.org/news/?id=10563 SFTP was disabled] recently.

scp -r works for me; your diagnostics look like an access issue, please check
the output of ssh -v jkraehem...@dl.sv.nongnu.org, further troubleshooting at
//savannah.nongnu.org/maintenance/SshAccess/


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16461] Submission of sinaps is not a password safe

[Ineiev]

Follow-up Comment #9, task #16461 (project administration):


> Ok, so the documentation part is much tougher than I expected. Thank you for
all the input and guidance. Let me try to organize it a bit, please comment on
my thoughts.
> 
> 1. I currently use doxygen to generate "HTML output". This is the term that
is used by doxygen itself, but it includes HTML, css, javascript, png and
*.md5 and *.map files.

What category includes the *.svg files?

>   a) The latter two are intermediate files and not part of the documentation
so I do not see the necessity to put in notices.

Since they are not part of the documentation, don't you see the necessity to
exclude them from the tarball?

>   b) The css and javascript files are boilerplate so I don't think I can or
should put a copyright in there. I am not sure about a license notice though.

The point you have here is, there are files in the wild you can't add legal
notices to---for example, proprietary files.  However, that doesn't override
the Savannah requirement for all copyrightable files included to have valid
copyright and license notices.

Also, looking at files like doc/doxygen-header.html, it may seem that you
don't fully realize what you said here.

> If you think I should include one, I can do it.

We can't continually monitor all the packages we host on Savannah, to say
nothing of fixing the new issues they may have.  You must be able and willing
to think yourself.

>   c) The HTML files already contain copyright and license notices.

Have you verified that, e.g. using a command like the following?


find doc/html/ -type f -name \*.html -exec less -N {} \;


Many files in doc/html/search/ have no notices.

>   d) The png files are also generated from the source code so I put a note
in the README to declare their license.

Do you mean, from the source code of your package?  Can you explain how a file
like folderopen.png was generated from it?

> 2. Just to clairfy: I think all the files mentioned above make up one
particular type of a "produced document" to which the GPLv2 of doxygen does
not apply.

Let us discuss the points that led you to such conclusion (once more omitting
the question about the version of the GPL).

> 3. I see that lynx does not render the menus; I added a direct link so the
license will be accessible.

Nice; perhaps it would be consistent to add a link to it not only to the "main
page" (by the way, index.html seems to include the license notice, but its
footer still surprisingly refers to "main page").

Now on the license notice itself in doc/html/index.html#autotoc_md6.  It says
that the copies of code in the documentation are not covered by the FDL, but
by GPLv3.  This is confusing in at least two ways:

1. The users may think that they have a GPLv3-only package.
2. The non-FDL'ed parts that are not clearly and explicitly separated from the
FDL'ed parts.

But the main problem is, such combination makes your documentation proprietary
because it mixes works under incompatible licenses, the FDL and the GPL.

> 4. Regarding doxygen.conf: Now that I have dropped all boilerplate, there is
no copied expression in there because all of the remaining settings were
handwritten after reading the documentation.

Dropping the boilerplate implies that it was there at some point, which in
turn suggests that the result was derived from the original file.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16461] Submission of sinaps is not a password safe

[Ineiev]

Follow-up Comment #7, task #16461 (project administration):

[comment #6 comment #6:]
> 
> > > Yes, I forgot to also license the generated html files. I just added the
notices.
> > 
> > Did I say, "HTML"?  Do you mean HTML?  And a question with an asterisk:
are all added notices valid?
> The HTML documentation is the only one that I generated, so I assumed that's
what you were talking about.

So no, we don't refer to the same thing when we speak of "HTML."  By HTML, I
mean text files of the specific format standardized by the W3C.  Again, I
didn't say, "HTML files." I said, "all copyrightable files."

> The doxygen webpage states the following: "Documents produced by doxygen are
derivative works derived from the input used in their production; they are not
affected by this license."
> My understanding is that I can choose any license for the produced
documents. If that was not the case, using doxygen would force me to also use
GPL...

And what are the "produced documents"?  If we assume that it must be something
that isn't derived from Doxygen, then I can only suggest that it may be a
snapshot of a page as rendered in a browser---which is definitely not what the
tarball is to contain.

> ...v2.

The license versions of Doxygen and other dependencies will be the next issue
to resolve.

> > I see neither the tree view nor the top menu with my browser.
> 
> Hmm... just to be on the same page: Are we talking about the generated
HTML-documentation? Out of curiosity and to trouble shoot: Which browser do
you use?

Just to be on the same page:


tar xzf sinaps_2.tgz && lynx file://`pwd`/sinaps/doc/html/index.html


> > > I dropped all default lines and kept only the ones I changed; then, it
shouldn't be an issue.
> > 
> > Why not?  The file is still derived, isn't it?
> 
> Well, ... technically it is.

Why just technically?

> But taking pieces from the doxygen manual to construct a doxygen.conf is
also derived, isn't it?

It depends on the nature of the "taking pieces": when one takes expressions,
it makes a derivative; when one takes ideas, it doesn't.

For the record, the GNU Project
[//www.gnu.org/prep/maintain/html_node/License-Notices-for-Code-Examples.html
releases examples in manuals under an additional license].

> I suppose the easy way out is to strip off the doxygen.conf and generated
documentation and leave it to interested people to run doxygen themselves.

It doesn't matter who runs the compiler.  The package should take care to make
the result GFDL-compatible.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16461] Submission of sinaps is not a password safe

[Ineiev]

Follow-up Comment #5, task #16461 (project administration):

[comment #4 comment #4:]
> Yes, I forgot to also license the generated html files. I just added the
notices.

Did I say, "HTML"?  Do you mean HTML?  And a question with an asterisk: are
all added notices valid?

> The section containing the GNU Free Documentation License can be found in
the tree view on the left-hand side or from "Related Pages" in the top menu.

I see neither the tree view nor the top menu with my browser.

> Regarding doxygen.conf: Are you concerned that the file should inherit the
license of doxygen because of all the boilerplate code?

You are right.

> I dropped all default lines and kept only the ones I changed; then, it
shouldn't be an issue.

Why not?  The file is still derived, isn't it?


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16461] Submission of sinaps is not a password safe

[Ineiev]

Follow-up Comment #3, task #16461 (project administration):

Thank you!

When adding the generated documentation, didn't you forget that all
copyrightable files should have valid copyright and license notices?  While at
it: the license notice mentions a certain section, but I failed to find it.

Also, are you sure the copyright notice in doxygen.conf is valid?


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16438] Submission of QStarDict

[Ineiev]

Update of task #16438 (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 Savannah
https://savannah.nongnu.org/

[task #16461] Submission of sinaps is not a password safe

[Ineiev]

Update of task #16461 (project administration):

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

___

Follow-up Comment #1:

Please identify licenses of your dependencies, including the versions of the
licenses.

Then, doxygen.conf is copyrightable, but has no copyright and license
notices.

At last, README.md mentions further documentation, but the tarball misses it. 
Being GFDL-compatible is a requirement for the documentation, so probably it
will need more work.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16461>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16460] Submission of jstack

[Ineiev]

Update of task #16460 (project administration):

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

___

Follow-up Comment #1:

We expect to be used primarily and not as a back-up.

Cancelling.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16460>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16459] Submission of All Call TCP/IP-over-HTTP System

[Ineiev]

Update of task #16459 (project administration):

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

___

Follow-up Comment #6:

Thank you, cancelling.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16452] Submission of SolarDevs

[Ineiev]

Update of task #16452 (project administration):

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

___

Follow-up Comment #5:

No response; cancelling.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16459] Submission of All Call TCP/IP-over-HTTP System

[Ineiev]

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

[comment #3 comment #3:]
> 
> With respect to one file, protocol.txt, I could use some advice.  It is not
part of the program per se, it is the protocol I wrote which the program
implements.  I'm not sure a protocol (which one does not want altered) is
appropriate for GPL or FDL license. When there is more documentation, I can
included the protocol as an invariant section.  Until then, do you have a
suggestion?

Let's start with clarifying why it can't be an invariant section.  Do you have
any ideas yourself?

> FreePascal: https://wiki.lazarus.freepascal.org/FPC_modified_LGPL
> LGPL v2.0 with static library linking exception (similar to GCC and other
runtime libraries). A page explaining their license and rationale is here:
https://wiki.lazarus.freepascal.org/licensing

Thank you!

> a vanilla MIT license.

It looks like we don't listen to each other.  Too bad.

> DIMime: I'm not using it as a library, so referencing it as such was not
really correct.  I modified and incorporated one file from it into my project.
 With the written permission of the author, I was able to license this file as
GPL v3.0.  That is noted in the file base64url.pas.   Its history, original
license and copyright, and current status are noted there.

I'm not convinced the result of such integration is
GPLv3-or-later-compatible.

The notice only says, the file was allowed to be used in a package licensed
under the GPL 3.0, and that allows for a range of interpretations, including
the permission for private use only; and at any rate, it says nothing about
the versions of the GPL higher than 3.0.

> It was originally released under the MPL v1.1, which I understand that GNU
considers GPL compatible

Could you tell where the GNU Project says MPL v1.1 is GPL-compatible?


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16438] Submission of QStarDict

[Ineiev]

Follow-up Comment #3, task #16438 (project administration):

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


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16458] Submission of util-ironclad

[Ineiev]

Update of task #16458 (project administration):

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

___

Follow-up Comment #2:

Adding the ironclad/util-ironclad.git repository to Ironclad and cancelling,
per
<18GnBzqIZtTMtxBxDPNK6eW-Uf5Tw9zKiIUFxe84AG7P2prCBs1qJez-SeLpFU0G1Xjs_qKeaszMtlvPoqUWHMKBGwO0gz2kmkx6uOWUB5g=@protonmail.com>
at savannah-register-public@.

You can edit repository descriptions at
https://savannah.nongnu.org/git/admin/?group=ironclad


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16459] Submission of All Call TCP/IP-over-HTTP System

[Ineiev]

Follow-up Comment #2, task #16459 (project administration):


[comment #1 comment #1:]
> Please make sure that all copyrightable files in your tarball have
[//savannah.gnu.org/maintenance/ValidNotices/ valid copyright and license
notices].

While at it, please use the form of the license notice the GPL recommends.  In
your tarball, the notices include a very old FSF's postal address.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16459] Submission of All Call TCP/IP-over-HTTP System

[Ineiev]

Update of task #16459 (project administration):

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

___

Follow-up Comment #1:

Could you be more specific when listing licenses of your dependencies?  In
particular, which version of the LGPL does Free Pascal use?  Also, "MIT
license" doesn't [//www.gnu.org/licenses/license-list.html#Expat identify a
license unambiguously]: people use it to refer a number of various licenses. 
It would be helpful if you provided links to pages where each dependency
specifies its license.  I failed to find out the licensing terms of DIMime.

Then, please note that Savannah is GNU Project's software forge.  Therefore,
we require that people [//www.gnu.org/gnu/why-gnu-linux.html give our work due
credit] when hosting their packages here; in particular, they should
[//www.gnu.org/gnu/gnu-linux-faq.html call the operating system GNU/Linux
rather than just "Linux"].

Please make sure that all copyrightable files in your tarball have
[//savannah.gnu.org/maintenance/ValidNotices/ valid copyright and license
notices].


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16459>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16455] Submission of Glitchapp productions

[Ineiev]

Update of task #16455 (project administration):

   Should be Finished on: Mon 15 Jan 2024 06:00:00 AM UTC => Tue 31 Oct 2023
12:00:00 AM UTC
  Status:   Need Info => Cancelled  
 Assigned to:   carlc => ineiev 
 Open/Closed:Open => Closed 

___

Follow-up Comment #6:

I'm afraid, we aren't in a position to approve your package at Savannah.  We
rely on package maintainers to keep the proper legal status of their packages,
which requires understanding basics of free software licensing.  Without that,
we are extremely likely to end up having proprietary software hosted at
Savannah.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16455>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16458] Submission of util-ironclad

[Ineiev]

Update of task #16458 (project administration):

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

___

Follow-up Comment #1:

First, note that "the MIT license" doesn't
[//www.gnu.org/licenses/license-list.html#Expat identify a license
unambiguously]: people use it to refer a number of various licenses.  What
mlibc uses looks like the Expat license.  Please be more specific when
discussing such matters.

I would approve it, but since this package is very closely related, have you
considered adding another git repository to Ironclad instead of creating a new
Savannah group?


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16458>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16455] Submission of Glitchapp productions

[Ineiev]

Update of task #16455 (project administration):

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

___

Follow-up Comment #3:

Thank you!

One of your licenses is GPLv2-only; it means that the GPLv2 shall apply to
your work and its derivatives, so one can't use third-party code released
under GPLv3-or-later in it.  In other words, your package is
GPLv3-incompatible, therefore it doesn't meet our hosting requirements.

Cancelling.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16452] Submission of SolarDevs

[Ineiev]

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

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


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16445] Submission of Brigham Keys

[Ineiev]

Update of task #16445 (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 Savannah
https://savannah.nongnu.org/

[task #16455] Submission of Glitchapp productions

[Ineiev]

Update of task #16455 (project administration):

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

___

Follow-up Comment #1:

Please note that Savannah is GNU Project's software forge.  Therefore, we
require that people [//www.gnu.org/gnu/why-gnu-linux.html give our work due
credit] when hosting their packages here; in particular, they should
[//www.gnu.org/gnu/gnu-linux-faq.html call the operating system GNU/Linux
rather than just "Linux"].

Then, please [//www.gnu.org/licenses/identify-licenses-clearly.html identify
the licenses of your package and its dependencies clearly].  The words "MIT
license" are ambiguous because MIT released software under various licenses.

Also, I can't download your tarball; however, from the few files you linked to
I suggest that you should use the exact form of the license notice the GPL and
www.gnu.org recommend, without replacing any parts with other texts.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16455>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16438] Submission of QStarDict

[Ineiev]

Update of task #16438 (project administration):

 Assigned to:   carlc => ineiev 

___

Follow-up Comment #2:

Please make sure that all copyrightable files in your tarball have
[//savannah.gnu.org/maintenance/ValidNotices/ valid copyright and license
notices].

Also, note that Savannah is GNU Project's software forge.  Therefore, we
require that people [//www.gnu.org/gnu/why-gnu-linux.html give our work due
credit] when hosting their packages here; in particular, they should
[//www.gnu.org/gnu/gnu-linux-faq.html call the operating system GNU/Linux
rather than just "Linux"].




___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16438>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16452] Submission of SolarDevs

[Ineiev]

Follow-up Comment #3, task #16452 (project administration):

Thank you.

You needn't create another submission, I can modify the current one if you
tell me.

In your new tarball some copyrightable files still miss valid copyright or
license notices (or both).  Can you check again?

What about naming the OS?


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16452] Submission of SolarDevs

[Ineiev]

Update of task #16452 (project administration):

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

___

Follow-up Comment #1:

First, please be careful with
[//www.gnu.org/licenses/identify-licenses-clearly.html identifying the
licenses of your dependencies] (in particular, GCC and make are distributed
under the GPLv3 "or later").  If you don't, you are likely to end up with a
package having major licensing issues.

Then, please make sure that all copyrightable files in your tarball have
[//savannah.gnu.org/maintenance/ValidNotices/ valid copyright and license
notices], including supporting text files.  For images, the copyright and
license notices should be written in a README file in the same directory with
the files in question.

Also, please note that Savannah is GNU Project's software forge.  Therefore,
we require that people [//www.gnu.org/gnu/why-gnu-linux.html give our work due
credit] when hosting their packages here; in particular, they should
[//www.gnu.org/gnu/gnu-linux-faq.html call the operating system GNU/Linux
rather than just "Linux"].  Is it possible for you to make sure you comply
with this requirement?

At last, the "Unix name" of new groups should be reasonably descriptive;
"solar" sounds too generic.  Can you suggest a better name?


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16452>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16445] Submission of Brigham Keys

[Ineiev]

Follow-up Comment #3, task #16445 (project administration):

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


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16428] Submission of imaze - multi-player action game for X11

[Ineiev]

Update of task #16428 (project administration):

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

___

Follow-up Comment #5:

No response; cancelling.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16451] Submission of frpbruteforcer

[Ineiev]

Update of task #16451 (project administration):

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

___

Follow-up Comment #1:

Your package is a single very short file.  We discourage simplistic packages
on Savannah.  They can be hosted on a single web page and needn't a
full-fledged Savannah group.

Cancelling.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16451>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16425] Submission of flet - evaluator of arithmetic floating point expressions

[Ineiev]

Update of task #16425 (project administration):

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

___

Follow-up Comment #5:

No response; cancelling.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16445] Submission of Brigham Keys

[Ineiev]

Update of task #16445 (project administration):

  Status:None => In Progress


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16445] Submission of Brigham Keys

[Ineiev]

Update of task #16445 (project administration):

 Assigned to:   carlc => ineiev 

___

Follow-up Comment #2:

The name and system name of your package ("Birgham Keys" and
"talosworkstation") don't look reasonable; could you suggest better ones?

Then, "MIT license" is a misleading term because MIT has used many different
licenses; can you name the license correctly?

At last, one of files in your tarball is licensed under the LGPL, but no copy
of that license is included in the tarball; could you fix that?


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16445>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16442] Submission of Snaptik

[Ineiev]

Update of task #16442 (project administration):

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


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16442>

___
Message sent via Savannah
https://savannah.nongnu.org/

Re: [task #16428] imaze - multi-player action game for X11

[Ineiev]

[off-tracker]

On Thu, Aug 31, 2023 at 06:49:03PM -0400, Corwin Brust wrote:
> 
> In particular, I don't understand the meaning of the "all rights
> reserved" language preceding the (BSD 3 clause plus protecting the name of the
> software from use by others, is it?) license.

"All rights reserved" does sound inconsistently and confusingly,
but I think it doesn't override the subsequent license; I tend
to read it like "...reserved unless granted hereby", which is
what the copyright law does, anyway. 

Still this is an issue that would be nice to get fixed.  We rely on
package maintainers to keep their packages in a proper state
from the legal viewpoint, so they should apply the legal notices
meaningfully.


signature.asc
Description: PGP signature

[task #16429] Submission of Free software

[Ineiev]

Update of task #16429 (project administration):

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

___

Follow-up Comment #1:

The license of your package is incompatible with our hosting requirements.

Cancelling.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16429>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16427] [SPAM] Submission of Raphael s

[Ineiev]

Update of task #16427 (project administration):

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


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16427>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16425] Submission of flet - evaluator of arithmetic floating point expressions

[Ineiev]

Follow-up Comment #3, task #16425 (project administration):

Please list the problems you seem to solve, and explain how you solved them.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16425] Submission of flet - evaluator of arithmetic floating point expressions

[Ineiev]

Update of task #16425 (project administration):

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

___

Follow-up Comment #1:

The issues raised in task #16414 weren't addressed; please check again.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16425>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16422] Submission of DEW Browser

[Ineiev]

Update of task #16422 (project administration):

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

___

Follow-up Comment #2:

The submitting account removed itself; cancelling.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16414] Submission of flet c lib for

[Ineiev]

Update of task #16414 (project administration):

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

___

Follow-up Comment #5:

No response; cancelling.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16422] Submission of DEW Browser

[Ineiev]

Update of task #16422 (project administration):

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

___

Follow-up Comment #1:

Please list your dependencies with their licenses (ideally, with links to
their distribution terms).

Please use the exact license text as published on
https://www.gnu.org/licenses/agpl-3.0.txt.

Please make sure that all copyrightable files in your tarball have
[//savannah.gnu.org/maintenance/ValidNotices/ valid copyright and license
notices].


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16422>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16414] Submission of flet c lib for

[Ineiev]

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

[comment #3 comment #3:]
> Please identify the licenses of your dependencies clearly...

Please read the links. I added them on purpose.

> This is the LICENSE of flex project
https://github.com/westes/flex/blob/master/COPYING

I can't read that page.  What is the license?

> I have attached the new project tarball file. In the folder there are also
gifs and docuemntation of a mvp as possibile implementation as Bash's builtin
function.

I'm sorry, the new file doesn't address my remark.

> Flet

This is as short and non-descriptive as the previous one.  Can you suggest a
better name?


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16416] Submission of Pharmacy inventory and billing system

[Ineiev]

Update of task #16416 (project administration):

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

___

Follow-up Comment #1:

Your package is a relatively short single file.  We discourage simplistic
packages on Savannah.  They can be hosted on a single web page and needn't a
full-fledged Savannah group.


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16416>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16414] Submission of flet c lib for

[Ineiev]

Update of task #16414 (project administration):

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

___

Follow-up Comment #1:

Please [//www.gnu.org/licenses/identify-licenses-clearly.html identify the
licenses of your dependencies clearly].  There is
[//www.gnu.org/licenses/bsd.html no "BSD" license]: some licenses with "BSD"
in their name are GPL compatible, other aren't.

Then, it looks like your tarball doesn't unpack correctly for me: the
resulting directory includes a lot of auxiliary files.  Could you make sure it
only contains necessary files, without backups, artifacts of non-standard
attributes and Git data?

At last, group names should be reasonably descriptive, rather than terse
abbreviations or confusingly general.  Can you suggest a better name?


___

Reply to this item at:

  <https://savannah.nongnu.org/task/?16414>

___
Message sent via Savannah
https://savannah.nongnu.org/

[task #16406] Submission of CC Mode

[Ineiev]

Update of task #16406 (project administration):

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

___

Follow-up Comment #16:

Thank you, approving.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/