[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Sanjay]

Follow-up Comment #21, task #15352 (project administration):


[comment #20 comment #20:]
> Thank you, approving.

Thank you.  Thanks for all the help.

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Ineiev]

Update of task #15352 (project administration):

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

___

Follow-up Comment #20:

Thank you, approving.

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Sanjay]

Follow-up Comment #19, task #15352 (project administration):

[comment #18 comment #18:]
> > > > No.  There aren't any files with wrong copyright notices in this
package.
> > > 
> > > Why?
> > 
> > What do you mean?
> 
> We discovered one file with a wrong copyright notice, so at that point, it
was possible that some files had wrong copyright notices.
> 
> I'd like to know why this is not the case now.

Oh.  Because I have now manually checked, to the best of my ability, every
file packaged in the fussy.tar.gz file for the copyright notice and that is
the correct one.  

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Ineiev]

Follow-up Comment #18, task #15352 (project administration):

> > > No.  There aren't any files with wrong copyright notices in this
package.
> > 
> > Why?
> 
> What do you mean?

We discovered one file with a wrong copyright notice, so at that point, it was
possible that some files had wrong copyright notices.

I'd like to know why this is not the case now.

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Sanjay]

Follow-up Comment #17, task #15352 (project administration):

[comment #16 comment #16:]
> > I have now added the required README file.
> 
> Thank you! README doesn't explicitly list the files the notices apply to;
> this is quite easy to get wrong, by just adding a new file with a different
> status; could you fix that?

Done.  The README file explicitly also lists the files the notices apply to.


> > I have modified the
> > scripts that generates them to include copyright and license notices in
them
> > when they are generated.  These files are not in fussy.tar.gz.
> 
> Then why not include them?  GNU standards say that such files should be
included .

OK.  I have no problem in including them -- they have the notices anyway (as
you point out).  They are now included in the fussy.tar.gz file.

> 
> >> I should ask if there are other such files with wrong copyright notices
> >> in your package.
> > No.  There aren't any files with wrong copyright notices in this package.
> 
> Why?

What do you mean?

I have updated the fussy.tar.gz file at
http://www.aoc.nrao.edu/~sbhatnag/Softwares/fussy.tar.gz.  Could you review it
again?

Thanks for your help so far.


___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Ineiev]

Follow-up Comment #16, task #15352 (project administration):

> I have now added the required README file.

Thank you! README doesn't explicitly list the files the notices apply to;
this is quite easy to get wrong, by just adding a new file with a different
status; could you fix that?

> src/*.a files are not part of the code repository for this project any more
> and are therefore also not part of the tar file.

It does't follow for me.  Making a release is more than just bundling up your
source files in a tar file and putting it up for FTP.

> While I do not understand
> why these files would require any notice whatsoever,

They require notices because they are copyrightable.

> I have modified the
> scripts that generates them to include copyright and license notices in
them
> when they are generated.  These files are not in fussy.tar.gz.

Then why not include them?  GNU standards say that such files should be
included .

>> I should ask if there are other such files with wrong copyright notices
>> in your package.
> No.  There aren't any files with wrong copyright notices in this package.

Why?

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Sanjay]

Follow-up Comment #15, task #15352 (project administration):

Kindly review the updated fussy.tar.gz file at
http://www.aoc.nrao.edu/~sbhatnag/Softwares/fussy.tar.gz.  Thanks.

Comments answers to your questions earlier are below.

[comment #13 comment #13:]
> > > Files like lex.yy.c and src/vm.a have no copyright and license notices
(please check other files as well).
> > 
> > We have removed these files.   These are not necessary and are generated
as part of the build process.  Apologies for missing to exclude them earlier.
> 
> This case is harder than removing files like 'configure': you'll need to
re-add them and  ensure their compliance  when your package is evaluated for
GNU ('configure' already was compliant).

src/*.a files are not part of the code repository for this project any more
and are therefore also not part of the tar file.  While I do not understand
why these files would require any notice whatsoever, I have modified the
scripts that generates them to include copyright and license notices in them
when they are generated.  These files are not in fussy.tar.gz.  

> 
> > We have checked that all files now have some copyright and license notice.
 Only files which have neither are the following PDF files.  Not sure if they
need these notices and if so, how to add them.
> > 
> > doc/LaTeX/Figs/fig1.pdf
> > doc/LaTeX/Figs/fig2.pdf
> 
> https://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html says that
if some file has a format that doesn't permit notices, they should be stated
in a README file in the same directory.  Haven't you read that page?

I have.  But misunderstood requirement for files like the .pdf files mentioned
above.  I have now added the required README file.



[comment #14 comment #14:]
> > Thanks for pointing this out.  We have now removed our copyright notice
from it
> 
> Oh, and of course, now I should ask if there are other such files with wrong
copyright notices in your package.

No.  There aren't any files with wrong copyright notices in this package.


___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Ineiev]

Follow-up Comment #14, task #15352 (project administration):

> Thanks for pointing this out.  We have now removed our copyright notice from
it

Oh, and of course, now I should ask if there are other such files with wrong
copyright notices in your package.

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Ineiev]

Follow-up Comment #13, task #15352 (project administration):

> Thanks for pointing this out.  We have now removed our copyright notice from
it, but kept the license notice.  Hope that is appropriate (and necessary?).

It already had a permissive license notice; you can add the notice from the
GPL on top of it, but it isn't necessary.

> > Files like lex.yy.c and src/vm.a have no copyright and license notices
(please check other files as well).
> 
> We have removed these files.   These are not necessary and are generated as
part of the build process.  Apologies for missing to exclude them earlier.

This case is harder than removing files like 'configure': you'll need to
re-add them and  ensure their compliance  when your package is evaluated for
GNU ('configure' already was compliant).

> We have checked that all files now have some copyright and license notice. 
Only files which have neither are the following PDF files.  Not sure if they
need these notices and if so, how to add them.
> 
> doc/LaTeX/Figs/fig1.pdf
> doc/LaTeX/Figs/fig2.pdf

https://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html says that
if some file has a format that doesn't permit notices, they should be stated
in a README file in the same directory.  Haven't you read that page?

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Sanjay]

Follow-up Comment #12, task #15352 (project administration):

[comment #11 comment #11:]

Could we request you to re-check the updated tar file
(http://www.aoc.nrao.edu/~sbhatnag/Softwares/fussy.tar.gz)?

Thanks for your continued effort in reviewing our submission.  Apologies for
missing the issues you mention below:
 
> INSTALL looks like the file from Autoconf; have you any copyright related to
it, really?

Thanks for pointing this out.  We have now removed our copyright notice from
it, but kept the license notice.  Hope that is appropriate (and necessary?).

> Files like lex.yy.c and src/vm.a have no copyright and license notices
(please check other files as well).

We have removed these files.   These are not necessary and are generated as
part of the build process.  Apologies for missing to exclude them earlier.

We have checked that all files now have some copyright and license notice. 
Only files which have neither are the following PDF files.  Not sure if they
need these notices and if so, how to add them.

doc/LaTeX/Figs/fig1.pdf
doc/LaTeX/Figs/fig2.pdf


> At last, some of your license notices say, "Foobar is distributed in the
hope that it will be useful".

Fixed.  "grep -ir foobar *" now does not find any file.  Apologies for missing
to check this earlier. 

> 
> > As a separate question: Is there an existing script/program
> > that one can use to ensure compliance of the source code
> > with Savannah requirements?
> 
> No.  There used to be an alpha-quality script, but we check packages
manually these days.  It shouldn't be a problem for your package, it has less
than 1000 files.

Thanks.  A combination of the "find" and "grep" commands to search for a few
keywords seems to be sufficient for this project.



___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Ineiev]

Follow-up Comment #11, task #15352 (project administration):

> Could you please check the source files again
(http://www.aoc.nrao.edu/~sbhatnag/Softwares/fussy.tar.gz)?
> AFAICT, all files have the copyright notices, we have updated
> all copyright notices to be same (GPLv3+) and the form of the
> notice is as advised by you.

Thank you!

INSTALL looks like the file from Autoconf; have you any copyright related to
it, really?

Files like lex.yy.c and src/vm.a have no copyright and license notices (please
check other files as well).

At last, some of your license notices say, "Foobar is distributed in the hope
that it will be useful".

> As a separate question: Is there an existing script/program
> that one can use to ensure compliance of the source code
> with Savannah requirements?

No.  There used to be an alpha-quality script, but we check packages manually
these days.  It shouldn't be a problem for your package, it has less than 1000
files.

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Sanjay]

Follow-up Comment #10, task #15352 (project administration):

[comment #9 comment #9:]
> > We are working separately to comply with GNU standards before it can be
accepted as a GNU Project.
> ...
> > Let us know if this is OK. I.e. get the various legal notices etc. right
to make it a Savannah project first, without changing how we currently build
the project.
> 
> It's up to you.  Let us to that separately.

Could you please check the source files again
(http://www.aoc.nrao.edu/~sbhatnag/Softwares/fussy.tar.gz)? AFAICT, all files
have the copyright notices, we have updated all copyright notices to be same
(GPLv3+) and the form of the notice is as advised by you.

We have also included ./configure and associated files now.  Those of course
can also be re-build by running the "./build" script.

As a separate question: Is there an existing script/program that one can use
to ensure compliance of the source code with Savannah requirements?
 

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Ineiev]

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

> We are working separately to comply with GNU standards before it can be
accepted as a GNU Project.
...
> Let us know if this is OK. I.e. get the various legal notices etc. right to
make it a Savannah project first, without changing how we currently build the
project.

It's up to you.  Let us to that separately.

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Sanjay]

Follow-up Comment #8, task #15352 (project administration):


[comment #7 comment #7:]
> 
> Savannah has no requirements about building the package from the source
code; but you applied for inclusion in the GNU Project, so you still should
comply with GNU Standards.

We are working separately to comply with GNU standards before it can be
accepted as a GNU Project.  There are other things in the code that need
change to comply with GNU standards.  Also we still don't know if it will even
be accepted as a GNU Project.  

Therefore we would like to start using Savannah as our git repos first and do
the development required on this repos to comply for acceptance as a GNU
Project. Hence the current effort to do whatever is needed to comply with
Savannah requirements.  

Let us know if this is OK. I.e. get the various legal notices etc. right to
make it a Savannah project first, without changing how we currently build the
project.

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Ineiev]

Update of task #15352 (project administration):

 Should Start On: Mon 05 Aug 2019 12:00:00 AM UTC => Tue 30 Jul 2019
12:00:00 AM UTC
   Should be Finished on: Mon 05 Aug 2019 12:00:00 AM UTC => Fri 09 Aug 2019
12:00:00 AM UTC

___

Follow-up Comment #7:

> This isn't "wrong" since the software currently builds by running the
"build" script which is included in the tar file.  This, as you can see,
generates the "configure" file.  Currently this is our preferred mode of
building the software.  I hope Savannah does not impose restrictions on how to
build the program from the source code.

Savannah has no requirements about building the package from the source code;
but you applied for inclusion in the GNU Project, so you still should comply
with GNU Standards.

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Sanjay]

Follow-up Comment #6, task #15352 (project administration):

[comment #5 comment #5:]
> Files like .gitignore and src/exit.dat still have no notices; also, many
files in your tarball say they are GPLv2+ rather than GPLv3+, and have an
obsolete address of the FSF. I recommend using the form of the notice from the
GPL HowTo .

OK.  We will modify the notices accordingly and make a modified tar file later
today.

> 
> > Others have been excluded in the tar.gz file.
> 
> As far as I can see, you excluded files like 'configure'.  This is wrong,
because your package needs them.

This isn't "wrong" since the software currently builds by running the "build"
script which is included in the tar file.  This, as you can see, generates the
"configure" file.  Currently this is our preferred mode of building the
software.  I hope Savannah does not impose restrictions on how to build the
program from the source code.

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Ineiev]

Update of task #15352 (project administration):

 Should Start On: Thu 01 Aug 2019 12:00:00 AM UTC => Mon 05 Aug 2019
12:00:00 AM UTC
   Should be Finished on: Thu 01 Aug 2019 12:00:00 AM UTC => Mon 05 Aug 2019
12:00:00 AM UTC

___

Follow-up Comment #5:

Files like .gitignore and src/exit.dat still have no notices; also, many files
in your tarball say they are GPLv2+ rather than GPLv3+, and have an obsolete
address of the FSF. I recommend using the form of the notice from the GPL
HowTo .

> Others have been excluded in the tar.gz file.

As far as I can see, you excluded files like 'configure'.  This is wrong,
because your package needs them.

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Sanjay]

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

[comment #3 comment #3:]
> > I haven't added these notices to files which are generated (as against
written by us).
> 
> I think Information for maintainers of GNU software
 doesn't
distinguish between "written" and "generated" files.

OK. Check again the tar file:
http://www.aoc.nrao.edu/~sbhatnag/Softwares/fussy.tar.gz.  All copyrightable
files should have notices.  Others have been excluded in the tar.gz file.

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Ineiev]

Update of task #15352 (project administration):

 Should Start On: Tue 30 Jul 2019 12:00:00 AM UTC => Thu 01 Aug 2019
12:00:00 AM UTC
   Should be Finished on: Fri 09 Aug 2019 12:00:00 AM UTC => Thu 01 Aug 2019
12:00:00 AM UTC

___

Follow-up Comment #3:

> I haven't added these notices to files which are generated (as against
written by us).

I think Information for maintainers of GNU software
 doesn't
distinguish between "written" and "generated" files.

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Sanjay Bhatnagar]

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

[comment #1 comment #1:]
> Please make sure that all copyrightable files in your tarball have valid
copyright and license notices.  Currently, README has neither.

I am added copyright and license headers in all files I think are
copyrightable.  This includes README, README.md, TODO, NOTES and a few other
files.  I haven't added these notices to files which are generated (as against
written by us).  Hope this is sufficient.

The changes are in http://www.aoc.nrao.edu/~sbhatnag/Softwares/fussy.tar.gz. 
I am also attempting to attach this file with this task (not quite sure I know
how to do it yet though).

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Ineiev]

Update of task #15352 (project administration):

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

___

Follow-up Comment #1:

Please make sure that all copyrightable files in your tarball have valid
copyright and license notices.  Currently, README has neither.

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15352] Submission of An interpretor for a language with automatic error propagation

[Sanjay Bhatnagar]

URL:
  

 Summary: Submission of An interpretor for a language with
automatic error propagation 
 Project: Savannah Administration
Submitted by: sanb
Submitted on: Tue 30 Jul 2019 08:32:30 PM UTC
 Should Start On: Tue 30 Jul 2019 12:00:00 AM UTC
   Should be Finished on: Fri 09 Aug 2019 12:00:00 AM UTC
Category: Project Approval
Priority: 5 - Normal
  Status: None
 Privacy: Public
Percent Complete: 0%
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
  Effort: 0.00

___

Details:

A new project has been registered at Savannah
This project account will remain inactive until a site admin approves
or discards the registration.


= Registration Administration =

While this item will be useful to track the registration process,
*approving or discarding the registration must be done using the specific
Group Administration
 page*,
accessible only to site administrators,
effectively *logged as site administrators* (superuser):

* Group Administration



= Registration Details =

* Name: *An interpretor for a language with automatic error propagation *
* System Name:  *fussy*
* Type: non-GNU software and documentation
* License: GNU General Public License v3 or later



== Description: ==
The fussy program implements a scripting language with an algorithm for
automatic error propagation of random measurement errors in an arbitrary
mathematical expression. The program can be used as a simple interactive
calculator with error propagation. Mathematical expressions can be implemented
as a collection of sub-expressions, as sub-program units (functions or
procedures) or as single atomic expressions. Sub-expressions can be assigned
to temporary variables which can then be used to write the final expression.
The interpreter is internally implemented as a virtual machine for efficient
runtime performance and can be used as an interpreter in a client code as
well. A simple C binding to the interpreter is also provided.

The scripting syntax of fussy is similar to that of C programming language. It
is easy, particularly for those familiar with programming in C, to use fussy
with minimal learning. In its simplest form, fussy interpretor can be used
interactively as a simple calculator with the added feature of automatic error
prorogation (see syntax for simple expressions, sub-expressions, and
functions/procedure).


== Other Comments: ==
The code depends only on libraries and tools available on standard  GNU/Linux
system.

We currently host the project on GitHub:

https://github.com/sanbee/fussy


== Tarball URL: ==
http://www.aoc.nrao.edu/~sbhatnag/Softwares/fussy.tar.gz






___

Reply to this item at:

  

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