taskSavannah Administration - Tasks: task #16372, Submission of MicroBenchmark

 
 

task #16372: Submission of MicroBenchmark

Submitter:  Miguel Ángel Arruga Vivas <m1gu3l>
Submitted:  Sun 04 Jun 2023 04:57:22 PM UTC
   
 
Should Start On:  Sat 03 Jun 2023 10:00:00 PM UTC Should be Finished on:  Tue 13 Jun 2023 10:00:00 PM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Done Privacy:  Public
Assigned to:  ineiev Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Wed 07 Jun 2023 04:03:57 PM UTC, comment #14: 

Again, thank you for your time, help and effort.

Miguel Ángel Arruga Vivas <m1gu3l>
Wed 07 Jun 2023 02:30:47 AM UTC, comment #13: 

Thank you, approving.

Ineiev <ineiev>
Site Administrator
Tue 06 Jun 2023 05:08:20 PM UTC, comment #12: 


comment #11:

> I can see that po/en@boldquot.gmo and po/en@quot.gmo have no license notices.


These are binary files.  The tarball attached to this answer contains a README file on the po directory specifying that they are subject to the same license as the rest of the program (LGPLv3+) and some general information regarding their regeneration.



(file #54821)

Miguel Ángel Arruga Vivas <m1gu3l>
Tue 06 Jun 2023 04:32:59 PM UTC, comment #11: 

Sorry, I must have looked into an older tarball...

I can see that po/en@boldquot.gmo and po/en@quot.gmo have no license notices.

Ineiev <ineiev>
Site Administrator
Tue 06 Jun 2023 04:14:44 PM UTC, comment #10: 

comment #9:

> Is anything still unclear about this point?


There was nothing unclear, as I already applied the changes in the direction you were asking for:

comment #8:

> [...] I've changed the build process and the manual to generate and include them as texinfo files instead.


Perhaps I wasn't clear that they have a copyright line and license notice; they do now.

> [...]
> (file #54815)


Is there any issue with that version?

Miguel Ángel Arruga Vivas <m1gu3l>
Tue 06 Jun 2023 05:19:36 AM UTC, comment #9: 

JSON can easily include legal notices,

{
  "copyright-notice": "Copyright 2023 J. R. Hacker",
  "license-notice": "Copying and distribution of this file, with
    or without modification, are permitted in any medium without
    royalty provided the copyright notice and this notice are
    preserved.  This file is offered as-is, without any
    warranty."
}


Is anything still unclear about this point?

Ineiev <ineiev>
Site Administrator
Mon 05 Jun 2023 07:31:25 PM UTC, comment #8: 

comment #7:

> So, the first point: the technique of a README file is only applicable for files whose format has no place for notices; text files should include copyright and license notices directly.


I understand your point, but not all text file formats support comments to include notices (JSON is probably a very common example).  This was the case with the old files but I've changed the build process and the manual to generate and include them as texinfo files instead.

Is there any other issue pending?

(file #54815)

Miguel Ángel Arruga Vivas <m1gu3l>
Mon 05 Jun 2023 06:27:01 PM UTC, comment #7: 

[reordered]

> > Then, po/en@boldquot.header po/en@quot.header still have no notices.
>
> This are copied by autopoint --install --force, so I had to workaround the build process.

...

> To avoid further issues, I added a copyright line and license notice to Makevars, as my changes are already around 10 lines.


Ok.

> The attached tarball includes a README file on the same directory indicating their license and their regeneration process.  Thanks for pointing out the latter.


We are miscommunicating here; probably I lumped too many points in a single passage.  I'll separate them and write by one in a message.

So, the first point: the technique of a README file is only applicable for files whose format has no place for notices; text files should include copyright and license notices directly.

Is that clear?

Ineiev <ineiev>
Site Administrator
Mon 05 Jun 2023 05:47:41 PM UTC, comment #6: 

Thank you again for your time.

comment #5:

> [...]
> These are text files; if they are copyrightable, the notices should be included in them; if they are not, a note explaining their status and how they are generated would be nice to include.  Can you figure out which is the case?


The attached tarball includes a README file on the same directory indicating their license and their regeneration process.  Thanks for pointing out the latter.

> Then, po/en@boldquot.header po/en@quot.header still have no notices.


This are copied by autopoint --install --force, so I had to workaround the build process.  I've chosen to replace them with a link to an appropiate section of GNU gettext documentation instead of adding a license notice, as they are included into en@{bold,}quot.po and they already have a copyright line and license notice.

To avoid further issues, I added a copyright line and license notice to Makevars, as my changes are already around 10 lines.

I hope this solves all the licensing issues, let me know any point I could have missed.

(file #54814)

Miguel Ángel Arruga Vivas <m1gu3l>
Mon 05 Jun 2023 03:00:43 PM UTC, comment #5: 

Thank you!

comment #3:

> comment #2:
> > doc/examples/basic.log, basic-guile.log, fib.log: These files are generated by the output of basic examples and included verbatim into the texinfo manual. They can be regenerated and are quite short, are they worthy of a note to place them on public domain?  A license notice there would be misleading.
>
> Sorry, I missed the ten lines limit.  The attached file contains a README file on the same folder applying the conditions to these files too.


These are text files; if they are copyrightable, the notices should be included in them; if they are not, a note explaining their status and how they are generated would be nice to include.  Can you figure out which is the case?

Then, po/en@boldquot.header po/en@quot.header still have no notices.

Ineiev <ineiev>
Site Administrator
Sun 04 Jun 2023 08:18:41 PM UTC, comment #4: 


comment #2:

> * ChangeLog: It seems customary to not include a license on this file, is this wrong?  It is generated by gitlog-to-changelog and a make target, so it wouldn't be a problem to add it if necessary.


Sorry again, my bad: https://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html

The attached tarball solves this one too.

(file #54812)

Miguel Ángel Arruga Vivas <m1gu3l>
Sun 04 Jun 2023 07:54:50 PM UTC, comment #3: 


comment #2:

> doc/examples/basic.log, basic-guile.log, fib.log: These files are generated by the output of basic examples and included verbatim into the texinfo manual. They can be regenerated and are quite short, are they worthy of a note to place them on public domain?  A license notice there would be misleading.


Sorry, I missed the ten lines limit.  The attached file contains a README file on the same folder applying the conditions to these files too.

(file #54811)

Miguel Ángel Arruga Vivas <m1gu3l>
Sun 04 Jun 2023 07:31:46 PM UTC, comment #2: 

Thanks for your quick answer.

I've executed this on the old tarball and these are the files don't have a Copyright line:

mbenchmark-0.0$ for f in `find -type f`; do fgrep Copyright $f >/dev/null 2>&1 || echo $f; done | sort
./ABOUT-NLS
./AUTHORS
./ChangeLog
./doc/examples/basic-guile.log
./doc/examples/basic.log
./doc/examples/fib.log
./include/config.h.in
./po/boldquot.sed
./po/en@boldquot.header
./po/en@quot.header
./po/POTFILES.in
./po/quot.sed
./po/stamp-po


The attached tarball solves this detected issues:

  • include/config.h.in: License text added.
  • po/POTFILES.in: License text added.


I didn't add a license notice to these others:

  • AUTHORS: Currently is only a line too, I think it doesn't apply either.
  • ChangeLog: It seems customary to not include a license on this file, is this wrong?  It is generated by gitlog-to-changelog and a make target, so it wouldn't be a problem to add it if necessary.
  • doc/examples/basic.log, basic-guile.log, fib.log: These files are generated by the output of basic* examples and included verbatim into the texinfo manual. They can be regenerated and are quite short, are they worthy of a note to place them on public domain?  A license notice there would be misleading.
  • ABOUT-NLS and po/*: They are copied by autopoint.


(file #54810)

Miguel Ángel Arruga Vivas <m1gu3l>
Sun 04 Jun 2023 05:59:41 PM UTC, comment #1: 

Please make sure that all copyrightable files in your tarball
have valid copyright and license notices.

Ineiev <ineiev>
Site Administrator
Sun 04 Jun 2023 04:57:22 PM UTC, original submission:  

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


Registration Administration


Approving or discarding the registration must be done using the specific
Group administration page, accessible only to site
administrators logged in as superusers.

Registration Details


  • Name: MicroBenchmark
  • System Name:  mbenchmark
  • Type: non-GNU software and documentation
  • License: GNU Lesser General Public License (Code original from the project:

GNU LGPLv3+: Library code and build files.
GNU FDLv1.3+: Info pages.
GNU GLPv3+/FDLv1.3+: Examples and code for the info pages.
Public Domain: Generic project files, such as README.

External files:
GNU GPLv3+: gitlog-to-changelog from GNU gnulib, test-driver.scm from GNU guix.)




Description:

MicroBenchmark is a library implemented in C99--with bindings for
other programming languages: currently C++ and GNU Guile
Scheme--designed to measure the performance of code fragments.  The
comparison of these kind of measurements between different
implementations and/or environments is usually called micro benchmark,
hence the library name.

The main unit of MicroBenchmark framework is the `Test Case'.  A Test
Case encapsulates a code fragment whose performance will be measured
and, optionally, may contain data provided by the user, as well as
code to set up and tear down the execution fixture.  One or more Test
Cases compose a Suite, which is responsible for their execution
lifecycle.  To measure the performance, the code under test is
executed multiple times and the measurements performed are aggregated
into a report.  These reports are accessible through the suite and
can be printed or examined programmatically.


Other Software Required:

- Runtime: C library
- Build: C compiler (GCC 4+, clang 6+)
- Build: GNU Automake
- Build: GNU Autoconf
- Build: GNU libtool
- Build: sed
- Build: awk
- Build: make
- Build: Bourne Shell
- Build: GNU Texinfo (+TeX distribution)
- Optional: C++ compiler (GCC 5+, clang 6+)
- Optional: GNU Guile 2.2+



Other Comments:

.gitignore files are not included on the tarball; they are released to the public domain.


Tarball URL:

https://savannah.gnu.org/submissions_uploads/X0cRXg-mbenchmark-0.0.tar.gz


Miguel Ángel Arruga Vivas <m1gu3l>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #54821:  mbenchmark-0.0.tar.gz added by m1gu3l (770KiB - application/gzip)
file #54815:  mbenchmark-0.0.tar.gz added by m1gu3l (770KiB - application/gzip - changed examples to texi format)
file #54814:  mbenchmark-0.0.tar.gz added by m1gu3l (769KiB - application/gzip - fixed ChangeLog, config.h.in, doc/examples/*.log, po/*.header)
file #54812:  mbenchmark-0.0.tar.gz added by m1gu3l (759KiB - application/gzip - fixed ChangeLog, config.h.in, POTFILES.in, doc/examples/*.log)
file #54811:  mbenchmark-0.0.tar.gz added by m1gu3l (758KiB - application/gzip - fixed config.h.in, POTFILES.in, doc/examples/*.log)
file #54810:  mbenchmark-0.0.tar.gz added by m1gu3l (758KiB - application/gzip)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by ineiev (Posted a comment)
  • -email is unavailable- added by m1gu3l (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 10 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2023-06-07 ineiev StatusIn Progress Done
        Open/ClosedOpen Closed
    2023-06-06 m1gu3l Attached File- Added mbenchmark-0.0.tar.gz, #54821
    2023-06-05 m1gu3l Attached File- Added mbenchmark-0.0.tar.gz, #54815
    2023-06-05 m1gu3l Attached File- Added mbenchmark-0.0.tar.gz, #54814
    2023-06-04 m1gu3l Attached File- Added mbenchmark-0.0.tar.gz, #54812
    2023-06-04 m1gu3l Attached File- Added mbenchmark-0.0.tar.gz, #54811
    2023-06-04 m1gu3l Attached File- Added mbenchmark-0.0.tar.gz, #54810
    2023-06-04 ineiev StatusNone In Progress
        Assigned toNone ineiev

    Back to the top

    Powered by Savane 3.13-3230.
    Corresponding source code